On the rota
A moderator does the work that arrives whether or not an event is running: proof to look at, accounts to verify, a roster that drifts. This is what the queue is made of, and how to clear it without becoming the reason people wait.
What the role is
Roles stack downward: everything a moderator can do, a treasurer and an admin can do too. What a moderator specifically owns:
- the roster: syncing it, adding people, promoting a guest
- account verifications — the XP challenge and manual review
- submissions and proof screenshots
- weekly competitions and the schedule
- feedback from members
What they cannot do, on purpose:
- create or edit an event, or its tiles
- change clan settings or Discord wiring
- promote anyone, or touch staff
- settle a fee or run a payout
Start at what needs you
The admin dashboard is not a summary of the site — it is a list of what is waiting, ordered by how much it matters, computed from real data rather than from counters that drift. If it says nothing needs you, nothing does.
Work it top down. The items that reach the top are the ones with a person on the other end of them: someone who can’t sign up because their account isn’t verified, or whose drop hasn’t counted because nobody looked at it yet.
Submissions and proof
Most credits never reach you: the plugin sees the drop, files a screenshot stamped with the team and a UTC timestamp, and the tile completes. What lands in the queue is the manual tiles and anything the plugin flagged.
The stamp is what makes a proof hard to argue with. A plugin screenshot carries the team and the moment baked into the picture, and with two-frame proof enabled a second frame a couple of seconds later shows the loot settled on the floor. A screenshot without any of that is a screenshot from a phone, which is fine — it just means you are the one doing the checking.
Verifying accounts
Nobody can sign up for an event without at least one verified account, so this queue directly blocks people from playing. It is the one worth clearing daily.
Verifying an account says “this is really theirs”. It does not put them in the clan — clan membership comes only from an in-game roster sync or an admin adding them by hand. Someone verified but not on the roster is a guest: tracked, visible, and not a member. That is deliberate, and it is what stops anyone joining your clan by typing a name.
Keeping the roster true
The roster comes from one place: an admin runs a sync from the in-game clan list, with the Anvil button in the clan window’s title bar (or Sync roster in the plugin’s side panel). Everything else — verifications, links, sign-ups — hangs off it.
So the maintenance job is small but real: run the sync after any recruitment round, promote the guests who have actually joined, and look at people the site has flagged as needing review rather than waiting for them to complain.
A member’s last-seen-in-clan timestamp records the last roster sync that found them, not the last time they logged in. For “are they still playing”, read their live stats time instead — it is the one that moves on its own.
Reviewing starting shots
On an event that requires one, every player has to file a screenshot taken after the event went live, at a location drawn at the start moment. Plugin captures with a verified keyword arrive already accepted, so in practice you are only looking at the players who uploaded by hand from a phone.
What you are checking is small: the character is in the picture, the keyword is in the chatbox, and it is the keyword that player was actually given. The uploads count immediately and you review them after the fact, so nobody is blocked from playing while they wait for you.
The calls you will have to make
None of these have a right answer in software, which is why they reach a person.
A moderator sees everything a member does plus the review surfaces. Creating and editing events, settings, staff and payouts are admin and treasurer jobs — if a button isn’t there, that’s why, and it’s deliberate.