Moderation records
Keep decisions understandable for the next person reviewing them.
Watchpost moderation commands and automatic records are not confirmed as available. These are the intended operating rules.
What a case should contain
- A stable case reference and the affected user's ID.
- The action, moderator and timestamp.
- A specific reason tied to a community rule.
- Relevant evidence references with appropriate access restrictions.
- Later corrections, appeals and their outcomes.
Write reasons that another moderator can understand. “Repeatedly interrupted the session after two reminders” is more useful than “bad behaviour.” Avoid unrelated personal information.
Discord and ER:LC are separate
A Discord action does not automatically take effect in ER:LC. Any future in-game action must identify the game account and target server explicitly. Do not claim an in-game action succeeded unless the integration confirms its outcome.
Corrections and appeals
Give members a defined route to request review. Where possible, a different staff member should review a disputed action. Preserve the original record and append the outcome; do not silently rewrite the history.
If an action fails
Record what was requested and whether the result is known. If the request timed out, check the target state before trying again. A duplicate punishment is harder to undo than a delayed one. Keep technical errors out of public announcements and report them with secrets removed.