Horse Run Monthly - Rules


Info
The Horse Run Monthly event series for Team Fortress 2 will be using a slightly modified version of the RGL Global Rulebook. Most changes will be in regards to the format accommodating a both a Single & Double elimination hybrid bracket. Any verbiage relating to Highlander and/or Prolander has been removed or altered to pertain to Sixes.

If you have any questions, comments, concerns, or need to report anything to an admin, please privately contact a Gamer Latam staff member in the Official Gamer Latam Discord.

Our event series will be matching bans with the current RGL ban list (The only exception being failure to submit demos). If you were once banned from RGL and have a lifted ban, please privately contact a Gamer Latam staff member in the Official Gamer Latam Discord to be unbanned. You can find a list of players who are currently banned from RGL here.

Prize Pool:
1st: $300
2nd: $150
3rd: $50

The Top 3 teams will be paid out by a Gamer Latam staff member. A Gamer Latam staff member will contact the leader of your team via Discord.

A Gamer Latam staff member will never ask you for access to your bank account or for any personal details such as log-in information. We will only require information that is relevant to sending you any proper funds for winning.

Tournament Format

Bracket Setup
16 teams total will be able to play in our 6v6 single-elimination Headliner Bracket.

Once Top 8 Begins, it will turn into a double-elimination bracket.

Single elimination bracket with 16 teams.


Double elimination bracket for Top 8.

Secondary Bracket

There will be a separate division bracket for players who are in AM - IM.

This bracket is for players to practice, gain experience, and have fun!

Grand Finals
Grand Finals will be a Single Best of 3 set that gives the team from Winners’ Side a 1 Map Advantage.

Team Color Clause
During the Bo3 Grand Finals, teams must stay on their assigned sides for the duration of the set. (If Team A is on the RED team for Game 1, then they must select the RED team again once the map changes for Game 2).

Format Rules
Teams are required to play with 6 players per team during matches. If a team is unable to field 6 players, then the team may choose to play 5v6. Teams with fewer than 5 players on the server must gather a substitute or a ringer.

Class Limits

The following class limits commands are used inside of Sixes:

tf_tournament_classlimit_scout "2”

"tf_tournament_classlimit_soldier "2"

tf_tournament_classlimit_pyro "2"

tf_tournament_classlimit_demoman "1"

tf_tournament_classlimit_heavy "1"

tf_tournament_classlimit_engineer "1"

tf_tournament_classlimit_medic "1"

tf_tournament_classlimit_sniper "1"

tf_tournament_classlimit_spy "2"

Bypassing these limits in any way that impacts a match (however slight, even if accidental) is considered an exploit, and may result in round or match overturns.

Item Whitelist
The Horse Run Monthly will be using the latest 6s RGL item whitelist.

If there are weapon changes or new weapons added in a TF2 update during the season, they will be automatically banned. The admin team will then evaluate the changes/additions, and update the community on if the weapons will be unbanned or stay banned for the next upcoming event.

6s Map Pool

The Horse Run Monthly will use a combination of tournament legal 5cp and KoTH 6s maps. Maps will be determined by the phase of the bracket. Please refer to the bracket or confirm with a Gamer Latam staff member on which map you will need to play.

5CP Rules

Five Control Point maps (e.g. cp_snakewater_final1, cp_sunshine) will use the "Pro Config" which incorporates the Improved Round Timer and Improved Match Timer plugins.

Control Point (5CP): Each 5CP map has a map timer limit of 30 minutes and a round timer of 4 minutes. No halftimes are played; instead, matches using the 5CP Progressive Config (rgl_6s_5cp_match_pro.cfg) are continuous until a winner is declared.

Suppose neither team has scored the maximum number of 5 rounds possible after the 30 minute map timer has expired. In that case, the win limit will automatically reduce to [current highest rounds won on the scoreboard]+1, triggering continuous overtime.

Example: If at 30 minutes the score is (2-3), the win limit will automatically be adjusted to 4 with the next team to reach 4 rounds won being the winner.

KOTH Rules

King of the Hill maps (e.g. koth_product_final):

King of the Hill (KoTH): Each KoTH map has no map timer and no halftimes played. Instead, the first team to 4 rounds is the winner. Matches using the KoTH Progressive Config (rgl_6s_koth_pro.cfg) are continuous until a winner is declared.

Seeding
Tournament Seeding will be determined by each team’s placement in their most recent RGL season and by which RGL division they have played in most recently.

Forfeiting Matches
Teams have the ability to forfeit matches due to an emergency or conflict. Please note that forfeiting a match may have you disqualified from the current bracket that you are playing in.

Teams and/or Players found forfeiting throughout multiple brackets may be subject to bans.

Here are the Current Forfeit Penalties:
1st forfeit: Warning, Minor Penalty
2nd forfeit: The team is DQ’d from their current bracket.
3rd forfeit: The team is DQ’d from their current bracket, possible ban based on circumstances.

Top 8 Bracket Forfeit Penalties:
1st forfeit: The team is DQ’d from their current bracket.
2nd forfeit (or more): The team is DQ’d from their current bracket, possible ban based on circumstances.

Pauses

Normal procedures regarding pauses can be found under the global rulebook in [1008.9] - Pauses - Pauses. Deviations due to 6v6 rulebook differences are noted here.

Each team will be allowed to initiate two pauses per map for both Control Point and King of the Hill game modes. Pauses must not exceed 5 minutes.


Ruleset

[1001] - Rulebook Overview

Gamer Latam administrators reserve the right to issue decisions for circumstances that are not explicitly dealt with in our rules. Our rules are enforced by administrator discretion, and these rules serve as the guideline from which we make our decisions. We strive to keep the rules both fair and up to date. Consequently, our rules may be updated or changed in any rulebook.

