Most loot disputes are easier to prevent before the first pull. A group does not need complicated rules, but everyone should be able to read the same rules and understand what happens when an item drops.
Put the agreement in writing
State the loot system in the recruitment post and again before starting. List reservations, exceptions, off-spec priority, and who handles distribution. If an item is reserved, name it explicitly. A label such as "standard rules" is not enough when players come from different communities.
Ask questions before you commit time. A leader should be willing to explain how tied rolls, late arrivals, replacements, and disconnected players are handled. If the answer is unclear, wait for clarification.
Check identity and context
Character names are not globally unique. Record the realm and region along with the name. Similar spellings, transfers, and renamed characters can cause mistaken identity. Guild membership alone does not establish responsibility for another player's actions.
Avoid treating a screenshot of an accusation as proof. A community tool can provide context, but a warning needs a source, a date, and a way to appeal. Read the safety policy before relying on any published alert.
Capture the full sequence if something goes wrong
- The original loot rules, including reservations.
- The item and relevant roll or allocation.
- The character and realm involved.
- The conversation around the disputed decision.
- The date, approximate time, and run details.
Keep original screenshots. Cropped images may remove the context a reviewer needs. Do not include unrelated private conversations or personal information. Use the game's reporting tools for conduct that needs Blizzard action.
Try a calm clarification
Ask the leader to explain the decision against the written rules. A misclick, overlooked reservation, or misunderstanding may have a straightforward correction. Do not threaten other players or invite a public pile-on.
If the issue remains unresolved, submit a private report. Our moderators review evidence; a submitted report is not automatically published. Public alerts require separate reviewer approval and expire unless renewed.
Understand the limits of community moderation
We cannot restore items, reverse trades, suspend game accounts, or verify every interaction. Those actions belong to Blizzard or the relevant platform. Our role is to review conduct within the community and publish carefully limited safety information where the evidence supports it.
Players affected by a published alert can appeal. Pending appeals suspend an alert from public listings and addon exports while reviewers consider the new context.
For organizers
Keep one stable link to your rules and record when they change. Announce changes before people join a run, never retroactively after a contested drop. Designate a second officer who can review disputes involving the raid leader. Clear expectations protect both players and organizers.
Written by the Forever Community Team. About our organizers · Suggest a correction