Jump to content

- Alex -

Community Leader
  • Posts

    511
  • Joined

  • Last visited

  • Days Won

    36
  • Donations

    0.01 USD 
Community Hub Profile

- Alex -

@alexthunderhunter

Open Community Hub

I develop stuff

Discord Level 19 Steam Accounts 2 Wizards 4 Achievements 8

Everything posted by - Alex -

  1. Welcome back to the GGU Staff team!

  2. If anyone is interested in joining GGU via Wizard101 lmk so we can create the clan in game (Need 11 "friends" online).
  3. Welcome back to the GGU Leadership Team!

  4. Welcome to the GGU Development Team!

  5. Welcome to GGU and the GGU Development Team!

  6. Welcome to GGU!

  7. Team Fortress 2 Rule Enforcement Procedures These guidelines are followed by Mods when a rule is broken. Please note that the rules outlined below are only guidelines. Mods may not follow them in some cases. It is important to remember we have rules to keep the server fun and enjoyable for all. GGU Leadership is here to help. Game & Server Exploit Offenses Usage of Cheats, Aim-bot, etc. Procedure: Ban Proof Required: Demo(s) of cheat usage, aim-bot, etc. 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 Weapons in the Arena (Trade Servers) 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. 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. Communication Offenses Doxing/Illegal Activities Procedure: Ban Proof Required: Screenshots (preferred) or demo(s) of: Chat entry or voice chat including the threat of Doxing/Illegal Activities. DDoS Threats Procedure: Ban Proof Required: Screenshots (preferred) or demo(s) of: Chat entry or voice chat including the DDoS threat. 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 Mic-spam Procedure: Warn ➦ Mute ➦ Ban Proof Required: Screenshots and/or demo(s) of: Warn Mute Mic-spam 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. Chat-spam Procedure: Warn ➦ Gag ➦ Ban Proof Required: Screenshots (preferred) or demo(s) of: Warn Gag Chat-spam 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 chat-spams until they are gagged 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-GGU server, ban them immediately. Linking an Explicit Website Procedure: Ban Proof Required: Screenshots or demo(s) of: Chat entry or voice chat including the explicit link. Notes: Please add the proof in a separate reply to the ban so that leadership may hide it. Miscellaneous Offenses 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.
  8. Welcome to Development team!

  9. Welcome to the GGU Design Team!

  10. Welcome to the GGU Outreach Team!

    1. brgr.

      brgr.

      Thank you thank you

    2. TyGuy464646

      TyGuy464646

      Congrats buttercup 😉

  11. Welcome to GGU!

  12. Welcome to GGU!

  13. Welcome to the GGU Mod team!

  14. I'll have the Unturned Leadership team look into the issue.
  15. Forum Guidelines Enforcement Procedures IPS Warning Points, Expirations & Forum Restrictions Public GGU moderation documentation — IPS warning-point enforcement model. Public Enforcement Standard: GGU publishes its Forum enforcement framework so members can understand how warning points and restrictions are applied. Private reports, sensitive evidence, and Staff-only notes may remain restricted. GGU Forums use the IPS warning-point system. Forum enforcement should therefore be recorded through warning points, point expirations, and the moderation/restriction options attached to those warnings rather than through an unrelated generic punishment ladder. How the IPS Warning-Point System Is Used Warning Points record the severity and history of a Forum rule violation. Expiration determines how long the points remain active for escalation and automated/manual restrictions. Content Moderation may require a member's future content to be approved before it becomes publicly visible. Posting Restrictions may prevent the member from posting until the restriction expires or is successfully appealed. Spammer Status may be used for qualifying spam behavior. Zero-Point Warnings may be used when GGU intentionally wants an administrative record without adding active warning points. Point Values Matter: Do not replace a point-based offense with a generic warning unless the Forum policy is intentionally being changed. The points, expiration, and attached restriction are part of the enforcement action. General Forum Moderation Process Identify the specific Forum rule that was violated. Preserve the relevant post/topic and surrounding context. Confirm whether the member has prior active/relevant warnings when the procedure uses escalating offenses. Issue the warning using the point value and expiration listed for the applicable offense. Apply the content action and any moderation/posting restriction required by the offense level. Record a clear reason so another authorized reviewer can understand the action. Escalate unusual, disputed, or severe cases when appropriate. Advertising 1st Offense: 10 warning points, expiring after 3 months; hide/remove the advertising content. 2nd Offense: 150 warning points, expiring after 1 year; place the member's content under moderation for that duration. 3rd Offense: 150 warning points, expiring after 1 year; restrict the member from posting until successfully appealed or otherwise reviewed. Evidence / Record: preserve the advertising post, link, invite, server IP, recruitment message, or other content that triggered the warning. Doxing 1st Offense: 8000 warning points and restrict the member from posting. Evidence / Record: preserve the original content in a restricted location. Do not repeat personal information publicly in the warning reason. Sensitive Evidence: Doxing evidence should be hidden from public view while remaining available to authorized Leadership. Forum Alternate Accounts 1st Offense: close the alternate account. The existing procedure requires Senior Manager+ authority. Under the current GGU hierarchy, Senior Manager+ includes Senior Manager, Operations Leader, Community Leader, and Owner. Identity should be reasonably verified before account closure. Harassment, Slurs & Discrimination 1st Offense: 10 warning points per instance, expiring after 6 months; hide/remove the content and place future content under moderation for that duration. 2nd Offense: issue 3× the points assessed for the 1st offense, expiring after 1 year; hide/remove the content and restrict posting until successfully appealed or otherwise reviewed. Evidence / Record: preserve the offending content and enough surrounding context to identify the target, conduct, and number of distinct instances being counted. Malicious Links 1st Offense: 8000 warning points and restrict the member from posting. Evidence / Record: preserve the post and URL in a restricted location. Do not repost malware, phishing, credential-stealing, or otherwise dangerous links in public Staff notes. Necroposting 1st Offense: 0 warning points; lock the thread where appropriate. This warning is used strictly as an administrative record. 2nd Offense: 10 warning points, expiring after 1 month. 3rd Offense: 150 warning points, expiring after 1 year; place the member's content under moderation for that duration. Use Judgment: Not every reply to an old topic is harmful. Apply necroposting enforcement when reviving the thread is actually contrary to current Forum rules or materially disrupts the Forum. Spamming 1st Offense: warning points are based on the content/severity of the spam; points expire after 1 month; hide/remove the spam. 2nd Offense: issue 3× the warning points and duration used for the 1st offense; hide/remove the content, flag the account as a spammer where appropriate, and moderate future content for the issued duration. 3rd Offense: issue 3× the points and duration used for the 2nd offense; hide/remove the content and restrict posting until successfully appealed or otherwise reviewed. Evidence / Record: preserve representative spam content and enough context to show frequency/volume. For automated or malicious spam accounts, faster action may be appropriate under the Global Moderation Standard. "Shitposting" / Low-Value Content Offenses 1–3: 0 warning points, expiring after 1 month; hide or move the posts as appropriate. 4th+ Offense: 10 warning points, expiring after 3 months; hide or move the posts. Evidence / Record: preserve or reference the affected posts so the pattern can be reviewed. Moving content may be more appropriate than hiding it when the problem is location rather than misconduct. Content Actions Hide content when it violates rules but may be needed for Staff review. Move content when the primary problem is that it belongs elsewhere. Lock a thread when further replies should stop. Delete permanently only when preservation is unnecessary and authorized. Preserve Reviewability: When in doubt, hide rather than permanently delete. IPS moderation history is more useful when the underlying content can still be reviewed by authorized Staff. Automatic vs. Manual Restrictions IPS may apply restrictions through the warning configuration, while Leadership may also attach or review restrictions manually. The Forum procedure should describe the intended outcome; the IPS warning configuration should be kept aligned with that policy. Point Expiration Expiration is part of the punishment. A warning should use the duration listed in the procedure unless an approved exception applies. Expired points may remain historically visible to Staff even though they are no longer active. Escalation & Appeals Moderators should not alter point values simply to reach a preferred outcome. Unusual cases may be escalated to Staff/Manager or higher Leadership. Appeals should be reviewed by someone with appropriate authority. A reviewer may correct an incorrect warning, point value, expiration, or attached restriction. Reports involving higher Leadership should follow the normal GGU escalation chain, including Operations Leader where applicable. Point-System Maintenance The written procedure and the IPS warning configuration should be reviewed together. If GGU changes a point value, expiration period, or automated restriction in IPS, this public procedure should be updated at the same time so members and Staff see the same enforcement model. Use the point system consistently and keep the written policy aligned with IPS.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.