We encourage players to be on time, be fair, and maintain a respectful competitive spirit. It is unlikely that you will ever run into any issues with our rules if you do so.

[1002] - Code of Conduct

[1002.1] - Sportsmanship and Spirit
Players are expected to uphold the competitive integrity that RGL & the Horse Run Monthly encourages. As such, we want to list clear guidelines for behavior to follow while placing importance on understanding the context and intent of behavior in player reports. If you suspect another player or team of any rule violation, you should contact a Gamer Latam staff member privately as soon as possible so an investigation can be opened.The excess posting of harmful or offensive messages on public platforms directed at or referencing the Horse Run Monthly, Gamer Latam, our sponsors, our staff, or a participant will not be tolerated. Abusing in-game chat functions with excessive chat spamming during the game or pauses (as per [1008.9] - Pauses), toxicity, or offensive behavior to other opponents on other platforms in RGL, such as matches and scrimmages, is not tolerated and may lead to a ban.

[1002.2] - Harassment / Flaming / In-Game Toxicity

In misconduct reports, comments made on public platforms (i.e. RGL’s platforms) or during scrims and matches will be looked at on a case-by-case basis. Context and circumstances are extremely important factors to consider when investigating such reports.

Conversely, comments made on private platforms (i.e. Steam messages, private Discord servers, Mumble, Twitch, etc.) will not play a large factor in acting against players accused of misconduct. The Horse Run Monthly team does not believe it is fair to police the words and actions of players in a private setting and therefore will not apply much scrutiny to these reports unless we suspect a genuine intent to harm or threaten another player, the players have a history of misconduct behavior, or the players have disregarded warning(s) to discontinue the behavior. Please note that the below examples of harassment are not tolerated regardless of where it occurs.

Some examples of what harassment is, but is not limited to:

  • Verbal abuse
  • Offensive behavior
  • Hate speech made towards a player (through any medium) that makes them feel uncomfortable or threatened
  • Threatening to dox or harm another player
  • Stalking
  • Circumventing another player's block using any method of digital communication including, but not limited to, Steam, Discord, or Twitch with mal-intent or continued harassment
  • Unwelcomed sexual messages (e.g. sexual harassment, sexual advances, or sexual jokes)
  • Raiding, spamming, or encouraging disruption on social media platforms (e.g. Discord, Twitch, Twitter) through bigoted language, racial epithets/slurs, etc.
  • Discrimination in any form, including but not limited to race, ethnicity, religion, disability, sexual orientation, or gender

Some examples of what harassment is NOT:

  • In-game “trash talk” (ex: being called bad) (note that excessive toxicity/”trash talk” may still fall under the rules outlined in [1002.1] - Sportsmanship and Spirit)
  • Being spammed in private messages - If someone is bothering you, it is suggested to block the individual. (note that this does not override harassment)
  • Gossip in private Discords.

    [1002.3] - Discriminatory Language and Symbols
    ANY use of slurs or discriminatory dog whistles either in in-game chat or found on named items during scrims and matches, whether directed or undirected, is STRICTLY prohibited.

Decals and cosmetic loadouts depicting hate symbols or hate group imagery are prohibited.

When you play on competitive servers, a level of professionalism is expected. If you are unsure about the usage of certain items in-game, please contact an admin to clarify the situation before using the item in an official match.

Refer to [1002.2] - Harassment / Flaming / In-Game Toxicity for information regarding what is considered on-platform and off-platform. The following serves as a guideline of the ban length for the use of slurs, hate symbols, discriminatory dog whistles, or hate group imagery. In more egregious cases, the first offense may be longer than the guideline

1st offense will be a 4-month ban minimum. Further offenses will lead to increasingly longer ban lengths or permanent bans.

[1002.4] - Witch Hunting

Witch hunting refers to any public accusation that insinuates, intends to, or causes harm to the reputation of a specific player or entity without sufficient evidence to support the claim of wrongdoing. Engaging in witch hunting consists of harassing and targeting specific players based on these unsubstantiated claims.Example: Accusing an individual of sexual misconduct based on hearsay and personal grudges rather than concrete evidence. This is often used in conjunction to incite others to harass, doxx, or attack the person being accused. Violations of this may lead to a warning or suspension.

[1002.5] - Withholding Information

Teams/players are expected to report issues related to scrims/matches immediately. These issues should be reported within 24 hours to an admin/moderator. Otherwise, the infraction will be looked at much differently compared to an immediate report, and the admin team will be prompted to use their discretion.This primarily exists to prevent teams or players from withholding information that may lead to a suspension that maximizes damage done to a player or team. For example, if a player uses a slur on a Saturday scrim, but you report it Monday to prevent the player from making the match, your team may face severe consequences for withholding the information.

[1002.6] - Report Abuse

Most cases that come through our reporting system are legitimate. If you see a rule being broken or you feel uncomfortable playing in the league, do not hesitate to report your issue to the admin team. However, a small number of the reports we receive only act to disrupt the work of the admin team. If the report (or reports) in question are found to disturb, harass, or impede the admin team, we may consider it a candidate for report abuse.

For cases like these, admins may delve much further into the background of the case to determine the validity of the report and seek further context behind the report.

Additionally, if a team or player is found to be abusing the report system on any RGL platform or for the Horse Run Monthly, penalties may be administered depending on the severity of the case. Teams or players that persistently report immaterial issues to the admin team may be requested to tone down their involvement in issues and frequency of reporting or lose access to player support from the Horse Run monthly team.

[1003] - Game Integrity

[1003.1] - Cheating
We do not tolerate cheating in TF2 in any form. If we receive evidence (demos, server or anti-cheat software logs, etc.) of someone cheating anywhere in TF2 (including public servers, scrims, and PUGs (Pick-Up Games)), that person will be subject to league penalties. Please note that this applies to all the sections below on a case-by-case basis depending on the intent and impact where it occurred. There is no appeal process. If another player on their team undoubtedly knew/aided/supported their cheating, they also may be subjected to a ban. When players take part and participate in our league, the Horse Run Monthly team expects all of our players to keep their accounts cheat-free.

