Unturned Rule Enforcement Procedures

[- Alex - 36]

Unturned Rule Enforcement Procedures
Detailed Unturned Punishment Ladders, Base Actions & Evidence
Public GGU moderation documentation — detailed procedure edition.

How to Use This Procedure:
This edition intentionally keeps Unturned-specific actions such as base destruction, owner checks, loot-spawn enforcement, and long-duration raid bans. Those operational details are why this procedure exists separately from the Global Standard.

How to Read “Proof Required”:
Each checklist describes the minimum evidence a Moderator should submit for that offense. A complete submission should prove the player’s identity, the underlying rule violation, and each required escalation step that occurred before the ban. If a listed step was skipped because an immediate-ban exception applies, the evidence should make that exception clear.

 

Game & Server Exploit Offenses

Usage of Cheats, Aim-bot, etc.

View Procedure

Procedure: Ban

Proof Required:

1. A demo or video that clearly shows the suspicious gameplay from enough angles/time to evaluate it.
2. The accused player's SteamID/SteamID64 or other unique account identifier.
3. At least one clear example of the behavior that supports the cheat allegation; do not submit only a scoreboard or a verbal accusation.
4. If possible, include the incident timestamp/map so Staff can compare server logs.

Notes: Preserve the player's SteamID and the strongest available server/OpenMod evidence.

General Minor Server / Map Exploits (Does Not Break Gameplay)

View Procedure

Procedure: Warn + Slay → Kick → Ban

Proof Required:

1. The original warning, showing which player was warned and what exploit they were told to stop.
2. The slay, showing the same player was punished after ignoring the warning.
3. The kick, showing the same player continued after the slay.
4. The player's reconnect with SteamID/SteamID64 visible so the reconnect is tied to the same person.
5. A screenshot/demo showing the actual exploit being performed. The punishment commands alone are not enough.

Notes: If previously banned for the same exploit, the existing procedure permits an immediate ban.

Major Server / Map Exploits (Breaks Gameplay)

View Procedure

Procedure: Ban

Proof Required:

1. A screenshot/demo clearly showing the exploit being performed.
2. Enough surrounding gameplay to show why the exploit materially breaks or bypasses normal gameplay.
3. The player's SteamID/SteamID64.
4. The map/server and approximate time of the incident.

Notes: Consult Unturned Leadership when practical because exploits can be situational and may change after game/plugin updates.

 

Communication Offenses

Asking Staff to Spawn Items / Vehicles

View Procedure

Procedure: Warn → Mute → Kick → Ban

Proof Required:

1. The initial warning telling the player to stop asking Staff to spawn items/vehicles.
2. The mute showing the same player continued after the warning.
3. The kick showing the same player continued after the mute.
4. The player's reconnect with SteamID/SteamID64 visible.
5. At least one screenshot/demo of the actual repeated request so Staff can verify the underlying offense.

Notes: Keep this only if current Unturned rules still treat repeated requests for spawned items/vehicles as punishable.

Doxing / Illegal Activities

View Procedure

Procedure: Ban

Proof Required:

1. A screenshot/demo containing the actual message or voice content.
2. The sender/speaker identity visible or otherwise clearly attributable.
3. The target/context needed to understand the threat or disclosure.
4. For personal information, store the evidence in a restricted location rather than reposting it publicly.

Notes: Keep sensitive evidence restricted.

DDoS Threats

View Procedure

Procedure: Ban

Proof Required:

1. A screenshot/demo containing the actual DDoS threat.
2. The sender/speaker identity visible or clearly attributable.
3. The approximate time/server/channel of the threat.
4. Any follow-up context that shows whether the threat was directed at GGU, a player, or infrastructure.

Notes: Escalate credible threats.

Avoiding Punishment

View Procedure

Procedure: Ban

Proof Required:

1. The original warning or moderation instruction.
2. The active gag, mute, silence, or other punishment being evaded.
3. The player's disconnect with SteamID/SteamID64 visible.
4. The reconnect with SteamID/SteamID64 visible.
5. Evidence that the reconnect/alternate identity was used to continue the same prohibited behavior or bypass the active punishment.

Notes: Show that the reconnect or identity change was used to evade the active punishment.

Mic-Spam

View Procedure

Procedure: Warn → Mute → Ban

Proof Required:

1. The warning telling the player to stop mic-spam.
2. The mute applied after the warning was ignored.
3. A demo/video/audio capture that actually contains the mic-spam.
4. The player's identity or SteamID/SteamID64.
5. For a ban, include evidence of the prior/repeated pattern that justifies escalation beyond the mute.

