Agree on the rules before people invest an evening, not after a contested item drops. A short, specific agreement usually helps more than a long list of assumed conventions. This is an organizer's communication checklist, not confirmation that a particular loot system is available in every version of WoW Forever.
Put the agreement where everyone can read it
State the intended loot approach in the group post and repeat it before starting. Name reservations and exceptions explicitly. Explain the priority order, who distributes loot, and who reviews a disagreement involving that person.
The phrase "standard rules" is not enough when players arrive from different guilds or game versions. Link one stable written policy and announce any change before people agree to participate.
Resolve the predictable edge cases
- Main role versus an off-spec or alternate role.
- Tied rolls and any restrictions on repeated wins.
- A late arrival, replacement, or early departure.
- A player disconnecting at the relevant moment.
- A reserved item and whether the reservation has conditions.
- A mistaken distribution and the limits of any correction.
Check the actual game rules before promising that an item can be traded or recovered. Community agreement cannot override the game's item restrictions.
Replace an ambiguous rule with a useful one
Ambiguous example: Main spec first, usual rules, one item reserved.
That leaves the reserved item unnamed and does not explain roles, ties, or exceptions. A better recruitment message names the reservation, identifies how a player's main role is agreed, describes how ties are resolved, and links the complete policy. If those decisions have not been made, resolve them before asking players to commit.
This is a communication example, not a ready-made policy or an endorsement of a particular loot system. Each host is responsible for choosing rules that are supported by the game and understood by the group.
The pre-run check
- The same written rules are visible to everyone.
- Reservations and priorities are explicit.
- Players have had a chance to ask questions.
- The host, distributor, and second reviewer are identified.
- Start time, expected finish, and replacement expectations are clear.
- Any changes were announced before participation, not after a drop.
The group-post guide explains where these details fit into recruitment.
If a decision seems wrong
Ask for a calm explanation against the written agreement. A misclick, misunderstanding, or missed message may have a straightforward explanation. Do not threaten a player or ask others to pile on.
If review is still needed, preserve the original rules, relevant roll/allocation, surrounding conversation, date, region, ruleset, and complete character identity. For Forever, use the full two-part character name rather than only a first name. Avoid unrelated private messages or personal data, and do not present a cropped accusation as the whole sequence. The current safety tools still use a legacy realm field: ask staff to confirm the supported intake before filing a Forever-specific case; do not invent a realm or match someone by first name alone.
Submit relevant information through the private report process. A report is not automatically published. Read the evidence and safety policy for how review works.
Understand what moderation can do
Community staff cannot restore items, reverse trades, suspend game accounts, or verify every interaction. Use Blizzard's own reporting tools for issues requiring platform action. Our public alerts require separate review and have an appeal route; pending appeals suspend the alert during review.
No addon or directory badge can guarantee a trouble-free group. Clear expectations, specific evidence, and proportionate review are the practical tools available to organizers and players.
Written by WoW Forever Discord Team. About our organizers · Suggest an article correction in Discord

