§1 League Information
Owner- The person who is the Owner of the organization which registered the league team on the website.
Captain - The Player listed on the team profile as the Captain. This person will be held responsible for the team's actions before, during, and immediately after a match. If the Captain does not participate in a match, then any players(s) who type "ready" to start either half of play will be designated as acting captain for the entire match and be held responsible for any and all team violations that occur at any point during the match.
Scheduler - The Scheduler is responsible for setting up a match. The team Captain and Owner may designate up to two Schedulers on the team roster by clicking "Manage Team Roster" under the Team Panel box on this website. All information pertaining to the match being scheduled should be exchanged via the TPG Scheduler, located on the TPG League website. The TPG Scheduler is the only official form of inter-team communication.
Reporter - The team Reporter is able to report match scores and file disputes. The team Captain and Owner may designate up to one Reporter on the team roster by clicking "Manage Team Roster" under the Team Panel box on this website.
Privileged Player - The team Owner, Captain, Schedulers and Reporter are considered privileged team players in regard to the TPG League website.
TPG Scheduler - The system used by teams to contact opponents via the TPG League website, to schedule matches. The TPG Scheduler link can be found by clicking the link titled "Season Matches" under the Team Panel box.
Pending Queue/Opponent Pending - When an odd number of teams are active within a division, the odd team out will not receive an automatic bye win. Instead, this team will be placed into the Pending Queue for its division. Once two teams are added to the Pending Queue, they will both be scheduled together automatically and emails will be dispatched to all Privileged Players on both teams.
Cheating - Cheating includes, but is not limited to: the use of any outside programs that aids in the visual location of players on a map; the use of any outside programs that aids in targeting players on a map; custom sounds, or rates outside the standard allowable range; adding, deleting, or modifying player and/or environment models and/or skins.
Players are prohibited from binding any action in conjunction with +attack. Also, players may not bind +attack to mwheelup or mwheeldown to accelerate shooting weapons faster than they are intended to be.
Weapon spawning to bypass TPG class limitations is illegal.
Note: The use of stopsound is legal.
Demo - A first person recording of an entire half of match play, created by using the console command record. Every player is required to record one demo per half of play.
Half - The 10 rounds begin when the half of play goes live, and end after the 10th round.
Overtime - two -3 round halfs of play, with an increased amount of starting cash.
Ineligible Player - Any player not on a team's roster, during regular and post season play. A player on a team roster with no Steam ID listed, or an incorrect Steam ID listed, is considered ineligible during regular and post season play. Players suspended from league play are ineligible to play in league matches regardless of their in-game handle or Steam ID.
Match - The completion of two halves of play, each team playing one half as Allies, and one half as Axis. In the event of a tie, an overtime session will be played.
Player - A single person associated with a single Steam ID.
Roster - The listing of a team's Players, which include each player's name, game handle, and Steam ID, as posted on the TPG League website.
Screenshot (SS) - The image created by using the console command snapshot, or by pressing the key bound to snapshot, or defined in the keyboard options as take screenshot.
RCON STATUS Screenshot - A screenshot created by the SNAPSHOT command showing each participating players' handle, Steam ID, and IP address. This is created by using the console commands RCON STATUS then SNAPSHOT.
Multi-Teaming - Being on the roster of more than one team, in a single league, at the same time.
Client Variable (Cvar) - A client-side command used in the game console, or config files.
Server Variable (Svar) - A server-side command used by the game server.
§2 Player Information
§2.1 Player Names
All players must use their tag and handle as listed on the TPG League website during match play. If no handle is listed, the player must use the name listed on the League website.
Players' names including, but not limited to, the following content will not be permitted: profanity, bigotry or hate against any race, sex, or religious group; drug use and other content deemed inappropriate by the League.
§2.2 Custom File Content
Only default game files may be used, unless explicitly approved or provided by TPG League.
The use of the file customXHair.spr to obtain a custom crosshair is permitted in TPG matches, except when using the sniper rifle. Using a custom crosshair for the sniper scope is not permitted.
§2.3 Custom Game Content
§2.3.1 Client Config
Players rates must be between the following values during match play:
rate - 20000 to maximum value
cl_cmdrate - 60 to maximum value
cl_updaterate - 60 to maximum value
ex_interp - 0.01 to 0.03
Only commands and Cvars approved by TPG League may be used in the game console or config files. No Cvar may be altered from its default value, except via the use of the game options menu, or unless explicitly approved by the TPG League.
§2.4 Information & Evidence Request
§2.5 Multi-Teaming & Multiple Accounts
Players may not be members of more than one team at the same time, within the same game, within TPG League.
Players may not create multiple accounts or use more than one Steam ID to attempt to join multiple teams' rosters at the same time.
A player may not participate in more than one match of play for a given week of play.
§3 Team Information
§3.1 Participation in the League
Any team interested in participating in TPG League should create a team via the TPG League website. To be scheduled for match play, a team's roster must consist of a minimum of five players. Rosters remain unlocked during preseason.
Any team having two or more persons suspended during the same season, due to cheating or unsportsmanlike conduct MAY be removed from league play for the duration of the current season.
Teams joining the league after the completion of week four of regular season will not be eligible for post season play.
TPG League reserves the right to remove teams from the league at the discretion of the league.
Rosters will lock 24 hours prior to the scheduled match day and time. Players may not join a roster while rosters are locked, but leaving rosters is permitted.
Team rosters will be locked for the duration of the season prior to the completion of week seven. This will prevent players on losing teams from jumping to teams that are sure to make the playoffs.
TPG Admins will not change or correct Steam ID's when team rosters are locked. Ensuring rosters are accurate and up to date is the responsibility of teams and not the TPG Admins. In case an issue arises from our website which prevents Players from joining teams or changing Steam IDs before the rosters officially lock for that week, then the deadline for support ticket requests concerning roster or Steam ID changes is whenever rosters are officially set to lock for that week. Submitting a roster-related support ticket before the deadline does not guarantee that the request will be approved by your match time.
§3.3 Team Names
Team names including, but not limited to the following content will not be permitted: profanity, bigotry, or hate to any race, sex, or religious group; drug use, and other content deemed inappropriate by the League.
Requests to change a team's name or tag must be submitted via the support ticket system.
§4 Match Information
The default day and time for all matches is yet to be determined.
All team are expected to follow the set TPG map rotation. No Exceptions.
All information pertaining to the match being scheduled should be exchanged via the TPG Scheduler, located on the TPG website under the heading "Season Matches".
Both Captains and team Owners may partake in team scheduling. Captains and Owners may designate an additional two players to become team schedulers on the TPG website by clicking "Manage Team Roster" under their Team Panel.
Teams whose opponents have failed to attempt to contact them via the TPG Scheduler within TWENTY FOUR hours of the default match time, or earlier, will be eligible to give their opponent a forfeit loss for the week and automatically reschedule themselves into the Pending Queue so that they may play an active team in their division. If another team in the same division is already in the Pending Queue, then both teams will be automatically scheduled together. Teams whose opponents are considered inactive leading up to a match are encouraged to make use of this feature.
Submitting and then deleting requests before they are accepted or declined by their opponent will not count as an attempted contact; some form of proposal must either remain active or be accepted or declined.
Teams who are marked inactive and given a forfeit loss are allowed to file a support ticket to request immediate reactivation and rescheduling against the next available team.
Matches that need to be rescheduled must be played within three days, Wednesday at 9:00 PM EST, of the default day and time.
Un-agreeable Match Offers - if both team captains cannot agree upon a new match time before 24 hours of the default match time, the match will be played at the default match time.
***The only exception to this rule is for TPG playoff matches. You cannot take a FF win in the playoffs. If the default sunday does not work, and no time can become agreed upon during the week, then the following Sunday becomes the new default.
§4.1.1 Pending Queue
Teams added to the Pending Queue will have "Opponent Pending" listed on the weekly schedule instead of an opponent. This is not a bye week. Teams in the Pending Queue may be scheduled against any opponent in their division at any time leading up to the default match date and time (Sunday, 9:00 PM Eastern Time). Once scheduled, both teams will be informed of this via email. Teams will then use the TPG Scheduler to finalize their match date, time, and server location. It is important to begin this process the moment your team is scheduled from Pending Queue, since you will generally have less than 24 hours with which to schedule your match.
If your team is in the Pending Queue with less than 24 hours until the default match date and time, and you know that your team will not be able to play that week at the default date and time, then a privileged member of your team is encouraged to contact a TPG admin and inform him that your team wishes to be removed from Pending Queue for that week.
Teams who are not scheduled nor are in Pending Queue for a given week will simply not have any match recorded for them upon completion of that week. Teams who remain in Pending Queue may be eligible for receiving a bye win for that week if (and only if) a privileged member of the team reports at the default match start date and time and contacts a TPG admin, assuming no other teams in their division are waiting for a match opponent. The bye win will be awarded if no teams in your division are available for reschedule by 9:20 PM Eastern Time.
Bye wins will count as a forfeit win and may decrease your team's chances of making playoffs.
§4.2 Player Eligibility
Players must use the Steam ID indicated on their team's roster for match play. If a player uses a game handle that is different from the roster, their opponent should be made aware of the change. Player eligibility should be verified before match time by both teams. Matches may be suspended until player eligibility can be verified.
All are welcome to sign up and play. There is no entry fee.
*Those who have a current suspensions in other TPG Leagues must wait until their suspension is lifted to be able to play.
Teams who have RCON control must take an RCON STATUS screen shot before the match. In the event that screenshots are to be provided to a league admin, player eligibility can be further checked through IP matching to prevent a player from avoiding the roster lock or playing while suspended on a different Steam ID.
Matches are to be played 5v5.
Note: TPG League requires a team roster consisting of five or more eligible players to keep a team active in league play.
§4.3 Voice Communication
Only team Captains are allowed to use public in-game messaging (messagemode1/mm1) during match time. This rule also applies when dead.
Use of team voice communication programs (TeamSpeak, Ventrilo, Mumble, etc.) is completely acceptable and recommended.
§4.4 Match Screen Shots
Before each half starts, the screenshot rules must be observed. The Captain of the team who has control of the server must take an RCON STATUS screenshot. To do this type "Rcon Status in console, once all the names, steamIDs, and IP address appear, quickly type "SNAPSHOT" to obtain a screenshot of this information.
Both team Captains must verify the Steam IDs of all players in the server by typing STATUS in console.
A valid screenshot must include all of the following elements:
- Scoreboard must be showing.
- Primary weapon must be out (snipers must take two, 1 scoped and 1 unscoped).
- Radar must be enabled.
- Netgraph must be turned on using the console command net_graph 3 .
- At least one friendly and one opposing player model must be in view.
All players must a take a screenshot at the end of each half showing the final scores for that half. If a player leaves the half early then he must take a screenshot showing the scoreboard and net_graph 3 before exiting.
If any of the above elements are missing from the screenshot it will not be considered a valid screenshot. You must repeat the above procedure for each half of play.
If you (re-)join the match after it is live, you must take a screenshot in your spawn immediately. Player models are not required to be in view for these in-spawn screenshots.
§4.5 Game Settings
- Game Mode - Classic Competitive
- Rounds per Half - 10
- Starting Cash - $800
- Freeze Time - 12 seconds
- Buy Time - 20 seconds
- Round Time Limit - 1 minute and 45 seconds
- Zeus Weapon disabled
- Players are allowed to carry up to 3 different grenades.
- 2 Flash bangs are allowed and will count as 1 Grenade.
Overtime Match Settings:
- Rounds per Half - 3
- Starting Cash - $10,000
§4.6 Match Process
A 20 minute grace period is provided prior to match beginning. The grace period is not an extended warm-up period. If both teams have the agreed upon number of players on a match server at anytime between 9:00 Eastern and 9:20 Eastern then match must begin immediately.
After completing the first half of the game, teams are allowed a 5 minute break.
A cease-fire should be observed during half-time. Teams should refrain from disruptive behavior during half-time (i.e. grenade-spamming opponents' spawn area).
Summary of match procedure:
- Both teams enter server
- Team ping is verified
- Steam ID's are verified
- Servers team Captain must take a Rcon Status shot
- Players begin their individual demos
- Any waiver of rules is verified and documented in-game
- Cease-fire is in effect allowing teams to meet at the center of map for individual player Screenshots.
- Captains notify each other when their teams are ready by typing "ready" in all chat
- Once both teams are ready, the Hosting Team exec's the league config (rcon exec tpg.cfg) and the match goes live
- Match half is played
- Match half ends and players take a screen shot of half time scores
- Server switches player sides
- 2nd half goes live
- Match Half is played
- Match half ends and players take a screen shot of half time/Overall Match scores
- Players stop their 2nd half demos
In the event of a tie at the end of both halves of play, two - 3 round overtime halfs must be played. Teams will use the side they used from the first half of play first. Ex. Home team was CT first half so they are CT during the first 3 overtime rounds.
In the event there is a tie after the Overtime, the teams will proceed into a double overtime. This will repeat until there is a winner.
§4.7 Server Crashes
In the event of a server crash, the hosting team must restore the game to the last completed round (match score, per player start money, equipment, weapons, etc.):
Go into console and use the following command to retrieve the backup round file name:
rcon mp_backup_restore_list_files 1 (Use 1 for First Half - Use 2 for Second Half)
The most recent round should be displayed first.
Once the server displays all previous rounds played, load the appropriate round using the following command:
rcon mp_backup_restore_load_file [use the output from step 1]
In the event the server cannot be restarted, the game must be suspended and team hosting the match, must make a support ticket.
§4.8 Player Disconnect(s)
If a player disconnects, the Hosting team Captain (or a designated player if the hosting Captain disconnects) shall pause the round during the freeze time of the NEXT round. The match will remain paused for no more than three minutes, at which point the match will be un-paused and resumed by the designated player of the disconnected team. Teams are limited to 1 pause per each half period and 1 pause per each overtime half period. A pause can last no longer than 3 minutes.
To Pause the round during the freeze time use the following command:
Once the disconnected player reconnects OR the 3 minute grace time is over, resume the game by using the same command:
§4.9 Match Results
Upon conclusion of a match, team Captains are to verify the final score. Either team may report the final score for the match (combined scores total of all halves played) using the "Report" link found via the "Season Matches" panel of the website.
Do not report official match results to the league via the league forums, steam or email.
If there is an issue in reporting scores, or scores have been reported incorrectly, the team captain must file a support ticket.
Forfeits must be reported using the "Report" link found in the "Season Matches" panel. If your team is awarded a forfeit win (by either team) before the default match date for that week, then your team will automatically be placed in the Pending Queue for automatic rescheduling.
For a team to recieve a ff win, they must first have accepted or proposed a match time via TPG Match Comm. If both teams have agreed on a match time both teams must join the server at accepted time. If a team does not have five players in the server "readied up" after 20 minutes from the originally scheduled match time, then the opposing team can force them to play with four. If they cannot field four, then the team with enough players must take a screenshot of the scoreboard showing their entire team in the server. This is to help you prove that you did show up and they didn't. At that time the team may leave and report a FF win. The other team does NOT have to allow you to use a RINGER. A screenshot of them agreeing is the best way to prove they allowed the ringer.
Any team receiving a forfeit loss during regular season will be set inactive and must file a support ticket to be reactivated for league play. Any team receiving two or more forfeit losses during a single season may be removed from the league.
§4.11 Quitting the Match
If an entire team quits from the server once the half has gone live but before the half has ended, then the match will be considered over. The team who remained in the server will keep their score up to that point, and the team who quit the match will be scored as having 0 points for the entire match.
Should a team drop under 5 players during the first half of play, they have until the end of the half to have their players reconnect. The second half may not start with less than 5 players.
§5 Server Information
§5.1 Designated Server Usage
The Use of Private Servers are Allowed. If you are using a private server, the following criteria must be met:
Servers used for league matches must be in the United States, unless both teams agree on a server in a different location. Any variation must be documented via the TPG Scheduler.
All Servers must be dedicated (i.e. non-listening) and on a T1 or better connection (no DSL or cable modems).
Servers used for league matches must be set to record server logs.
Servers must contain 11 Slots.
10 slots for the 5 competing players on each team
1 slot for the CS:GO TV
The team listed on the schedule as the "home" team has choice of server usage for both halves. The Home team ALSO has choice of which side to join first.
The home team may choose to use the away team's server, if they wish. In this case, the Home team still has choice of sides.
Team Captains (or other privileged team player) should enter their server details into their team's properties. This can be found from the "Team Panel" menu on the left of this website. If a team does or does not have a server then it should be specified in their team properties (updated weekly if the situation should change).
If your team does not specify that your server is available for match play by the time your team is scheduled for a given week of play, then it will not be available for match play regardless of who the home team is; the server selected via the TPG Scheduler's drop-down box will become the official designated server for that match of play.
Server details entered into the TPG Scheduler comments field are not official for match play.
If you do not have a server and would like to "Borrow" a TPG server for your match, you must submit a support ticket 24 hours BEFORE your scheduled match time.
§5.2 Server Configuration
The server configuration file is subject to change at any time. Teams are responsible for ensuring they have the most current and up to date server config uploaded.
Check the League news page regularly as we will post updates there.
§5.3 Ping Imbalance
In the event that the home team's choice of server results in an average team ping imbalance that is consistently greater than or equal to 40 milliseconds (ms), then the match will be played on the away team's choice of server. If the away team cannot produce a server that fixes the ping imbalance for both teams, then the match is to be rescheduled. A Screenshot must be taken to document the ping imbalance using the F12 feature, so that it goes to your steam profile and can easily be viewed right away by a TPG Admin.
South American/European teams that are in a North American division waive their rights to Ping Imbalance.
§5.4 Anti-Cheat Software & Server Admin Module
Valve's Anti-cheat (VAC) Security Module must be running on a server used for an official TPG match. Other third-party anti-cheat programs are not allowed. Third-party admin modules may be loaded on servers as long as they do not interfere with match play.
Other prohibited plugins include amxx, and similar plugins that would change the default style gameplay. Such plugins may be installed on the server, but they must be disabled during match play.
§5.5 CS:GO TV
CS:GO TV MUST be used during matches. Executing the TPG.cfg will automatically start the CS:GO TV. If the opposing team should request a copy of the CS:GO TV demo the hosting team MUST comply.
Failure to provide CS:GO TV demos will result in the suspension of the team's Captain for a minimum two games.
If the match was played on a TPG Server, you must open a support ticket.
TPG reserves the right to request CS:GO TV demos.
*CS:GO TV is not something you need to purchase. It is free to use, you just need 1 server slot for it.
All disputes must be filed within 24 hours of match completion. Disputes can only be submitted by team owners, leaders, or designated match reporters.
Players have 36 hours to upload requested match information. The 36 hours shall begin when an email has been sent to player(s) email, requesting match information.
Disputes must specify only one person (with Steam ID) who is suspected of cheating. In the event that person is found to be cheating, another demo can be requested until a player is cleared.
Teams may file three cheating disputes per season (including pre-season, regular season, and post season play). If a disputed player is guilty of cheating, the disputing team will not be charged with a dispute. Teams may not dispute more than 2 players in 1 match. Disputing 2 players will use 2 of the 3 disputes alloted to each team per season. Please create 2 separate tickets if disputing 2 players, one for each disputed player.
When creating a support ticket, you must include your game handle, and team information. If this is a cheating ticket, you must include the players Steam ID,game handle and a link to the end round screenshots. If you are the hosting team a link to the rcon status is required at the time of creating ticket. Please include all information that would help in your case, the more information we have the easier and faster it is to resolve the ticket for you. Here is an example ticket format to use.
I (player) from (team name) would like to dispute (player) ; (steam_id) from (team name) for (dispute info).
End round screenshots "Link to screenshots here"
Rcon status Screenshots "Link to rcon status here"
That is a proper format for creating a support ticket. Tickets not filled out properly will be closed.
Teams may dispute up to two people in 1 match and will count
*Note TPG Admins will not join a match server to assist in disputes. We require you to file a support ticket or join #tpg_support for assistance.
All dispute appeals must be filed within 36 hours of the original ruling.
TPG staff reserves the right to reject a dispute appeal for any reason.
Code of Conduct
All players and teams are expected to adhere to the following code of conduct. Any action by an individual player, or action by a collection of players from the same Team, found to be in violation of the code of conduct by league administrators can result in disciplinary action by the league.
§7.1 Acceptable Team/Player Names
§7.2 Acceptable Player Conduct
The use of vulgar, bigoted or profane speech, harassing players/teams and league administrators will not be tolerated.
Any player found crashing and/or spamming vents, servers or sending packets to player, will be removed from the league permenantly.
Teams that knowingly and willingly allow suspended players to join their roster will be removed from the league, and all players on that team will be suspended.
§7.3 Acceptable In-game conduct
In-game activity includes the warm-up period leading up to a match, half-time while on a match server and the time immediately after a match while a player is connected to a match server.
While In-game, players are to conduct themselves in an appropriate manner, with maturity and respect. Any player(s) or team(s) found in violation of the code of conduct, as stated above, will be disciplined as follows:
Access to the league IRC channels and forums will be revoked and the player(s) and/or team(s) will be suspended from participation in the league based on the level of the infraction at TPG Administration's discretion.
§7.4 Match Infractions
Listed below are common match violations and typical league remedies. These are guidelines only and the league may require more or less stringent remedies on a case by case basis. The league reserves the right to review rule violations whether or not a team files a formal dispute.
Failure to employ proper server config:
Half must be immediately stopped and replayed after voicing objection on mm1. If no objections are raised by the end of the match then the results will stand.
Players may not go below the minimum approved values. Failure to do so will result in that player suspended for a minimum of one game.
TPG admins will review each case separately and determine what, if any, remedy is required for each situation.
Playing while suspended:
The suspended Player will receive 200% of the original suspension time added to the current suspension length. Permission granted by the opposing team for the suspended Player to participate will not nullify this rule.
Individual suspensions may be given on a case by case basis by any admin if the rule violator is deemed to have done it with purpose and disregard for the TPG rules.
Steam account trading:
Any player found to have traded their Steam ID to another player in order to bypass the Steam ID check, will receive a xx game suspension. The match will be overturned.
Inappropriate use of mm1:
TPG admins will review each case separately and determine what, if any, remedy is required for each situation. (The use of any profanity, bigotry or hate against any race, sex, or religious group towards any player will result in the said players being punished.)
Player(s) are documented to have cheated in a TPG match:
Loss of match to offending team and ban of player from the league.
Players(s) are documented to have cheated in a sanctioned match of another league:
TPG reserves the right to request demos, server logs and/or HLTV of banned players for consideration by TPG.Player(s) involved in Sky Walking or Clip boosting:
If 2 or more players of a team are involved in an illegal boost, they will each receive a 2 game suspension. If the infraction had a direct impact on the outcome of that round in addition to the subsequent three rounds, the round(s) will be awarded to the opposing team. If both teams are found to have been involved in illegal boosting and both boosts had direct impact on the outcome of the round, the round will not be awarded to neither team and players involved will receive a 2 game suspension.Player fails to record valid demo(s):
Failing to record a valid demo for one half will result in a three month suspension.
Failing to record a valid demo for both halves will result in a six month suspension.
Failing to provide any valid demo(s) will result in ff loss for your team.
Partial or corrupt demo(s) will be considered as invalid demo(s).
Upon second infraction of this rule, player(s) in question will at a minimum, be suspended for one year.
Player fails to take valid screenshot(s):
Failing to submit valid screenshot for one half will result in a one game suspension.
Failing to submit valid screenshot for both halves will result in a two game suspension.
Failing to submit any screenshot(s) will result in a forfeit loss for your team.
Upon second infraction of this rule, the player in question will, at a minimum, be suspended for the duration of the current season.
Server Captain fails to take an RCON STATUS screenshot:
Failing to produce a requested rcon status shot will result in a one game suspension of the team Captain.Failure to produce server logs:
Failure to produce requested server logs will result in a one game suspension of team Captain.
If both teams in a given match are determined to have violated the rules during a match (i.e. "off-setting penalties"), TPG reserves the right to give forfeit losses out to each team involved. Rule violations do not have to be "equal" for this option to be enforced.Exploit & Infraction Penalties:
Exploits and infractions will be dealt with on a case by case decision, but standard resolution for the below infractions include overturning the round in which the infraction occurred if the infraction had a direct impact on the outcome of that round in addition to the subsequent three rounds. At the admin's discretion, the player who committed the offense can be banned for a week.
§7.5 Exploitations/Sky Walking
Map manipulation which involves gaining access to areas outside of the standard map limits is considered illegal. This includes any area in which the player is not surrounded on all sides by visible map models or textures. Sky walking, or any area in which the player is backed up against "invisible walls" is illegal.
If you have questions about restricted areas of a particular map, please contact a TPG Admin before match time.
Player boosting is allowed. Boosts that result in clipping AND/OR Sky Walking are illegal. Clipping is when a player is either boosted through a solid layer, or when a player manipulates him/herself so that they can see over, under, and/or through any solid entity such as a wall or box. It is illegal to boost on a spot where there is no surface directly below you and your model must not appear to be floating.
Nade exploitation(glitching) is NOT PERMITTED. Anyone who does this will be subject to suspension from the league. This includes the use of Flash Bang Bugs - it is illegal to use any flash bang bugs, regardless of intent.
Silent Bomb Plants are illegal - all bomb plants must be done in a position in which it can be heard by the opposing team.Illegal Bomb Plants - it is illegal to plant the bomb in a position that cannot be defused by the opposing team or in a position in which the bomb is floating and not touching the ground.
Illegal Bomb Defuses - the bomb cannot be defused through any solid objects.
Illegal Bomb Defuses - it is illegal to intentionally distort your hit boxes with the use of an alias while defusing the bomb. Each dispute will be handled on a case by case basis, reviewing multiple aspects, including, but not limited to, the speed at which movement is made, the action of movement made, as well as the outcome of the exploiting action.
Walking / Boosting Through Walls - walking or boosting through walls, floors, or roofs is not allowed.
§7.6 Altering/Manipulating/Releasing Evidence
Submitting falsified evidence to a TPG Admin, either intentionally, or unintentionally, will result in a six month suspension. Submitting demo(s) and/or screenshot(s) as your own, that belong to another player, will result in a six month suspension.
Any player disputed in a TPG match cannot release his/her demos to the public until a dispute has been closed by TPG. Any player who does, will be suspended for two weeks and if found cheating, this will be added on to your suspension.
Players cannot release private conversations/messages/e-mails between admins and players about TPG disputes to the public.
§7.7 Cheating Outside of TPG
§8.1 Rule Manipulation
If a player and/or team attempts to manipulate or exploit any TPG rule by any means necessary for other than what it was intended, TPG has the right to make a final ruling on the rule itself.
§8.2 Rule Changes
TPG reserves the right to modify and apply any rules as needed at any time, even retroactively. This includes changes due to software updates or releases and all other changes deemed necessary to the league. Major changes to the rules will be posted on our website and forums as needed. Teams should check the rules on a regular basis and prior to every match to ensure they are in complete compliance.
The TPG Administrators decisions are final.