Notes: A ban is normally for prior bans or repeated session-by-session behavior.

Chat-Spam

View Procedure

Procedure: Warn → Gag → Ban

Proof Required:

1. The warning telling the player to stop chat-spam.
2. The gag applied after the warning was ignored.
3. Screenshots/logs showing the repeated spam messages.
4. The player's identity or SteamID/SteamID64.
5. For a ban, include evidence of the prior/repeated pattern that justifies escalation beyond the gag.

Notes: A ban is normally for prior bans or repeated session-by-session behavior.

Racial Slurs / Hate Speech

View Procedure

Procedure: Warn → Silence → Ban

Proof Required:

1. The warning, unless the conduct qualifies for the documented immediate-ban exception.
2. The silence/mute/gag applied after the warning was ignored.
3. A screenshot/demo showing the actual slur or hate-speech content.
4. The player's identity or SteamID/SteamID64.
5. For an immediate ban based on rapid spam, capture enough consecutive messages/voice content to show the rapid repeated behavior.

Notes: The existing procedure permits immediate banning for rapid spam.

Non-English on Voice / In-Game Chat

View Procedure

Procedure: Warn → Mute → Ban

Proof Required:

1. The warning telling the player to use the language required by the current server rule.
2. The mute applied after the warning was ignored.
3. A screenshot/demo showing the continued voice/chat behavior after the warning.
4. The player's identity or SteamID/SteamID64.
5. Do not use this procedure unless the rule is confirmed as current for the server.

Notes: Preserved from the current procedure and should be explicitly reviewed before changing.

Player Disrespect / Harassment

View Procedure

Procedure: Warn → Silence → Ban

Proof Required:

1. The warning identifying the conduct that must stop.
2. The silence/mute/gag applied if the behavior continues.
3. Screenshots/demo showing the actual disrespect/harassment, including enough surrounding context to understand who was targeted and what occurred.
4. The player's identity or SteamID/SteamID64.
5. For a ban, include the repeat pattern or prior punishment supporting escalation.

Notes: Use context and severity when deciding whether faster escalation is justified.

Drama / Causing Conflict

View Procedure

Procedure: Warn → Silence → Ban

Proof Required:

1. The warning identifying the specific disruptive behavior—not merely the word 'drama'.
2. The silence/mute/gag applied if the conduct continues.
3. Screenshots/demo showing the actual conduct: e.g. repeated baiting, targeted provocation, harassment, or disruptive argument.
4. The player's identity or SteamID/SteamID64.
5. Enough surrounding context for Staff to understand why the conduct was disruptive.

Notes: Do not use the label alone as proof.

Advertising Another Server / Community

View Procedure

Procedure: Warn → Silence → Ban

Proof Required:

1. The warning, unless the current procedure allows an immediate ban for direct server-IP advertising.
2. The silence/mute/gag applied if the player continues.
3. A screenshot/demo showing the actual advertisement, recruitment message, invite, or server IP.
4. The player's identity or SteamID/SteamID64.
5. For an immediate ban, capture the full message containing the non-GGU server IP or other qualifying content.

Notes: The existing procedure permits immediate banning for posting another non-GGU server IP.

Linking an Explicit / Malicious Website

View Procedure

Procedure: Ban

Proof Required:

1. A screenshot/log showing the actual posted link or enough of the URL to identify it.
2. The player's identity or SteamID/SteamID64.
3. The surrounding message/context showing who posted it and where.
4. Store explicit, phishing, malware, or otherwise sensitive URLs in restricted evidence; do not repost them publicly.

Notes: Post proof in a restricted reply/evidence location.

 

Base, Building & World Offenses

Stealing Items / Claim-Flag-Related Base Action — Legacy Entry

View Procedure

Procedure: Warn → Base Destruction

Proof Required:

1. The warning given to the responsible player, if the legacy rule requires a warning before action.
2. Screenshots/video of the affected base and the relevant claim flags.
3. An owner check showing the SteamID/SteamID64 associated with the base/structures.
4. Evidence showing the conduct that triggered the base-destruction action.
5. Because the legacy entry is ambiguous, do not use this exact procedure until Unturned Leadership confirms what offense it is intended to cover.

Notes: The live 2022 source labels this entry 'Stealing Items' but its proof and punishment are base/claim-flag oriented. The intended rule must be identified before final publication.

