§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.
Default Server Location - Central United States.
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.
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 20 minute period of time beginning when the half of play goes live, and ending when time expires.
Overtime - Two additional halves of play, with a shortened defined period of time.
Ineligible Player - Any player not on a team's roster and not an approved ringer, during regular and post season play. No ringers will be authorized during playoff matches. 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.
Ringer - The use of a player not on the team’s roster. Ringers must be registered at the TPG website with a steamID and may not be banned from the league.
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.
IRC - Internet Relay Chat. The only two official TPG channels are #tpg_league and #tpg_support, both of which are found on the Quakenet IRC Network.
§2 Player Information
§2.1 Player Names
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
The use of custom hud and victory music to obtain smaller mini map icons and shorter victory music is premitted in TPG matchs.
§2.3 Custom Game Content
jpeg_quality: Must be 100
net_graph: Must be 1
A short but non-comprehensive list of CVARs which should not be changed outside the listed values.
mat_picmip 0, 1 or 2
cl_detaildist 1200 or higher
cl_detailfade 400 or higher
§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.
VPN / IP address masking in TPG is not allowed for any reason.
§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 six players. Rosters remain unlocked during preseason.
Any team having two or more persons suspended during the same season, due to cheating or unsportsmanlike conduct will 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 48 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 five. 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 Thursday at 9:00 PM Eastern Time.
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.
The owner/captain/leader is required to contact the opposing team within at least 12 hours of the scheduled match default time to discuss match information. To include, but not limited to match time, server information, sourceTV, etc.
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 whose opponents have failed to attempt to contact them via the TPG Scheduler 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 your team receives a forfeit loss your team will be considered inactive. 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.Teams who are marked inactive and given a forfeit loss are allowed to file a support ticket or join #tpg_support on IRC to request immediate reactivation and rescheduling against the next available team.
Matches that need to be rescheduled must be played within four days of the default day and time.
§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 (Thursday, 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 in #tpg_support on IRC 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 to #tpg_support 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. The exception to this rule is if no other teams have forfeit wins or bye wins for that week.
§4.2 Player Eligibility
Players must use the Steam ID and game handle indicated on their team's roster for match play.
Player eligibility must be verified before match time. Matches must be suspended until player eligibility can be verified. Any disputes regarding an ineligible player that are reported after a match is complete will be disregarded.
Typing "Ready" indicates both teams accept their opponent's players and server config being used. The exception to this is if a player is using a Steam account which does not belong to him in order to bypass the roster lock. In that case, he is still ineligible for participation.
Matches are to be played 6v6. Participating teams may play one player short (e.g. 6v5) or use one ringer if both teams agree. Note* Teams may use only one ringer per match up to two times per season.
Note: TPG League requires a team roster consisting of six or more 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, etc.) is completely acceptable and recommended.
§4.4 Match Screen Shots
Both team Captains must verify the Steam IDs of all players in the server by typing STATUS in console,and capturing a screen shot. Along with those, end round score screenshots must be captured and must be uploaded to report your teams scores.
All players must a take a screenshot at the end of each half showing the final scores for that half and net_graph 1. If a player leaves the half early then he must take a screenshot showing the scoreboard and net_graph 1 before exiting.
§4.5 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
- STV delay is verified to be set at a minimum 120 seconds (STATUS in console)
- Servers team Captain must take a Rcon Status shot
- Players begin their individual demos
- The league config is executed
- 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.
- Match half is played
- Players stop their individual half demos
- Repeat for the second half of play.
In the event of a tie at the end of both halves of play, two 5 minute overtime half must be played. Each overtime half will consist of each team playing one half as allies and the second as axis.
§4.6 Match Results
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, IRC 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.
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.
Any team with multiple forfeit wins or forfeit losses may not be eligible for playoffs.
§4.8 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
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.
The team listed on the schedule as the "home" team has choice of server usage for both halves. The away team 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 away 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.
§5.2 Server Configuration
can be found at the DBlocker website: http://dblocker.didrole.com/.
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.
§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 60 milliseconds (ms), then the match will be played on the away team's choice of server located central in the United States. If both teams' server choices result in a ping imbalance greater than or equal to 60 ms, then the match will be played on the server which results in the lowest overall ping difference.
§5.4 Server Crashes
In the event the server cannot be restarted, the game must be suspended and team captains must report to the TPG IRC Support Channel (#tpg_support) or contact an admin via TPG DoD:S 6v6 Steam Group.
§5.5 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.
TPG uses Sentinel for cvar and file consistency all servers MUST have this installed to your match servers.
§5.6 SourceTV (STV)
If the opposing team requests the STV the team leader has a maximum 48 hours to deliver STV.
All disputes must be filed within 24 hours of match completion. Disputes can only be submitted by team owners, leaders, or designated match reporters.
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.
*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.
An appeal of an admin's ruling on a dispute may only be filed if there is a conflict of interest between the admin handling the dispute and the team(s) or player(s) involved; if proper TPG procedures were not followed; if the TPG admin behaved in an inappropriate manner; or a rule has possibly been misinterpreted.
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
§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 for a minimum of four games.
§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 rules 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 a minimum one game suspension.
Class limits violated:
Half(s) are to be replayed.
Team size limit violated:
Half(s) are to be replayed.
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.
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 removal from the league.)
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) caught using a map/model exploit or roofing:
Half(s) to be replayed.
Player fails to record valid demo(s):
Failing to record a valid demo for one half will result in a two game suspension.
Failing to record a valid demo for both halves will result in a four game 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 the duration of the current season.
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 valid requested 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 two game suspension of the team Captain.
Use of spectator:
Once a match has gone live the use of spectator is deemed illegal. Any player found to be using spectator to avoid the spawn timer will be suspended for one game and the match will be overturned.
*Note: The only exception to this rule is if a player has been grenaded at the moment of a full map capture.
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.
"Roofing" or any other form of map manipulation which involves gaining access to areas outside of the standard map limits through the use of boosting and other methods is considered illegal. Boosting a player, sky-walking, or the use of any map exploit is strictly prohibited.
If you have questions about areas of a particular map, please contact a TPG admin before match time.
Model exploits are not to be used.
§7.6 Altering/Manipulating 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.
§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.