Team Fortress 2 Rule Enforcement Procedures

[- Alex - 36]

Team Fortress 2 Rule Enforcement Procedures
Detailed TF2 Punishment Ladders, Evidence & Moderator Actions
Public GGU moderation documentation — detailed procedure edition.

How to Use This Procedure:
This document preserves the operational detail of the long-standing TF2 procedure: each offense has a specific escalation path, required proof, and rule-specific notes. The Global Moderation Standard governs evidence integrity, appeals, conflicts, and Leadership review; this document tells a TF2 Moderator what to actually do.

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 or SourceTV records.

Notes: Preserve the strongest available demo/video evidence and the player's SteamID. If evidence is uncertain, escalate for Staff review rather than stretching weak proof.

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 the player has previously been 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 TF2 Leadership when practical before finalizing a ban. Exploits can be situational and may appear after TF2 or map 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: Preserved from the existing TF2 procedure. If this no longer has a meaningful TF2 context, retire or rename it rather than leaving dead policy.

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 out of public view.

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: Preserve identity and timestamp context.

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: The evidence should show that the reconnect or alternate action was actually used to evade an 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 reserved 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 reserved 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 when the player rapidly spams this content.

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 existing TF2 procedure. GGU should explicitly decide whether this remains a current rule and what moderation problem it is intended to solve.

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: A ban is generally for repeat conduct, prior punishment, or severe conduct warranting faster escalation.

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; document the actual disruptive conduct.

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. Clarify whether the current rule targets unsolicited recruitment, direct IP advertising, or all mentions.

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: Place sensitive proof in a restricted reply/evidence location.

 

Miscellaneous Offenses

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.

Notes: Capture the identity being impersonated and enough context to show deception or disruption.

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: The old TF2 procedure incorrectly referred to Unturned Leadership. This should be reviewed by TF2 Leadership / the appropriate TF2 Staff reviewer.

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 conduct, prior punishment, or repeated session-by-session disruption.

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 a ban for repeat conduct or prior punishment.

 

Moderator Ban Submission Checklist

• Player name and SteamID are correct.
• The offense matches the current TF2 rules.
• All proof required by the specific procedure is attached.
• Evidence includes the offense itself, not only punishment commands.
• Reconnect + SteamID are shown when the ladder requires them.
• Sensitive links or personal information are placed in restricted evidence.
• Staff is notified for review.

 

Follow the rule. Capture the proof. Make the action reviewable.