Blocking Roads (Bases / Barricades)

View Procedure

Procedure: Base / Barricade Destruction

Proof Required:

1. Screenshots/video showing the road is actually blocked by the base/barricades.
2. An owner check showing the SteamID/SteamID64 responsible for the blocking structures.
3. The location/road being blocked so Staff can identify the affected area.
4. Screenshots taken before destruction so the reason for removing the build remains reviewable.

Notes: Capture the obstruction clearly before destruction so the owner and reason remain reviewable.

Blocking Loot Spawns

View Procedure

Procedure: Warn → Ban + Base / Barricade Destruction

Proof Required:

1. The warning telling the owner to remove the blocking structure/items.
2. An owner check showing the responsible SteamID/SteamID64.
3. Screenshots/video showing exactly how the base/items block the loot spawn.
4. The location/loot spawn being affected.
5. For a ban after the grace period, proof that the warning period expired and the blocking structure remained.

Notes: The existing procedure says to ban 48 hours after the warning if ignored. Confirm that the 48-hour grace period remains current.

Raiding Fully Built Bases

View Procedure

Procedure: Ban — 2 Months

Proof Required:

1. Screenshots/video showing the accused player actively raiding the protected/fully-built base.
2. Evidence showing the base qualifies as protected under the current Unturned rule.
3. Screenshots/inventory/log evidence of the items taken where available.
4. The accused player's SteamID/SteamID64.
5. The base owner/ownership context and approximate incident time.

Notes: The 2-month duration is preserved from the live procedure and should be verified before final publication.

 

Miscellaneous Offenses

Stealing Items

View Procedure

Procedure: Warn → Kick → Ban

Proof Required:

1. The warning given to the player.
2. The kick if the player continues after the warning.
3. The player's reconnect with SteamID/SteamID64 visible if they return and continue.
4. Screenshots/video/logs showing the actual item theft.
5. Ownership/storage context showing why the items were not legitimately available to the accused player.

Notes: The live procedure contains this second 'Stealing Items' entry with a different ladder. The duplicate must be resolved by Unturned Leadership.

Impersonation

View Procedure

Procedure: Warn → Kick → Ban

Proof Required:

1. The warning telling the player to stop impersonating another person/role.
2. The kick if the impersonation continues.
3. The player's reconnect with SteamID/SteamID64 visible if they return and continue.
4. Evidence showing both the impersonating identity and the real person/role being impersonated.
5. Enough context to show the impersonation was misleading or disruptive rather than a harmless similar name.

Scamming

View Procedure

Procedure: Ban

Proof Required:

1. Screenshots/demo showing the offer, agreement, or transaction terms.
2. Evidence showing what each party actually gave/received, where available.
3. Chat/trade/inventory records that demonstrate the alleged deception.
4. The accused player's SteamID/SteamID64.
5. Any Staff/Leadership context needed to explain why the situation qualifies as a scam.

Notes: Speak with Unturned Leadership / the reviewing Staff member because proof depends heavily on the transaction.

Trolling / Disrupting Gameplay

View Procedure

Procedure: Warn → Mute / Gag / Kick → Ban

Proof Required:

1. The warning identifying the disruptive behavior.
2. The intermediate mute/gag/kick used if the player continues.
3. A demo/video/screenshots showing the actual trolling or gameplay disruption.
4. The player's identity or SteamID/SteamID64.
5. For a ban, include evidence of prior/repeated behavior or the session-to-session pattern justifying escalation.

Notes: For communication-based trolling, bans are generally for repeat behavior or prior punishment.

Unsolicited / Random Trades

View Procedure

Procedure: Warn → Kick → Ban

Proof Required:

1. The warning telling the player to stop unsolicited/random trade requests.
2. The kick if the behavior continues.
3. Screenshots/demo showing the repeated unsolicited/random trade behavior.
4. The player's identity or SteamID/SteamID64.
5. For a ban, include evidence of prior/repeated behavior after earlier warnings/kicks.

Notes: The existing procedure generally reserves bans for repeated behavior or prior punishment.

 

Unturned Evidence Checklist

• SteamID/player identity.
• Timestamp or incident window.
• Screenshots/video where visual context matters.
• OpenMod/server logs where they materially support the case.
• Owner check for base/barricade actions.
• Claim flags or ownership context where relevant.
• Items/structures involved in the offense.
• Required warning/kick/mute evidence for progressive ladders.

 

Use the server data, preserve ownership context, and document destructive actions.