Reports, complaints and sanctions

LS-PRO-007 · version 1.4 · Approved · next review 2027-05-07

1. Purpose

This procedure says how Landsidu handles four things: applications to join, reports about players, complaints about Landsidu itself, and appeals against a sanction. It also sets the sanctions staff use and how each one is recorded, so every case is handled the same way and can be checked and appealed.

2. Scope

The Landsidu Discord and every game server Landsidu hosts. Bugs go to the bug-reports forums and are not covered here; exploits and security holes follow LS-PRO-009.

3. Terms

4. Responsibilities

The response times below are Landsidu's own targets.

5. Applications

1. A newcomer joins through the public link and sees only the Start here area, which includes apply.
2. They accept the rules on Discord's rules screen, then open a private thread in apply using the pinned template: their in-game name for each game, which games they want (DayZ, Minecraft, general chat), and their Steam profile link if they choose to give it.
3. A Moderator or Admin replies within 24 hours. An Admin or the Owner checks the in-game name against the game's logs, its ban list and the player register for an earlier ban; a Moderator handling the application asks them to.
4. They give the roles asked for (DayZ, Minecraft, Member) and post a short welcome in the thread, or explain why not. Family and Kids roles are never given this way.
5. The Owner or an Admin adds or updates the person's entry in the player register: Discord name, in-game names and every Steam ID given or found, including second accounts. A Moderator who handled the application posts <date> | <member> | application approved | register entry needed in mod-log for them. Nothing from the register goes in Landsidu's documents.
6. They archive the thread without locking it, so the member can post in it again with later questions. It is removed 1 year after its last post.

If private threads aren't available on the server (LS-WI-001 section 8 step 4, branch B): newcomers and reporters send a direct message to a Moderator or Admin instead, or, if their direct messages are blocked, email contact@landsidu.com. Staff log each case in mod-log with the same line form (section 9) and keep any screenshots in a staff-only channel, never in their own messages or inbox alone.

6. Reports about players

6.1 Routes

6.2 Steps

1. Acknowledge in the thread within 24 hours: say it has been seen and who is looking at it.
2. Keep the evidence before acting. Turn on Discord's Developer Mode, copy the user and message IDs, and take screenshots before deleting anything or banning with message deletion; deleted messages and their IDs can't be recovered. For game reports, note the server, the time (Perth time) and the in-game names, and check the game logs, which are kept for 90 days. The one exception: never screenshot, copy, download or forward suspected sexual material involving a child. Record only where it is (the message link) and follow section 6.3.
3. Hear both sides where it is safe to: ask the other player for their account if the report is not clear-cut.
4. Decide using the steps in section 8, and write the outcome in the thread: what was found and what was done, without other players' private details. Tell the person sanctioned which rule was broken, what was done and the date; their 30 days to appeal (section 7) start from that notice.
5. Record the action in mod-log (section 9), and in the player register if it is a ban or hostile listing.
6. Close the thread. It is removed 1 year after closing.

6.3 A child's safety

Anything that may put a child at risk is never discussed in public or in a shared thread. First response, by whichever staff member sees it first:

1. If a child is in immediate danger, call 000 first.
2. Stop the contact now: kick the person. A kick removes all their roles, the children's area included, and they can only come back into the waiting room. A Moderator doesn't wait for an Admin or the Owner to do this. A time-out alone isn't enough: a timed-out member can still read every channel they could see. Only the Owner can give or remove the Kids and Family roles (LS-WI-001 section 2).
3. Keep the evidence safely: the message links, user IDs, times and what was said, as section 6.2. Never screenshot, copy, download or forward suspected sexual material involving a child; record only its message link.
4. Report it to Discord's Trust & Safety team, and for suspected online grooming or sexual exploitation to the Australian Centre to Counter Child Exploitation (accce.gov.au/report). The eSafety Commissioner takes reports of other harmful content.
5. Tell the Owner straight away by direct message. The Owner decides on the ban and any further report, and records it as an incident in LS-REG-005, naming roles only.

7. Complaints and appeals

• A complaint about Landsidu: a direct message to an Admin, or email contact@landsidu.com. The Owner acknowledges it within 2 days and answers within 14 days.
• An appeal against a sanction or a hostile listing: within 30 days, a direct message to an Admin, or email contact@landsidu.com, saying why it was wrong. The Owner hears it. Where there is a second staff member, someone other than the person who gave the sanction looks at it. The answer is final and is recorded beside the original action in mod-log.
• If you've been banned and can't use the Discord, email contact@landsidu.com. Joining again on another account to appeal counts as ban evasion.
• Complaints and appeals are reviewed for patterns at each quarterly management review, and lessons are recorded in LS-REG-005.

8. Sanctions

Staff judge each case and keep to these steps:

Straight to a ban: anything that puts a child at risk; sharing someone's personal details; harmful links; cheating, including using an exploit for advantage; ban evasion (the new account and the old one). Finding or minimally demonstrating an exploit in good faith and reporting it privately is not a breach (LS-PRO-009 section 7). A ban for any of these covers the Discord and every Landsidu game server; other bans cover where the breach happened, and the notice says which.

A straight-to-ban breach seen by a Moderator: keep the evidence, delete the content, give a 1-week time-out, and pass it to an Admin or the Owner in mod-log for the ban.

Hostile listings (DayZ): an Admin lists a player in #hostiles (only Admins post there) by in-game name and reason, and records it in mod-log and the player register. A listing ends after 2 weeks unless an Admin records a reason in mod-log to extend it, 2 weeks at a time. Players can give their view; the Admin decides on the evidence. An Admin can lift any listing, and a listing can be appealed like a sanction (section 7). A listed hostile may be killed on sight, but not at a fresh spawn. Only active listings are shown to players; the history stays in the player register. (The After's rule 4, approved by the Owner 2026-11-07; until then this proposed a players' vote by Discord poll after 2 weeks.)

Fights on Grundwela (Minecraft): for rule 3, admins use the Minecraft project's admin note on reading it, which sets what "first day" and "just respawned" mean and how an admin checks them.

Warnings older than 6 months don't count towards the next step. A game server ban uses that game's ban list; public lists show only the in-game name and the reason.

9. Records

Each mod-log line reads: <date> | <member> | <rule, LS-POL-002 section> | <step> | <by role> | <thread link>. Retention periods come from LS-REG-007.

10. Checking it works

At each quarterly management review: how many applications, reports, complaints and appeals there were; how many met the response targets; any overturned on appeal; and any pattern that needs a rule change. At the same time an Admin deletes what is past its period (section 9): application threads and messages whose last activity is over a year old; report, complaint and appeal cases closed over a year ago, wherever they are held (threads, direct messages, the Landsidu email inbox and the staff-only screenshot channel); and mod-log lines past their period. Each is logged by reference only (LS-REG-007).

Basis: decisions D10, D31 and D57 to D59 in the Landsidu decisions record; LS-REG-007 classes R1, R3, R4 and R11; the review of Discord's moderation guides of 2026-11-07.