Team Fortress 2 Classified Rule Enforcement Procedures

[- Alex - 36]

Team Fortress 2 Classified Rule Enforcement Procedures
Detailed Classified-Specific Punishment Ladders & Evidence
Public GGU moderation documentation — detailed procedure edition.

Classified-Specific Procedure:
Classified shares many general TF2 rules, but this detailed version intentionally retains the full Moderator-facing procedure because its unique spawn, arena, Engineer, and trade rules require concrete action sequences. Shared rules should stay synchronized with the main TF2 procedure.

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 SteamID and enough gameplay context for review.

Guillotine into Spawn Exploit

View Procedure

Procedure: Warn + Slay → Kick → Ban

Proof Required:

1. The warning telling the player to stop using the Guillotine exploit.
2. The slay applied after the warning was ignored.
3. The kick if the behavior continues.
4. The player's reconnect with SteamID/SteamID64 visible.
5. A demo/video showing the Guillotine entering spawn and actually damaging a player, as required by the live procedure.

Notes: The live procedure explicitly requires the Guillotine to damage a player. If previously banned for this offense, the existing procedure permits immediate banning.

Non-Melee Weapons in the Arena (Trade Servers)

View Procedure

Procedure: Warn + Slay → Kick → Ban

Proof Required:

1. The warning telling the player to stop using a non-melee weapon in the restricted arena.
2. The slay applied after the warning was ignored.
3. The kick if the behavior continues.
4. The player's reconnect with SteamID/SteamID64 visible.
5. A screenshot/demo clearly showing the non-melee weapon being used inside the restricted arena.

Notes: If previously banned for this offense, the existing procedure permits immediate banning.

Engineers Letting Enemy Spies into Spawn

View Procedure

Procedure: Warn + Destroy Exit → Kick → Ban

Proof Required:

1. The warning telling the Engineer to stop enabling enemy Spies to enter spawn.
2. Evidence that the offending teleporter exit was destroyed as the documented intermediate action.
3. The kick if the behavior continues.
4. The player's reconnect with SteamID/SteamID64 visible.
5. A demo/video showing the teleporter exit in spawn and the Engineer intentionally enabling the enemy Spy access.

Notes: This is a Classified-specific action and should remain explicit.

Enemy Spies Entering Spawn

View Procedure

Procedure: Warn + Slay → Kick → Ban

Proof Required:

1. The warning telling the Spy to leave/stop entering the protected spawn area.
2. The slay applied after the warning was ignored.
3. The kick if the behavior continues.
4. The player's reconnect with SteamID/SteamID64 visible.
5. A screenshot/demo clearly showing the enemy Spy inside the protected spawn area.

Notes: If previously banned for this offense, the existing procedure permits immediate banning.

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 exploit, the existing procedure permits immediate banning.

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 Classified Leadership when practical because new exploits can arise after game/map updates.

 

Communication Offenses

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.

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.

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: Bans are generally for repeat or prior-banned 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: Bans are generally for repeat or prior-banned 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.

Interrupting Trades on Voice Chat

View Procedure

Procedure: Warn → Mute → Ban

Proof Required:

1. The warning identifying the voice-chat trade interruption.
2. The mute applied if the player continues.
3. A demo/audio capture showing the player repeatedly interrupting an active trade discussion.
4. The player's identity or SteamID/SteamID64.
5. For a ban, include evidence of the repeat/prior pattern justifying escalation.

Notes: This is Classified-specific. A ban is normally for repeated behavior or prior punishment.

Non-English on Voice Chat

View Procedure

Procedure: Warn → Mute → Ban

Proof Required:

1. The warning telling the player to follow the current voice-language rule.
2. The mute applied after the warning was ignored.
3. A demo/audio capture showing continued non-English voice use after the warning.
4. The player's identity or SteamID/SteamID64.
5. Do not use this procedure unless the rule is confirmed as current.

Notes: Preserved from the live Classified procedure; review explicitly 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.

Drama / Stirring Conflict

View Procedure

Procedure: Warn → Silence → Ban

Proof Required:

1. The warning identifying the specific disruptive behavior.
2. The silence/mute/gag applied if it continues.
3. Screenshots/demo showing the actual provocation, harassment, baiting, or disruptive argument.
4. The player's identity or SteamID/SteamID64.
5. Enough context for Staff to understand why it qualifies as disruption rather than ordinary disagreement.

Notes: Avoid using the label without identifying the actual behavior.

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 Website

View Procedure

Procedure: Ban

Proof Required:

1. A screenshot/log showing the posted explicit URL or enough of it to identify the destination.
2. The player's identity or SteamID/SteamID64.
3. The surrounding message/context.
4. Store the URL/evidence in a restricted location rather than reposting explicit material publicly.

Notes: Post 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.

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 TF2 Classified Leadership / Staff because proof depends on the situation.

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 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: Bans are generally for repeated behavior or prior punishment.

 

Classified Moderator Checklist

• Confirm whether the rule is general TF2 or Classified-specific.
• For spawn/arena offenses, capture the prohibited location or interaction.
• For Engineer/Spy spawn issues, capture the teleporter/spawn context.
• For Guillotine abuse, show that it actually damaged a player in spawn.
• For progressive ladders, preserve each required action.
• Capture reconnect + SteamID where required.
• Submit the ban for Staff review.

 

Classified rules should be concrete enough that two Moderators can follow the same process.