Connect the right Discord guild.
Start with a Discord server you can manage, your WoW guild’s name, realm and region, and a channel for raid signups. Use the bot invite supplied by your Loothing administrator. Review the requested Discord permissions and authorize the intended server. These bot permissions allow channel messages, embeds, commands and setup; they are separate from a member’s access inside Loothing.
- Log in. On Loothing, choose Login with Discord, then select your server. The login prompt requests your identity and server list; it does not install the bot.
- Run Guild Setup. Open
/setup. Work through Battle.net, Characters, Warcraft Logs and Discord Channels. Steps save independently. Raider.io and AI configuration can be left for later. - Check guild identity. Match the WoW guild name, realm and region in your integrations. A Discord server name alone does not identify a Battle.net guild.
Battle.net provides character and armory data; the platform’s shared credentials have a guild quota. For your own developer client, use the wizard’s exact redirect and service URLs. Save before Test Connection: the test uses saved credentials. Warcraft Logs needs a V2 OAuth client, not the older Web API key. See Guild Setup and Bot Setup for the full forms.
Give officers the right access.
Loothing permissions belong to the selected guild. Someone can administer one guild and be a regular member in another. Use Discord Role Mapping to give each role the individual permissions its work needs; multiple roles combine their grants.
| Responsibility | Permissions to consider |
|---|---|
| Read raid and loot information | events.view, loot.view |
| Prepare characters and roster data | players.view, with players.import and players.manage for assigned officers |
| Run events or maintain loot records | events.manage or loot.manage, according to responsibility |
| Use council upgrade information | loot.council; raiders submit reports with droptimizer.submit |
The automatically created lootAdmin role and Discord server ownership bypass ordinary guild permission checks. Assign lootAdmin sparingly. Test a normal member’s view as well as an officer’s. Individual deny overrides can block a role grant; use the Permissions guide when access seems inconsistent.
Build a roster that represents your team.
In the setup wizard’s Characters step, import through Roster Sync, manual entry or CSV, then use Link to Discord. Check Auto-Link matches before relying on them. Members can self-link with /claim or connect Battle.net on their Account page.
Create a roster at /raid-roster. Set its name, type, difficulty and composition targets. Add the actual raid characters, choose Tank, Healer, DPS or Flex, and check their spec and status. A named main team is easier to keep accurate than one list containing every alt.
Roster sync enriches gear and performance data; it does not add or remove roster members. Unlinked characters can appear in the roster, but Discord reminders and auto-confirmations need their owner linked.
Visit /roster-audit before raid night. Review tier, enchants, gems and the character detail view. Adjust the roster’s Config to your team’s requirements. Audit flags depend on those settings and available source data, so investigate a missing value before treating it as a player’s missing preparation. The Roster & Audit guide covers composition, snapshots and exports.
Prepare gear context before a drop.
On Wishlists, select a character and create a named list. Add items through search or loot tables, then set priority and need: BiS, Major, Minor, Optional or Transmog. Search uses the cached item database, so an absent result can mean the item has not been imported.
Choose visibility deliberately: Private, Guild, Officers or Public. Link the wishlist to the raid roster so officers can find it during distribution; one list can serve multiple rosters. Mark received items fulfilled and keep the list current when a character’s gear or spec changes.
Use Gear & Upgrades for upgrade-track, raid, vault and crafting context. Consult its current tables rather than carrying old season values into raid requirements. BiS recommendations require an officer’s import. Where relevant, a Raidbots Droptimizer report adds simulation context; check its character, setup and freshness. A priority or score supports discussion, it does not settle the guild’s award policy. See Wishlists for sharing and roster assignment.
Publish a raid people can sign up for.
From Events, choose New Event. In the Builder Wizard, pick Raid and its difficulty, then set the title, start time, duration, signup channel, visibility and any requirements. Check the time against your guild’s expected timezone.
Configure role slots and limits. Link your roster to pre-populate signups, use Split DPS if you need separate melee and ranged slots, and decide whether Require Character, Auto-accept and Waitlist fit your process. Inspect the Discord embed preview and review the schedule before saving.
A saved event begins as Draft. Use Publish to post the signup embed and make it Scheduled. Ask a member to select their character, role and Accept, Tentative or Decline status. Verify the signup appears correctly before sharing it widely. Later, review the Attendance tab rather than assuming every accepted signup attended. Templates and recurrence can wait until this first event works; the Events & Signups guide explains them.
Record what happened, then inspect it.
Agree on responses, council membership and award criteria before the raid. Keep the item, recipient, source encounter and reason clear. Loothing’s website can receive existing loot data without requiring everyone to adopt a new addon first.
- Choose the source. In the Loot Hub’s Import tab, upload JSON, CSV or TSV, or paste an addon export. For an individual correction or entry, use the History workflow.
- Preview and validate. Check character identities, item details, dates, encounter context and responses. Read errors and warnings before Confirm Import. Keep the original export available for comparison.
- Verify History. Filter by player, item or date, then open an entry. Review Award Context and Gear Comparison; officers can inspect candidate information when available.
Use Items and Instances to trace drops across recipients and runs. Statistics and Analytics help officers review distribution patterns, but the history only describes recorded or imported data. Missing raids, incomplete candidates or different response conventions affect what those patterns mean. An analytics flag is a reason to investigate, not proof of an unfair award. The Loot System guide explains views, filters and import validation.
Add the in-game workflow when you need it.
The optional Loothing addon brings responses, council voting, awards and history into WoW. Follow the Addon guide for installation and configuration. Agree on the master looter, council and response buttons, then rehearse the process before a live raid.
Raiders respond to items; council members review candidates and vote under the configured rules. The master looter resolves the award. Export History as Compact, then paste it into the website’s Import tab and review the preview. Native-roll records can exclude players whose guild membership is not confirmed; inspect the import’s retained count and notices.
Confirm the actual item reaches the recipient. The addon has pending-trade tracking, but a website History entry alone does not establish that the in-game transfer finished.
Troubleshoot the specific missing step.
- Server missing from the selector? Check the Discord account and Manage Server permission. Invite and web login are separate steps.
- Connection test fails? Save first; check client type, exact callback URL, guild realm and region. Read any quota banner before retrying roster sync.
- Member misses reminders? Check character-to-Discord linking and the event’s reminder settings, then channel or DM access.
- Roster or loot looks incomplete? Confirm the selected guild, roster, filters and import source. Compare one known character or drop before processing another full export.
- Addon window closed or state stale? The addon guide documents
/lt reopen,/lt resyncand/lt diagfor session recovery and diagnostics.
Your first working loop is small: a correctly linked character, a shared wishlist, a published event with a verified signup, and one checked loot record. Repeat that loop before adding more automation.
Continue with Loothing’s own guides.
This walkthrough follows Loothing’s product guide system. Open the full guide directory for illustrated steps, character imports, guild administration and other workflows.
For the next step, explore Frostsim’s simulation guide or return to all Frostdev guides.