Leaderboard

Ima make this short and sweet. Ducky you shouldnt have messed with destroyer by calling him shit mod because of the situation, especially during the situation he probably didnt see it as a joke. Destroyer you shouldn't have pmuted ducky right away especially since you didnt even give him a prior warning before the mute. That was totally excessive. Behave Ducky and Destroyer make sure to warn players before punishing them.

Ey yo whats poppin, I'm Angel. I'm a new recruit, I've been playing on the CSS Death Match server for a little over a year. I like memes, and cats, and memes and about cats.

Who here is a musician? I play the piano, clarinet, and some trumpet.

Thank you!!

We thank you for your donation to helping and supporting the community LOBO!

Hello, On the server when it first starts I think the bots need to be on the easier side and work up harder (you might be working on this as we type) I noticed a couple of times while playing it would start out with 3-4 level bots and random people would join then leave after the first round of playing because the difficulty was to high. Just an idea to think about.

Welcome!!!!!

YO YO YO! WElcome to HG Angel! GLad your part of the coooooooooooooool kids

Team Fortress 2 Rule Enforcement Procedures Official Procedures for Moderating HG TF2 Servers Important Note: It is an admin's job to help make the server a fun and playable environment/experience. This is the most important and foremost factor that admins should keep in mind while moderating. Admins are not here to lash out at players and have fun punishing them. Please use discretion and leniency when enforcing these rules and following these procedures. Any action by an admin should be for the betterment of the server/community. Examples: If someone briefly makes a noise on the mic by accident, it is unnecessary to warn them for micspam. We punish players for micspamming when it is disrupting the server or trade environment (e.g. playing music disrupts the use of voice chat and trades). If someone's mic quality isn't the greatest but it's tolerable and players are not complaining, it is not necessary to punish them for micspam. If someone accidentally sends two trade advertisements on an occasion, it is not necessary to punish them for chat spam (do so on repeat or obnoxious offenses). If you warn someone for micspamming, give them a moment to read the warning and stop—do not immediately mute them. In addition, give players the chance to recognize a mistake they've made. For example, if someone accidentally talks over another person and genuinely apologizes, it's clear we do not need to punish them for micspam on that occasion (do so on repeat or obnoxious offenses). Give players a chance to acknowledge their warning and reiterate it if you don't think they saw it. Always take into account the current and always-changing server-gameplay environment. Our rules are in place to make the server the best it can be and attract the most players we can have in the best playable game environment. Miscellaneous Offenses Inappropriate Spray Procedure: Warn + Remove Spray → Remove Spray + Kick → Ban Proof Required: Screenshots (preferred) or demo(s) of: Warning Spray removal Kick Player reconnect with SteamID Inappropriate spray (Note: This must be screenshotted. Sprays are not shown in demos for anyone that was not on the server at the time of it being sprayed as sprays are stored in a local client cache). Notes: Please add the proof in a separate reply to the ban so that leadership may hide it. Impersonation Procedure: Warn → Kick → Ban Proof Required: Screenshots (preferred) or demo(s) of: Warning Kick Player reconnect with SteamID Scamming Procedure: Ban Proof Required: Screenshots or demo(s) of: Dependent upon the situation, speak with TF2 Leadership. Trolling or Disrupting Gameplay Procedure: Warn → Mute/Gag/Kick → Ban Proof Required: Screenshots or demo(s) of: Warn Mute, gag, or kick Trolling/gameplay disruption Notes: For a communication offense: A ban will only occur with this offense if the player has already been banned for it (such as with avoiding punishment) or repeatedly gets on and disrupts/trolls until they are punished each session. Unsolicited/Random Trades Procedure: Warn → Kick → Ban Proof Required: Screenshots or demo(s) of: Warn Kick Random trade Notes: A ban will only occur with this offense if the player has already been banned for it or repeatedly gets on and commits this offense until they are warned/kicked each session. Communication Offenses Avoiding Punishment Procedure: Ban Proof Required: Screenshots (preferred) or demo(s) of: Initial warning Initial gag, mute, or silence Player disconnect with SteamID Player reconnect with SteamID Notes: Exception: If the person uses name changes to continue to communicate to bypass a gag/mute/silence, use sm_namelock. This prevents them from further changing their name. Micspam Procedure: Warn → Mute → Ban Proof Required: Screenshots and/or demo(s) of: Warn Mute Micspam Notes: A ban will only occur with this offense if the player has already been banned for it (such as with avoiding punishment) or repeatedly gets on and micspams until they are muted each session. Chatspam Procedure: Warn → Gag → Ban Proof Required: Screenshots (preferred) or demo(s) of: Warn Gag Chatspam Notes: A ban will only occur with this offense if the player has already been banned for it (such as with avoiding punishment) or repeatedly gets on and chatspams until they are muted each session. Usage of Racial Slurs or other Hate Speech Procedure: Warn → Silence → Ban Proof Required: Screenshots or demo(s) of: Warn Silence Usage of racial slurs or other hate speech Notes: A ban will only occur with this offense if the player has already been banned for it or repeatedly gets on and commits this offense until they are silenced each session. If a player rapidly spams this, ban them immediately. Interrupting Trades on Voice Chat Procedure: Warn → Mute → Ban Proof Required: Screenshots or demo(s) of: Warn Mute Trade interruption Notes: A ban will only occur with this offense if the player has already been banned for it or repeatedly gets on and commits this offense until they are muted each session. Non-English on Voice Chat Procedure: Warn → Mute → Ban Proof Required: Screenshots and/or demo(s) of: Warn Mute Non-English on voice chat Notes: A ban will only occur with this offense if the player has already been banned for it or repeatedly gets on and commits this offense until they are muted each session. Player Disrespect/Harassment Procedure: Warn → Silence → Ban Proof Required: Screenshots or demo(s) of: Warn Silence Player disrespect or harassment Notes: A ban will only occur with this offense if the player has already been banned for it or repeatedly gets on and commits this offense until they are silenced each session. Drama/Stirring Conflict Procedure: Warn → Silence → Ban Proof Required: Screenshots or demo(s) of: Warn Silence Drama/stirring conflict Notes: A ban will only occur with this offense if the player has already been banned for it or repeatedly gets on and commits this offense until they are silenced each session. Advertising Another Server/Community Procedure: Warn → Silence → Ban Proof Required: Screenshots or demo(s) of: Warn Silence Advertisement of another server/community Notes: A ban will only occur with this offense if the player has already been banned for it or repeatedly gets on and commits this offense until they are silenced each session. If a player puts an IP address of another non-HG server, ban them immediately. Linking a Pornographic Website Procedure: Ban Proof Required: Screenshots or demo(s) of: Chat entry or voice chat including the pornographic link. Notes: Please add the proof in a separate reply to the ban so that leadership may hide it. Game & Server Exploit Offenses Usage of Cheats, Aimbots, Aim-Assistants, etc. Procedure: Ban Proof Required: Demo(s) of cheat usage, aim-assistant, aimbot, etc. Please use HG Observe (sm_observe) during the demo so that we can see the SteamID and any hits/damage they give or take. Portal Glitching Procedure: Warn + Slay → Kick → Ban Proof Required: Screenshots and/or demo(s) of: Warn Slay Kick Player reconnect with SteamID Portal glitching Notes: If they have been previously banned for this, immediately ban them. Guillotine into Spawn Exploit Procedure: Warn + Slay → Kick → Ban Proof Required: Screenshots and/or demo(s) of: Warn Slay Kick Player reconnect with SteamID Guillotine glitching (must damage a player) Notes: If they have been previously banned for this, immediately ban them. Non-melee Weaponry in the Arena Procedure: Warn + Slay → Kick → Ban Proof Required: Screenshots and/or demo(s) of: Warn Slay Kick Player reconnect with SteamID Non-melee weaponry in the arena Notes: If they have been previously banned for this, immediately ban them. Engineers Letting Enemy Spies into Spawn Procedure: Warn + Destroy Exit → Kick → Ban Proof Required: Screenshots and/or demo(s) of: Warn Destroy Kick Player reconnect with SteamID Teleporter exit in spawn Notes: If they have been previously banned for this, immediately ban them. Enemy Spies Entering Spawn Procedure: Warn + Slay → Kick → Ban Proof Required: Screenshots and/or demo(s) of: Warn Slay Kick Player reconnect with SteamID Enemy spy in spawn Notes: If they have been previously banned for this, immediately ban them. Point Farming (GameME) Procedure: Warn + Slay → Kick → Ban Proof Required: Screenshots and/or demo(s) of: Warn Slay Kick Player reconnect with SteamID Point farming Notes: If they have been previously banned for this, immediately ban them. If the point farming is severe enough or discovered via logs, this may result in an immediate permanent ban. This is at leadership's discretion. General Minor Server/Map Exploits (does not break gameplay) Procedure: Warn + Slay → Kick → Ban Proof Required: Screenshots and/or demo(s) of: Warn Slay Kick Player reconnect with SteamID Minor exploit Notes: If they have been previously banned for this, immediately ban them. Major Server/Map Exploits (breaks gameplay) Procedure: Ban Proof Required: Screenshots and/or demo(s) of: Major Exploit Notes: More often than not, consult TF2 Leadership prior to banning as exploits are often situational and arise suddenly with game updates. Credits to: Imperial Knight, Misc2008 and reploidzerox