[9000] - Discord PUG Rules⚓︎
Discord PUGs are an official part of the league, so all league rules (e.g. - offensive language and map exploits) apply and punishments may carry over.
[9000.1] - Respect⚓︎
Players should be respectful to everyone and avoid excessive bad manners, trash talk, or harassment of others. Constructive criticism is allowed but shouldn’t make teammates feel unwelcome.
| What IS Allowed | What ISN'T Allowed |
|---|---|
| Inoffensive light-hearted banter and constructive criticism or suggestions | Excessive BM or trash talk through text or voice |
| Focusing critical classes that your team is struggling to counter | Focusing specific players, independent if it’s beneficial to your team, for harassment or tilting the other player - also referred to as “Big game hunting” |
| Taunting after impressive plays | Taunting after every kill |
| Requesting a substitute for yourself or another player if they request someone to sub for them | Requesting a substitute for an active player who is following rules to get a different player in their place |
[9000.2] - Communication⚓︎
Players should exhibit good teamwork through communication and cooperation. While the game is active, remain undeafened to hear teammates. Use voice chat for communication unless there's a valid reason, and avoid mic spam. English should be used in PUGs for effective communication and moderation.
| What IS Allowed | What ISN'T Allowed |
|---|---|
| Deafening in pre-games | Deafening while rounds are active |
| Adjusting other players’ voice volume to be quieter | Completely muting certain players |
[9000.3] - Class Flexibility⚓︎
Due to the nature of PUGs, you may not always get the class you want. Be flexible and prepared to try out other classes. In particular, if an inexperienced player cannot reliably play more than one class, please try to be flexible with your class selection to accommodate them. In website PUGs, class swapping IS NOT allowed unless permitted by a PUG admin.
| What IS Allowed | What ISN'T Allowed |
|---|---|
| Queueing as a single class | Being picked for one class in captained pugs but playing a different one in-game |
| Asking a PUG admin for permission to class swap if a sub spot is hard to fill or both captains agree. | Class swapping without being given permission |
[9000.4] - Griefing⚓︎
Players are expected to take PUGs seriously enough to ensure other players in the PUG have fun. You should be attempting to fulfill your class’s role, no matter the score. Throwing and memeing in PUGs are not allowed. As a general rule, we strive to have PUGs be as close to actual scrims and matches as possible. Scenarios are at the discretion of PUG admins and asking for clarification is highly encouraged.
| What IS Allowed | What ISN'T Allowed |
|---|---|
| Running loadouts that have an established meta but may not be the most popular choice | Using non-competitive loadouts that deny your class to be able to fulfill its role |
| Running shotgun soldier or occasionally going for market gardener kills when appropriate but using your rocket launcher for primary damage | Running market gardener as your primary damage/kill method |
| Running loch-n-load or loose canon but still denying space and providing damage with stickies. | Running demoknight where you can’t provide the needed damage output or space denial |
| Running natascha to deny soldiers or scouts | Being a friendly heavy or creating truces by intentionally not attacking specific players of the other team. |
| Running level 3s on KOTH that actively denies soldier bombs or combat areas. You may actively build level 3 sentries near spawn, but it must be moved to the front line at the next opportunity. | Keeping level 3s in spawn areas when not at risk of being spawn camped for the majority of the game |
| Prioritizing healing certain classes over others but still providing heals to all players as needed | Refusing to heal certain players when requested or only healing with arrows without prioritizing ubercharge |
| Being forced to use uber charges to prevent dropping or at the end of rounds to prevent losing. Only occasionally and strategically ubering certain loadouts including widowmaker engineers or kritzing heavies. | Providing charges to non-meta classes when much better alternatives are available. For example, ubering rescue ranger engineers or spies over demoman, heavy, scout, or soldier. |
| Edging point capture to take advantage of spawn waves | Deliberately not capturing the point to make the PUG end sooner or manipulate Elo |
[9000.5] - PUG Readiness⚓︎
Players should be prepared to play with no guaranteed spot or team preference once in the queue. Avoid leaving PUGs due to dissatisfaction with teams or adding up if unable to finish. In emergencies, inform the current PUG Runner promptly, but try to be mindful.
[9000.6] - Running Discord PUGs⚓︎
Only PUG Runners may run PUGs. This includes not only hosting PUGs but also sorting teams, handling moderation, pausing or unpausing games, etc. If you have any concerns, please direct message the RGL Robo-Pug Bot on the RGL Discord and the PUG Runner will handle the situation.
[9000.7] - Ban Discussion⚓︎
PUGs and its chat are not places to discuss RGL bans or conduct violations as this may lead to arguments and interfere with the flow of PUGs. PUG admins discuss all bans internally. If you have any PUG conduct violations to report, please fill out a report form on the PUG site by clicking on the user and include as much information and evidence as possible.
[9000.8] - Leaving a Game⚓︎
By requesting a sub for yourself, you will be restricted from adding up for 90 minutes. If this is done by mistake, please open a support ticket in the RGL Discord or contact a PUG admin. While emergencies happen, substitutions are logged and you may be manually banned for longer if you consistently sub yourself out.
[9000.9] - Multiple Offenses & Ban Lengths⚓︎
By default, your first offense will result in a warning, with additional offenses that may induce the following:
- 1st Offense: Warning
- 2nd Offense: 24hr PUG ban
- 3rd Offense: 72hr PUG ban
- 4th Offense: 1 week PUG ban
- 5th Offense: 1+ month PUG ban
Any offenses resulting in a ban will be defaulted to 24 hours and extended if additional PUG admins find cause. While these are the standards, exceptions to extend or reduce penalties may be made if multiple PUG admins find it more appropriate. Note that the general rule [1006.2.5] - Sandbagging and Class Restrictions also applies to PUG bans.