When a player gets banned for a game integrity-related offense, all matches the player participated in may be completely overturned with no opportunity for the matches to be replayed. If the bracket can be played (i.e. if 1st round could be redone without delaying the bracket), then teams will replay the matches in which the cheating player participated.

Cheating(Aimbot/ESP)

  • 1st offense: Permanent Ban

VAC Bans

  • Permanent (Unless confirmed to be non-TF2 related or TF2 VAC ban removed by Valve)


Other


  • Map Exploits: Warning, match/round overturns, to possible bans based on intent and impact - [1003.4] - Map/Weapon Exploits
  • Script Abuse: Warning based on intent and impact, otherwise 3-Month ban †
  • Game Exploits: Warning based on intent and impact, otherwise 3-24 Month ban ‡
  • Ban evasion: 24 Months and reapplies the length of all active and pending Game Integrity-related bans
  • Alternate Accounts *: 24 Months
  • Assisting Players **: 24 Months

† = Warnings are only applicable to scripts or exploits noted in section [1003.2] - Scripts‡ = Warnings are only applicable to exploits noted in section [1003.3] - Game Exploits

* = Repeat offenders for the following will double their ban length for each new offense, with the 3rd offense resulting in a permanent ban.

** = This ban will be given to all players who are found to be assisting another player in breaking the rules

[1003.1.2] - Usage of 3rd Party Software

In the past, players have questioned the usage of specific 3rd party software, whether they can use software to enhance their hearing capabilities in-game or to bind a button to up the DPI of their mouse. Each software will be dealt with on a case-by-case basis, but they all share the same underlying belief: Does it give the user an unfair advantage over players on the server? Using this belief, we can determine whether a piece of software is allowed in competitive play and whether its usage may result in a ban. If you are unsure whether your use case is legal, please contact an admin.

Audio Equalizers

We have determined that the use of audio equalizers to isolate specific sound ranges to enhance the hearing capability of certain audio cues (e.g.: spy decloaks), whether successfully or unsuccessfully, will result in cheating bans. Using audio equalizers in this methodology is no different from the perks gained from using sound scripts/ESP cheats without the risk of VAC bans. If AC Staff determines that you are using ESP cheats, then you will receive a cheating ban and will not be granted a chance to appeal on the basis that you were using an equalizer.

Mouse Software

With the recent uprise in the use and ban of 180° turn scripts, players were inquiring about the legality of the use of built-in mouse software (e.g.: Logitech Gaming Software) to achieve similar results. The use of mouse software to automate turns is cheating, whether through macros or any other means. Players are expected to manually move their mouse to achieve movement in-game. Those who resort to the use of software/scripts will receive a Scripting Abuse ban. Players are allowed to use a sensitivity toggle in software or in-game to press to turn up or lower their mouse sensitivity. An example is provided below of a legal version of a sensitivity toggle:

//slow sniping

alias +sens "sensitivity 1.5"

alias -sens "sensitivity 3"

bind alt +sens

[1003.2] - Scripts

Scripts that allow players to perform in-game actions that they would not be able to perform without the script or scripts that intentionally disrupt the player's hitbox are banned. Scripts that freeze or glitch the player's model (e.g. forcing the hitbox to not be in the same position as its player model) to make it harder to hit the player are banned. Scripts or programs to enhance a player's sense of hearing are also against the rules.

Examples of banned scripts:

  • Bunnyhop script
  • Panic script †
  • Charge Turn script (as well as using peripherals to perform sharper turn angles) †
  • Turn scripts (such as 180° or panic scripts, as well as yaw/pitch binds) †

Examples of allowed scripts:

  • Crouch jump script
  • Null-cancelling movement script
  • Rocket jump script
  • Mask uber script
  • Team say scripts
  • Loadout changing scripts
  • Viewmodel/Crosshair switchers
  • Medic radar script
  • No explosions/particles smoke script
  • Speedometer script

† = Impact is based on the situation and amount of times abused. For example, scripts randomly clicked with no one around versus used in front of the enemy team or used once on accident with no one around versus used many times throughout the game.

If you are unsure whether a specific script is allowed, please contact an admin to clarify the situation before playing.

[1003.3] - Game Exploits

  • The abuse of unintended functions of the game that give unfair advantages is considered exploitation. Below are some examples:
  • Bypassing configuration-imposed class limits
  • Entering the player model default pose (“civilian pose”/“A-Pose”)
  • Sniper scope transparency ‡
  • Box shadows *
  • Spy cloak/footstep/Ubercharge sound scripts and hearing aids (software enhancements or audio mods to make specific sounds louder) or edit using surface properties *
  • Alteration of game settings to make map objects/props like rocks, boxes, and doors transparent or remove them in any way. Note: If you notice that certain props are missing on the map, please restart your game and see if that fixes the issue. You must not continue playing with invisible props.
  • Rate hacking
  • Intentionally abusing the retry command to void the respawn time and achieve a faster respawn time
  • Using an exploit as an Engineer to be able to hit players twice without a delay with melees
  • Uber Pause Bug (bug where medics can continue healing a player during a pause, which allows the medic to build ubercharge) If the pause uber exploit does happen in a match, teams are expected to inform one another if they unfairly gained uber from the pause and also pause the match. Failure to do so may result in a minor penalty.

Teams must agree to resolve this exploit through either option:

  1. The team that unfairly gained uber must wait for the duration that it would have taken to naturally gain the uber before using it, relative to their starting percentage when the pause occurred (e.g. if your medic's ubercharge level went from 0%-100% from the bug, you need to wait 40 seconds before you can use uber).
  2. Teams must re-exec the config and replay the round (for applicable game modes, this would also consist of restarting from the same positions on the map, round timer, and uber percentages before the exploit took place).

  • Using an illegally gained uber before it would have been naturally obtained will result in team penalties and potentially replayed/overturned rounds or maps.
  • HUD edit to always see your medic's ubercharge percentage (Bypass to access information created for spectators)
  • Reverse Quantum Crouch (https://github.com/ValveSoftware/Source-1-Games/issues/2195) or any method that causes the hitbox to be bugged, either visually or non-visually
  • Bypassing sv_cheats to enable in-game cheat commands *Killing/hurting players during the setup time of a match *
  • Using record;stop to see cloaked spies ‡‡
  • Bypassing cl_flipviewmodels to flip viewmodel animations while alive (doing this while dead or switching classes is allowed)Otherwise unlisted sv_pure exploits

‡ = Those with the script who quickly off class for a very short period (i.e. 30 seconds) and gain no bonus information due to no sniper scope, will only receive a warning.

‡‡ = Those who use record;stop and gain no bonus information due to it will only receive a warning.

* = These exploits result in a Cheating ban rather than a Game Exploit ban.

Examples of allowed mods:

  • Flat textures
  • Custom HUDs/Viewmodels/Crosshairs/Hitsounds
  • Removing Ambient sounds
  • No hats/cosmetics mods
  • No souls/Christmas lights
  • Hiding viewmodels
  • No Explosions
  • Transparent viewmodels
  • Removing damage particles

This is an exhaustive list. If there is a mod not on this list, please verify the usage of the mod before using it.

Examples of allowed but use at your own risk mods:

  • Metal footsteps script
  • Recolored overheal particles (no changes to size, or anything else)

Examples of NOT allowed mods:

Recolored or modified weapon tracer effects

Oversized particle effects (e.g. healing particles, weapon particles, etc.)

Transparent enemy pyro flames (removing your own flames is allowed)

Using mods to replace player texture colors

Developer Textures

Examples of allowed bugs:

  • Wallbugs
  • Edgebugs
  • C-taps
  • Crouch Sniper Peeking / Corner Sniping

If you are unsure about the legality of certain in-game settings or actions, please contact an admin to clarify the situation before playing. Usage of game exploits may result in the overturning of games or rounds, as well as potentially severe penalties to players found abusing them.

[1003.4] - Map/Weapon Exploits

Abusing a section or function of a map to gain an unintended and unfair advantage is considered exploitation. Banned exploits commonly include, but are not limited to:

  • Exploiting map flaws to access areas that are out-of-bounds
  • Exploits that allow a player to shoot another opponent without them being able to shoot back
  • Areas on a map where you can cap/deny capture through walls, floors, ceilings, etc.

Allowed:

  • The use of splash damage through grates and fences (such as wishbone/main on cp_steel) is permitted.

Not Allowed:

  • Engineer buildings may not be placed in areas where they cannot be destroyed, or in locations considered out of bounds (e.g. teleporters on the stock version of pl_upward 3rd forward spawn route, spawn rooms, etc.).
  • Entering out-of-bounds regions in maps is not permitted.
  • Resupplying through improperly brushed spawn zones is not permitted.
  • Using any methods to cancel the phlogistinator animation and extend the pyro’s invulnerability or crits is not permitted.
  • Storing the thermal thruster’s stomp ability while switching to a new secondary weapon is prohibited.
  • Any attempt to extend the intended range of the Pyro's flamethrower (e.g. getting stuck purposefully to gain velocity and extend the flamethrower range) is not permitted.
  • Taunt killing through walls is not permitted.
  • Shooting through the shutter on the last point of cp_gullywash is not permitted.
  • Building up charge meter for Weapon #1 and switching loadout to receive a fully charged Weapon #2. (e.g. Build up the Concheror, switch to the Battalion's Backup with any method, and get a fully charged Battalion. Build up Kritz and switch to fully charged Uber, etc.)

The above list is not exhaustive. If you are unsure about the legality of certain in-map actions or exploitive weapon usage, please contact an admin to clarify the situation before playing. Using map or weapon exploits may result in the overturning of games or rounds or possible bans.

[1003.5] - Match Fixing

In the event of players and teams improperly affecting the outcome of a match, all players involved will be subject to suspension. Should match-fixing be discovered before the end of the tournament, the teams involved will be disqualified.

[1003.6] - Ghosting

Ghosting is attempting to gain an unfair advantage by inappropriately sending or receiving real-time match information with participants. For example, unauthorized use of spectator mode by participants/non-participants. If this behavior is discovered, all players involved will be subject to suspension.

[1003.7] - Streaming Conduct

Stream sniping is not an actionable offense; streamers are responsible for ensuring their streams are not a detriment to their team. This means that we will not take action on stream sniping as players assume the risk of streaming their matches. We recommend delaying streams by at least 90 seconds, muting the game during pauses, or having an overlay during pauses to help mitigate the possibility of stream sniping occurring. Additionally, you are only allowed to stream in official matches if your stream is either:Delayed at least 90 seconds, OR:Easily discoverable by the public

The team with the stream must disclose that they are streaming if asked.

The streamer must be an active match participant for the duration of the match; they cannot be a spectator/mentor.

[1003.8] - No Live Coaching

Coaching, either for online or offline events, is strictly prohibited while a match is active. The use of any personnel for coaching to relay information to players in a match must be done before the games, during pauses, halves, or after the match has officially been concluded. If this behavior is discovered, all players involved will be subject to suspension.

[1003.9] - Account Sharing

Each player is allowed one RGL/Discord account at any given time. Someone creating several accounts or multiple players sharing one account is not allowed. If there are siblings, roommates, LAN centers, etc. who share an IP address, you must make your division admin aware of this as early as possible. Both users will need separate RGL and Steam accounts. Players caught account sharing, whether through RGL, Discord, or Steam, in official matches will face punishment. These can include match overturns, major penalties, bans, and more. These will be handled on a case-by-case basis and the punishment will be given based on the severity of the actions.

[1003.10] - Improper Server Administration

In the event of a match being played on non-league servers, the improper usage of server operator status to influence the outcome of a match will result in suspensions as well as the overturning of match results.

[1003.11] - Reporting

To report a cheater, alternate account, or person for misconduct regarding RGL, the Horse Run Monthly, or any other Gamer Latam event, please contact a Gamer Latam Staff Member privately via Discord.

[1004] - Warnings, Penalties, and Suspensions

[1004.1] - Punitive Action Toward Players

Players in RGL may view their disciplinary history on their profiles. Below is a list detailing the most common reasons for player suspensions:

  • Players found to violate the Code of Conduct will face suspensions of varying lengths. Ban lengths for Code of Conduct violations are handled on a case-by-case basis and may be appealed.
  • Game Integrity-related punitive actions can be found in section [1003] - Game Integrity
  • RGL mirrors bans from other Competitive TF2 leagues Leagues we mirror bans from will have RGL lengths applied to the following bans: cheating, account sharing, and alternate accounts. Bans will only be lifted in the event the league where the ban was mirrored from is lifted before it elapses its duration.

Players that wish to have a ban placed on their account (blacklisted) may do so by filing a support ticket in the RGL Discord.

This list is not comprehensive. Repeat offenders receive punishments of increasing severity.

[1004.2] - Punitive Action towards Teams

Teams receive minor and major penalties inside of RGL.

  • Three minor penalties equate to one major penalty.
  • Each major penalty deducts 4.5 match points from a team. In formats that do not use the match points system, this results in the subtraction of 0.5 wins from a team's record.
  • If a team incurs three major penalties, they are expelled from the league. Additionally, if a team is in egregious violation of the rules and disruptive to the league they may be expelled immediately with or without the necessary penalties.

Minor Penalties:

  • Violation of [1008.9] - Pauses - (1st offense)
  • Failure to submit a recording demo (1st and 2nd offense)
  • Excessive toxicity (1st offense)
  • Violation of [1006.2.5] - Sandbagging and Class Restrictions (1st offense)
  • Incorrect match configs (1st offense)
  • Use of a banned weapon (1st offense)
  • Match forfeit (1st offense)
  • Violation of [1009.4.1] - Communicating ringers - (1st offense)
  • Other rule violations (1st offense)

Major Penalties:

  • Violation of [1007.2.4] - Fraud
  • Match throwing
  • Violation of [1008.9] - Pauses (After 1st offense)
  • Failure to submit a recording demo (After 2nd offense)
  • Excessive toxicity (After 1st offense)
  • Violation of [1006.2.5] - Sandbagging and Class Restrictions (After 1st offense)
  • Incorrect match configs (After 1st offense)
  • Use of a banned weapon (After 1st offense)
  • Refusing to switch off using a banned weapon
  • Violation of [1009.4.1] - Communicating ringers (After 1st offense)\
  • Other rule violations (After 1st offense)

NOTE: This list is not a comprehensive list of all the section rules that will elicit a team penalty.

[1004.3] - Admin Support Abuse

Contacting other admins in search of a different answer after receiving an admin's answer ("Admin Shopping") is prohibited, and may result in a team penalty or warning (with increased penalties for repeat offenses).


[1005] - Player Registration and Eligibility

[1005.1] - Who Can Register

We welcome any player to sign up inside of RGL; however, RGL reserves the right to exclude certain players from any competitions as we see fit. Any account that a player registers into RGL becomes their responsibility. This means that any account you create will be tied back to you as well as other users controlling the account. In the event of a VAC ban, misconduct case, etc., penalties are applied to all accounts at the time of the infraction. Please create a Steam support ticket in case of losing access to your account immediately to recover it and also open a support ticket in the RGL Discord to discuss your options.

[1005.2] - Region

Recharge Gaming League contains separate formats and separate regions. Players outside of a league's default region are welcome to sign up, but teams are under no obligation to accommodate their play. Teams cannot be forced to alter their server location to accommodate players external to the respective league's region. For the following regions, players are considered in the region if they live in one of the countries, dependencies, or territories listed here.

  • North America
  • South America
  • Europe
  • Asia
  • Australia + New Zealand

[1005.3] - Multiple Accounts

Registration must be on your main Discord, RGL, and Steam account. As a rule of thumb, a “main account” is the account in which a player first registered on Steam. Alternative (alt/smurf) accounts are strictly forbidden. Registering for a league using an alt account will result in the alt/smurf account being permanently banned regardless of whether the player has also registered their main account in an RGL league. Furthermore, anyone aiding an alt/smurf account will also receive punishments.

If a player gets banned for an alt-related offense, all matches the player participated in during the season will be overturned. Teams who are found to have a player alting in playoffs will be disqualified, and the remaining playoff teams under the disqualified team will move up one rank. If the bracket can be played (i.e. if 1st round could be redone without delaying the bracket), then teams will replay the playoff matches in which the cheating player participated.

If you do plan to use an alternate account, that account must first be cleared by an admin. All accounts will be linked to the player's discipline history. Players must have their cases approved should they have a reason for the accounts to not be publicly linked (e.g. proof of harassment, etc.) Please open a support ticket in the RGL Discord to discuss your options.

[1005.3.1] - Team/Player Due Diligence

While [1005.3] - Multiple Accounts allows us to penalize teams and players accordingly, it does not mention the need for player due diligence in taking preventative measures to avoid receiving a ban for facilitating alternative accounts or allow us to be lenient against teams and players that have put effort into clearing their players. In recent seasons, we have come across teams that claim they did not suspect players without microphones or players that are “pros in Paladins” and so forth.

Provided below is a list of checks players must do to avoid harsh repercussions:

  • Be wary of players that perform well in logs with limited to no traceable competitive experience, particularly in Main or higher divisions
  • Be wary of players that have limited experience inside of TF2 or use newer than average Steam accounts
  • Be wary of players who state they do not own a microphone
  • Verify stories such as being a “pro” in other games, returning from a long departure from the scene, etc
  • Verify a player's competitive experience on RGL.gg, ESEA, ETF2L, OzFortress, and UGC, as well as their performances on Logs.tf over a prolonged period
  • Preemptively inform admins of suspicious players

Those who fail to perform these basic checks (e.g. failure to report an alt on your team, providing them the account) are liable to various levels of punishments, such as assisting alts bans, matches overturned, season disqualifications, etc.

[1005.4] - Other Registration Restrictions

A player may only be registered on one team per league. As an example, a player cannot be registered on two North American Prolander teams, but a player may be registered on one North American Prolander team and one North American Highlander team.

[1005.4.1] - VPN Usage

The usage of VPNs while playing in RGL.gg is forbidden. If you require an exception to this rule, please contact a Gamer Latam staff member before playing.

[1005.4.2] - Connection

If a player's ping, regardless of region, causes the game to be unplayable for other players (e.g. their character is constantly lagging/jumping around, etc...), that player may be blocked from that region's competitions. If the said player was used in a match, their team may face penalties and be forced to replay or forfeit rounds the player negatively impacted. [1005.4.3] - VAC Bans⚓︎ Any player who has owned a Steam account with a TF2 VAC ban will be banned from RGL permanently unless the VAC ban is removed by Valve. If a VAC ban is not from TF2 and does not apply to TF2, the player with the ban must prove this to an Anti-Cheat admin to be allowed to play.

[1005.4.4] - Player Aliases

Player aliases in RGL are used to identify players as they are known in the community for viewers and other players alike and keep records for admin purposes. As such, player aliases can only be changed once a year, starting from each name change. They may not be changed during an ongoing RGL-hosted season, cup, or other events that the player has participated in or is participating in. Players must have a reasonable motive for a request that justifies the change in records. Players must have a reasonable motive for a request that justifies the change in records and the new name must adhere to [1002] - Code of Conduct.

[1007.2.1] - Prize Pool Payouts

Payouts will be made to players two months after the end of the last grand final match. Leaders of the winning teams will be contacted by RGL and will need to provide RGL with information on how the money should be sent to them. Leaders are responsible for distributing the team's winnings to the rest of their team. Payouts can come in one of two forms: Check through the mail (minus $0.30) Payment through PayPal (minus standard PayPal fee approx. ~3%)

[1007.2.2] - Prize Pool Payout Disputes

In the event of an issue with a team leader failing to properly distribute the prize earnings to their team, a league admin will act as an intermediary. Cases in which a team leader of the winning team maliciously affects the distribution (e.g. keeping the earnings all to themselves or intentionally not distributing to certain team starters) are subject to bans. Such cases will be reviewed by the admin acting as an intermediary to resolve the dispute.

[1007.2.3] - Fraud

If a team or player is found to be committing or supporting fraud, they will face penalties. This includes the following, but is not limited to:

  • [1003.5] - Match Fixing Unapproved profiteering from league activities, including: Selling roster spots, or Monetizing RGL content (official RGL Twitch and Youtube content) without approval Fabricating or manipulating match-related information such as logs, demos, chat logs, screenshots Submitting false reports or including fake or doctored evidence Impersonating players with the intent to profit or gain an unfair advantage Impersonating RGL staff or RGL-approved casting organizations [1010.1] - Casting Organizations, including by presenting yourself as one or by pretending to be a specific staff member Committing payment fraud by tricking a payment processor into believing we have not provided you a service to get a fraudulent refund Punishments will depend on the severity of the situation but are not limited to major penalties being applied, suspensions to players who took part in the scheme, and winnings being forfeited.

[1008] - Matches

[1008.1] - Server Information
Servers with the RGL Server Resources Updater plugin installed will be given preference over servers that do not have it installed within the same location. Servers provided by Serveme or Qixalite are exempt from this requirement.

[1008.4.1.1] - Server Disputes

Teams can agree to play both halves/playoff maps on the same server or each half/playoff map on a different server. STV information must be provided for casted matches between swaps.

If both teams fail to agree on the server to be played, a server will be provided by a division administrator for the teams to play on.

[1008.1.2] - Mandatory Server Settings

  • Servers must be password protected
  • Servers cannot have unusual or abnormal settings or anything that affects a vanilla play experience negatively/detrimentally
  • Servers must be in sv_pure 2 mode
  • Servers must run the correct config for the game mode and map
  • Servers must be hosted by a dedicated server provider or a rental provider, such as na.serveme.tf

Other Sourcemod plugins are allowed so long as they do not affect the integrity of the game being played in any way. League configs must not be tampered with in any way whatsoever outside any config that ends in _custom . Possible violations of these rules will be judged on a case-by-case basis. For example, bunnyhopping plugins are allowed as long as they are not enabled for matches.

[1008.4.2] - Server Plugins & Configs

To ensure parity, competitive integrity, and a minimum standard of quality between servers rented by players through dedicated providers and league rules, all servers are required to include the following:

  • Metamod 1.11
  • SourceMod 1.11
  • RGL Server Resources Updater Plugin, which bundles the following:
  • RGL Match Configs for all formats
  • Updated Updater Plugin
  • Updated Pause Plugin
  • TF2 Comp Fixes
  • SrcTV+
  • RGL QOL Tweaks
  • Progressive Ruleset Timer Plugins
  • TF2 Halftime

  • LogsTF/SupStats2/MedicStats by F2
  • OR: TFTrue
  • Note: Match logs must be auto-uploaded using either TFTrue or LogsTF/SupStats2/MedicStats.

  • Demos.tf Uploader
  • Note: Teams may choose to not auto-upload demos, but must provide scrim/match STV demos when requested by an admin or anti-cheat.
  • It is up to teams to agree to an unlisted STV demo request, league staff will not facilitate or mediate STV demo requests.

Other Sourcemod plugins are allowed so long as they do not affect the integrity of the game being played in any way. League configs must not be tampered with in any way whatsoever outside any config that ends in "_custom". Possible violations of these rules will be judged on a case-by-case basis. For example, bunnyhopping plugins are allowed as long as they are not enabled for matches.

[1008.4.3] - Latency

Match servers must be reasonably playable for a majority of the players on both teams. (e.g. if half of the away team has ping above 110+, a new server should be used). If a player is from outside the default region of play, they do not need to be accommodated by the home team.

[1008.4.4] - Server Issues

If a server freezes, crashes, or gets DDoSed for a prolonged period (60 consecutive seconds or more), the round must be replayed. Any won rounds or halves before the server issues are officially completed and do not need to be replayed.

If either team believes a server disruption influences the outcome of a round, they are expected to pause and contact a Horse Run Monthly staff member via Discord immediately. Pauses during these times may be longer than expected to allow for the admin team to discuss and make a decision.

If teams do not contact an admin or unpause before a ruling, then any rounds played after an unpause are officially counted and will not be replayed. If teams do wait for an admin ruling, then they are to follow the ruling of if that round is counted, replayed, or an extra round is to be played and the situation is reviewed in more detail later.

Worst case scenario, the tournament may be postponed to another date depending on the severity of these issues.

[1008.4.5] - STV

STV must be enabled during matches. Upon request, the team hosting the match must give connect info for the STV broadcast to the enemy team.

If an admin asks a team for STV information, the team hosting the server must be able to provide it in a timely manner.

After the execution of configuration files, it is recommended to reload maps to ensure that the STV is functioning properly.

[1008.4.6] - Match Configs

Match servers must use the latest version of configs and the correct version of the map listed on the match page. The hosting team receives a minor penalty for executing incorrect maps, configs, or whitelists.

Players are barred from using weapons that are banned in the latest RGL whitelist for their respective formats. If at any point the player leaves spawn with a banned item or begins to have an impact on the match(e.g. near the front lines, using banned items, equipped passive weapons, etc.), that team immediately forfeits the round and may be subject to a DQ. Players and teams who refuse to switch out the banned weapon may be banned from future Gamer Latam events.

[1008.5] - STV Demos

Teams must record STV demos for every match. All STVs are forced to have at least a 90-second delay and any edits to shorten the STV delay are punishable. Should a team be caught changing the STV delay to ghost the match or have live spectators, they will face major penalties. Please refer to [1008.4.2] - Server Plugins & Configs for information on plugins that automatically upload STV demo files.

Should you need to provide a demo please upload it to Google Drive, Discord, OneDrive, Dropbox, Mega, demos.tf, or MediaFire. Other methods will be ignored.

[1008.6] - Match Punctuality

A match should start within 20 minutes of when your match is called by a Horse Run Monthly staff member. If a team fails to have a complete team within this timeframe, then the other team may request a forfeit win if they follow the steps in [1008.7] - Requesting Match Forfeits.

Between halves (halftime), both teams have 10 minutes to have a complete team on the server and resume the match. Should a team fail to resume gameplay on time, the opposing team may claim a forfeit win that includes already achieved match results.

If one team needs more time, the opposing team may choose to delay the start of the match if needed but are within their rights to request a forfeit if they believe that their time is being wasted.

Additionally, Horse Run Monthly staff members may decide to DQ a team who is delaying the rest of the bracket.

[1008.7] - Requesting Match Forfeits

For a team to request a forfeit, a match must be past the default start time or be paused. The team requesting a forfeit must have a full team on the server for 15 minutes and the team must be clear that they want to start the match or unpause before the request. The 15-minute timer starts when one team has all their players on their side present, it is past the default match time, and the team has announced their intention to start the match.

This means that your team cannot be silent and then 15 minutes after match time to request a forfeit win. However, if your team states to the other captain early on through direct message or in-game chat that you do not wish to wait past the allotted time, that would be grounds for obtaining a forfeit win.

This will also apply to pauses lasting more than 5 minutes.

.e.g. "We would like to start on time. Please make sure to be ready on time.”

e.g. "This pause is taking a long time. The default allotted time for a pause is 5 minutes, and we would like to unpause as soon as possible."

If you've made your intentions clear, then you can start the process of requesting a match forfeit. To request a forfeit, you can copy this exact text below into in-game chat or DM. You should also contact an Admin and inform them that you are starting this process.

Teams must first inform the enemy by including the following information before proceeding to request a forfeit win:

1. The minimum number of players has not been met.
2.Ready up or unpause in 5 minutes.
3. If they are not ready to play, there will be a forfeit.

If the enemy team does not start up in time, you will receive a “confirmation” from the admin and you may leave the match server. The team who was ready will receive a win, and will be able to advance to the next phase of the bracket.

Should a team request a forfeit win without having a full team for 15 minutes or request a forfeit without giving the opposing team a clear 5-minute warning, their forfeit request will be rejected. During Top 8, Horse Run Monthly staff members will try to accommodate teams who may be in need of a ringer.

Forfeiting matches in Top 8 may cause you our your team to be penalized/banned from future Gamer Latam events.

[1008.8] - Score Submission

Following a match, the team that provides the server must submit match results and link logs (https://logs.tf/) immediately upon completion of the match with potential penalties for late or incomplete submission.

The team providing the match server is responsible for submitting match results and posting all the logs into the appropriate channel; however, the opposing team may also do this.

If an incorrect match score or match log(s) is submitted, please contact a Horse Run Monthly staff member to have this resolved.

[1008.9] - Pauses

A team is allowed to initiate one pause per half **. They may use this pause at any time during the half. Using the "repause" command (unpauses and pauses the game instantly to allow the player(s) to join the server) does not count towards this limit.

Only the team that pauses the match may unpause it. They must alert their opponents and check that they are ready before unpausing. Either team can initiate a re-pause if necessary, but they must notify the other team before re-pausing. Both teams are responsible for keeping game chat clear during pauses so unpauses may be communicated. Any team that spams or obscures chat will be held responsible for the consequences.

A pause should take no longer than 5 minutes from either team. If your opponent allows a pause longer than 5 minutes or more than one pause, you are expected to extend the same courtesy to them. Please refer to [1008.7] - Requesting Match Forfeits for forfeits due to unpaused games.

If a player or team spams or abuses the pause feature, they will face penalties.** = See 6v6 format-specific rules for the number of pauses in [3001.8] - Pauses - Pauses

[1008.12] - In-Game Match Disputes

If players have disputes mid-match, they can reach out to their division admin/moderator to resolve any issues a team may have. If your division admin/moderator is unavailable, please reach out to other admins/moderators in your format. Minor disputes or issues may be solved quickly, such as but not limited to removing a player that is not rostered, unconfirmed/denied ringers, or incorrect config. Should arbitration take longer than 10 minutes (5 minutes max pause limit + 5 minutes extra time), teams are expected to play out the match and wait for a resolution after the match to prevent a rushed decision from being made.

Issues such as full match replays, mid-game forfeit wins, round overturns, etc. likely will take longer than 20 minutes and teams will be informed of the final decision after a thorough investigation has been completed.

[1008.13] - Match Throwing / Match Fixing

If a team is found to be throwing a match, they will face very harsh penalties.

This includes the following, but is not limited to:

  • Purposefully not trying, such as off-classing to suboptimal team compositions in terms of skill or game situation or suboptimal ringers who are below the division's team skill level
  • Purposely running in and not shooting at your opponents
  • Purposely not completing the objective (e.g. refusing to capture the objective to lose the game to allow the other team to win.)
  • Intentionally AFKing or idling during a match

Punishments will depend on the severity of the situation.

[1008.16] - Disruption of Services

The intentional disruption of the RGL site, forums, and other services that the Horse Run Monthly may use is not allowed.

This includes the following but is not limited to:

  • DDoSing servers being used for matches, the RGL site, or its various services
  • Intentionally interfering by connecting to a tournament match. Players can be found to be disrupting matches (before the start of the match, during halftime, ongoing gameplay, or during pauses) if they do not immediately disconnect from the server or refuse to leave the server upon a team requesting the player(s) to leave the server.
  • Intentionally tampering with server settings (refer to [1008.4.1.2] - Mandatory Server Settings) to disrupt the match or gain an unfair advantage over the players on the server
  • Attempts to boycott the tournament to disrupt play during the tournament.

Punishments will depend on the severity of the situation.

[1009] - Substitutes and Ringers

[1009.1] - Rostered Player Match Eligibility

Teams must have all 6 player slots filled up to be approved for the competition. Teams are allowed a maximum of two ringers per event. All players must have valid RGL, Steam, and Discord accounts to be allowed.

Team Captains must submit their Roster in the following format in the #teams channel in the Gamer Latam Discord Server:

[Team Name]
Pocket Scout: [RGL Link]
Pocket Soldier: [RGL Link]

Demoman: [RGL Link]
Medic: [RGL Link]
Flank Scout: [RGL Link]
Roamer: [RGL Link]
Ringer 1: [RGL Link]
Ringer 2: [RGL Link]

Ringers for the secondary bracket must be within the skill level of other RGL AM - IM players for their respective class. An admin can deny a Ringer if they are not found to be in line with the skill level of the team that they are ringing for.

Additionally, Ringers in the Headliner bracket are expected to be in line with other RGL Main and Up players in terms of skill.

Ringers must be communicated to Horse Run Monthly staff members BEFORE playing your match. Ringers must also remain on their designated class. Failing to do so will result in penalties or even bans.

Teams will be required to resubmit their rosters each month.

[1009.2] - Player Swapping

A team can switch a player out with another valid player during a match, with or without a pause. Players may be switched out due to connection/computer issues, sudden life events, etc. A team cannot have extra players on the server. For a team to switch a player out, the replaced player on the server must leave before the new player joins.

[1009.3] - No Live Spectators

Players/people in Spectator Mode are strictly prohibited in any match. Only Horse Run Monthly staff members will be allowed to spectate a match to handle match dispute cases.

[1010] - Match Casts

[1010.1] - Tardiness

We expect punctuality from top teams. For matches that are not casted, teams are still expected to follow the standard start time rules. However, for matches that are being casted, if the match does not start within twenty minutes of the start time the team(s) which are not ready will be issued a penalty.

This may result in a DQ for the offending team(s).

[1010.2] - Disrupting Casted Matches

If a team or player messes with a cast by changing maps, executing the off config, or anything that turns off the STV so that the viewers cannot see the conclusion to a match, etc., a penalty may apply.

ALWAYS ask a Horse Run Monthly for permission before starting games or changing maps if your match is being casted.

[1010.3] - Aliases / Fakenicking

During casted matches, player names must match their RGL aliases. Names do not have to be exact, but anyone who glances at your name should be able to instantly understand who you are. This is capped at a maximum of 1 major penalty per match.

Failing to properly alias may result in penalties for you and your team.