A. League Information updated: Tue, 1/26/16

  • A.1.­­ UGC's Team Fortress 2 Highlander League was created to offer an organized competitive environment for players of all experience levels to battle for the purpose of having fun while improving their skills and teamwork.­
  • A.2.­ UGC is committed to serving the community's needs. Rules and League policies are set in consultation with the players, teams and community which we serve. All suggestions, opinions, questions and comments should be directed to league administrators. A current list of league administrators can be found here on our ­Staff Webpage. Team leaders are encouraged to post league suggestions in the Team Leaders forum. Every member in our community is also encouraged to make suggestions in the League Suggestion forum. We are continually striving to make this league a better place for every member of the community.
  • A.3 HL TF2 Terms & Definitions
    • Default Match Day: Monday
    • Default Match Time: By Region
      • North American divisions - 9:30pm EST - 8:30pm CST - 7:30pm MST - 6:30pm PST
      • European divisions (CET is in effect from October 28th through March 31st)
        • 2 EAST Teams = 19:00 CEST/CET
        • 2 WEST Teams =  21:00 CEST/CET 
        • 1 EAST vs 1 WEST Team = 20:00 CEST/CET 
        • Teams leaders can set their team's time zone from the leader panel. Time zone changes will be prohibited past Week 2. Please see your Division Admin if there is an issue with your Time Zone setting after the lock. Please specify time zones in all communications so that there is no misunderstanding.
      • South America division - 21:00 UTC-3
      • AUS/NZ division - 8:00pm Sydney Time
      • Asia - 9:00pm Seoul Time
    • Default Team Size: 9 players
    • Minimum Match Team Size: 7 players
    • Maximum Players on Team Roster: 21 players

TeamFortress 2 League Common Rule Base

Published on June 24, 2016   6:06 AM Eastern Time Change log

1. Class Limits, Maps & Weapons updated: Mon, 3/21/16

1.1 Class Limits - Each TF2 league within UGC has it's own set of limitations on how many of each class you are allowed to use during a match. Please refer to the grid below for more details.

Highlander 6v6 4v4
1 of each class 1 Medic, 1 Demo, 1 Engie & 1 Heavy
2 of any other class
1 of each class, however teams cannot use Medic + Heavy at the same time.

1.1.1 Switching classes during the game is allowed, therefore class limits apply to players that leave the spawn room or engage in play in any way. The spawn room is defined as the actual room that the players spawn in. Some maps, such as cp_steel (blue side)  or cp_gravelpit (blue side) have an additional area outside of the spawn room that is protected by gates. This area is defined as your team's base.­ Class limits outlined above apply to your team's base.

1.2 Player Count - Each TF2 league within UGC has it's own set of limitations on how many players can participate in a match and how many players can be rostered on a team. Please refer to the grid below for more details.

Category Highlander 6v6 4v4
Default # of players for matches 9 6 4
Minimum # of players for matches 7 5 3
Maximum # of players per roster 21 15 10

1.3 League Maps - ­UGC plays league-worthy maps, which may include AD (Attack Defend), CTF (Capture The Flag), PL (Payload), KOTH (King Of The Hill) and Standard CP (Command Point Maps). Each map type has specific gameplay settings for timelimit and win conditions. Gameplay settings are controlled by server config files for each map type. Some map types will end when one team reaches a cumulative score, even if the config does not stop the match.­ See each map type below for details.

1.3.1 Teams must play the map listed on the schedule page for each given week. Teams are not permitted to change the map for any reason.

1.3.2 Stopwatch maps (aka Attack/Defense and Payload Maps)

Examples: cp_steel (Attack/Defense) & pl_badwater­ (Payload)
Configs: ugc_HL_stopwatch.cfg, ugc_6v_stopwatch.cfg & ugc_4v_stopwatch.cfg

Match Play: Stopwatch maps are played in 2 halves with a potential overtime round if there is a tie after 2 halves. Each team attacks and defends one time in each half. The Home team decides whether to attack first or defend in the first half.­ Teams should swap sides in the second half.

Example
1st half: Team A attacks and Team B defends then Team B attacks and Team A defends
2nd half: Team B attacks and Team A defends then Team A attacks and Team B defends.­
Overtime Round: If each team wins a half, the scores will be tied at 1-1. The overtime round should be played just like the 1st half. Team A attacks and Team B defends then Team B attacks and Team A defends.

Winning the half (or OT round): A team is considered the winner of the half if they have secured more checkpoints (or control points) than the other team or if they controlled the same number of checkpoints (or control points) in a faster time. 

Example (pl_badwater)
Team A secured all 5 checkpoints in 7 minutes and 32 seconds. Team B was able to secure all 5 checkpoints in 6 minutes and 58 seconds. Team B would be considered the winner of that half and would be awarded 1 point towards the final scoring.

Winning the match: A team is considered the winner of the match if they win both regular halves OR if they win one half and the overtime round.

Scoring:­ Each half won counts as 1 point and winning the overtime round counts as 1 point. Possible match scores ­are 2-0 or 2-1.

­1.3.3 Control Point maps ­

Examples: cp_badlands & cp_process_final
Configs: ugc_HL_standard.cfg,  ugc_6v_standard.cfg, &ugc_4v_standard.cfg

Match Play: Control Point maps are played in 2 halves (each consisting of up to 7 rounds). Each round ends when one team captures all of the control points. Each half ends when one team wins 4 rounds or the 30 min time limit is reached. Possible scores for a given half: 0-0, 1-0, 2-0, 3-0, 4-0, 1-1, 2-1, 3-1, 4-1, 2-2, 3-2, 4-2, 3-3, or 4-3.

Overtime Round:­ If the score is tied after 2 halves an overtime round must be played to decide the winner. The winner of the OT round is determined by whichever team can capture all the control points first.

If neither team manages to capture all control points during the OT round, a special second OT round is to be played. In this round the first team to capture the center control point will win the match. Please note: The configs will not stop the match after one team captures the center control point in the special OT round. You will need to stop the match manually by executing the ugc_off.cfg file.

Winning the match: The winning team is the first to win 5 cumulative rounds, or the team with the highest score after two full halves have been played.

Scoring: Each round won counts as 1 point. Possible match scores are 1-0, 2-0, 3-0, 4-0, 5-0, 1-1, 2-1, 3-1, 4-1, 5-1, 2-2, 3-2, 4-2, 5-2, 3-3, 4-3, 5-3 or 5-4.

­1.3.4 KOTH - King of the Hill maps ­

Examples: koth_viaduct_pro7, koth_ashville_rc1
Configs: ugc_HL_koth.cfg, ugc_6v_koth.cfg & ugc_4v_koth.cfg

Match Play: KOTH maps are played in 2 halves (each consisting of up to 5 rounds). Each round ends on a timer. Whichever team owns the control point when the timer runs out is considered the winner of that round. Each half ends when one team has won 3 rounds. Possible scores for a given half: 3-0, 3-1 or 3-2. Please note: A single half cannot result in a tie score.

Overtime: If ­teams are tied after 2 halves (example: Team A wins 3 rounds in the first half and Team B wins 3 rounds in the second half), a single overtime round must be played to determine the winner. Whichever team owns the control point when the timer runs out is considered the winner of the OT round.

Winning the match: The winning team is the first to win 4 cumulative rounds. Please note: The winning team must have won 4 cumulative rounds to end a match.

Scoring: Each round won counts as 1 point. Possible match scores are 4-0, 4-1, 4-2 or 4-3. 

1.4 Weapon and Item Restrictions - ­Players may use any weapon or item in TF2, except for those excluded by the official whitelists. This list may change during a season due to patches and new releases by Valve. Any new weapons or items that are released by Valve during a regular season are automatically banned until the next season.

1.5 Picking up weapons - With the Gun Mettle update in July 2015, weapon pickups were introduced to TF2. Players are not permitted to pickup dropped Medic secondary weapons under any circumstances. This includes; the Medi Gun, the Kritzkrieg, the Quick-Fix and the Vaccinator. Please note: If you have SourceMod installed on your server you can use the following command to prevent dropped weapons from being picked up sm_cvar tf_dropped_weapon_lifetime 0. This SourceMod command will prevent all weapon pickups.

2. League Schedule updated: Wed, 12/2/15

2.1­ Schedules for each week are typically posted 4-5 days prior to the default match day. Scheduling is dependent upon all matches being completed and reported from the prior week. Failure to play a match on time may delay the schedule for next week for your division. Please make all efforts to play your matches on time.

2.1.1­ Default Match Day and Time - See section A of the rules at the top of this page.

2.1.2 Moving a match - ­Leaders from both teams may agree to move a match to a different date and or time. This agreement must be documented in the Match Comm panel. If team leaders cannot agree on a new date and or time then the match must be played on the default date and time as dictated by your region. See section A.

2.1.3 ­Late Matches - Matches must be played no later than the deadline outlined in Section A (typically 2 days after the default match date/time). If you are unable to play your match by this time please contact your Division Admin immediately. Matches reported after the deadline will not be accepted.

­

2.2 Match Comms - Team leaders are required to post in the Match Comm panel every week. The Match Comms must be used to coordinate the date of the match, the time of the match, the server(s) to be used for the match and any possible ringers/mercs that need to be used in the match. Match Comms serve as the official record of your match and will be the only evidence that Admins use in reviewing a match dispute. Forfeit (default) wins ­will not be accepted if the Match Comms panel was not used!

2.2.1 In the interest of good sportsmanship, team leaders should post in the Match Comm panel at least 24 hours prior to the match to give ample time for responses. If you cannot post in the Match Comms for any reason or do not receive a response from the other team leader in Match Comms please try adding them on Steam prior to the match. Copy and paste your steam chat into the Match Comms. Contact your Division Admin if need help contacting the other team.

2.2.2 The match comms are built into your team leader 'My Match' web page. Simply ­log in as team leader to post. Match Comms are also available to all players, by using the steam login on UGC website.

2.3 UGC's TF2 leagues operate as a season-based competition. In a given year, UGC will offer 3 seasons: 2 full seasons comprised of 8 weeks of matches and a playoff period which can last up to 5 weeks and 1 shorter 8 week season. 

2.3.1 Regular Season - ­Scheduling during the regular season is based on team rank each week.­ Teams will not play the same opponent twice during the regular season.

2.3.2 Playoffs - ­Participation in playoffs will be limited to a certain number of teams and entry into playoffs will be based on the final rankings after all the Week 8 matches have completed. Typically the Platinum and Gold divisions will play in a Double Elimination bracket and all other divisions will play in a Single Elimination bracket. The number of teams that are eligible to participate in the playoffs will be determined by the size of your division. Typical counts are Top 8 teams for Double Elimination and Top 16 teams for Single Elimination. Exact playoff format may vary by league, division and season.

2.3.3 Playoff Finals - Final Matches are played as a Best of 3 Maps (Maps are played as 1 half only)

  • Map 1: Home Team picks Map 1. Visiting Team picks their starting color on Map 1. Map is played on Home team's server.
  • Map 2: Visiting Team picks Map 2. Home Team picks their starting color on Map 2. Map is played on Visiting team's server.
  • Map 3: If a Tiebreaker is needed, teams will play a specific map chosen by Admins. Home Team picks their starting color. Map is played on Home team's server.

2.3.4 Playoffs & Forfeits - ­­Forfeits during playoffs are strongly discouraged. In the interest of good sportsmanship and fair play, please make all attempts to ensure that your playoff match is played. Please contact your opponents via Match Comms and steam well in advance of the default match date and time. If your match cannot be played for whatever reason please contact your Division Admin immediately. The forfeiting team will be eliminated from the playoff bracket.

2.4 Roster Lock - ­Each team's roster will lock prior to the start of playoffs, at Week 7 default match day. Teams may not add any new players until the end of playoffs.

2.5 Bye Week - If your division has an uneven number of teams, it is likely that 1 team in your division will receive a bye week. A bye week means that there is no opponent to schedule against your team and therefore you do not have to play that week. Bye's are typically given to the lowest rankings teams that have played all of their matches up until that point. If you receive a bye, your team will show in the schedule versus "BYE WEEK." Each team that receives a bye will also get a free win that week with full match points. No team will receive more than 1 bye per season.

2.5.1 Requesting a bye - ­­Teams can request a bye from a week's scheduling with certain restrictions. Teams that request a bye will not be scheduled and will not receive any points from the bye.

3. Division Placement & Rosters updated: Thu, 6/2/16

3.1 Division Placement:­ Teams may request a specific division but ultimate placement will be decided by a Head Admin. Placement is based on your team's prior roster history with most emphasis given to the past 3 completed seasons. We consider your experience in a division as being established once you have been on a team that secured 3+ legitimate wins (meaning played wins) in that division. Scrim logs, class assignments and backups are not taken into account for placement. ­Note: 6v6­ and 4v4 ­experience is not considered 1:1 with Highlander when deciding team placement. Admins reserve the right to move your team up or down a division at any point during the season.­­ 

3.1.1 General placement guidelines

Platinum - Is the top division in the league. Entry to this division is very limited and teams must earn their right to play and stay in this division. Players should have multiple seasons of higher level competitive TF2 experience. Rosters are expected to be a mix of players with experience on established Platinum teams and players from high Gold teams.

Gold - Is traditionally the seeding division for Platinum, and is the TOP division for current 6v6 and 4v4 leagues. Rosters are expected to be a mix of players with experience on mid to low Platinum teams, established Gold teams and high Silver teams.

Silver - Is the seeding division for Gold. Rosters are expected to be a mix of players with experience on mid to low Gold teams, established Silver teams and high Steel teams. Teams are permitted to have no more than 3 Gold players (or 1 Gold player and 1 Platinum player). ESEA-I and ETF2L Premiership players are not permitted to play in Silver. See rule 3.2 for more information.

For HL S19, the Gold division has been removed from North America. With the absence of Gold, the restrictions of Gold & Platinum players allowed into Silver will be relaxed to 4 Gold players per team (or 2 Gold players and 2 Platinum players).

Steel - Is the lowest “skill division.” Rosters are expected to be a mix of players with experience on low Silver teams, established Steel teams and high Iron teams. Teams are permitted to have no more than 3 Silver players from teams with established records (3+ legitimate wins) in the past 4 completed seasons. Teams are not permitted to have any players with established experience in Platinum or Gold. ESEA-I and ETF2L Premiership players are not permitted to play in Steel. See rule 3.2 for more information.

Iron - Is a “special case division” for teams with no competitive experience or teams that could not secure 3+ legitimate wins in Steel in a prior season. Teams are not permitted to have any players with any experience in Platinum, Gold or Silver from any season. Rosters in Iron are strictly monitored to ensure that these standards are being met throughout the season. ESEA-I and ETF2L Premiership players are not permitted to play in Iron. See rule 3.2 for more information.

3.1.2 Regional placement - Teams must have at least 75% of their players housed in the region that they wish to play in. Example for South American teams wanting to play in North America - Please use this map as a guide. In order to be placed in the North American division, at least 75% of your players must be housed within the Dark Blue and Light Blue sections on the map.

3.2 ­Invite/Premiership Player Limit - Each league and division has a set limit to the number of Invite/premier players allowed on a team's roster.­ We define Invite/Premiership as any player in ESEA-I or ETF2L­ Premiership participating in the current season and prior 3 seasons of these respective leagues. For limits by league and division please refer to the grid below.

Division NA HL EU HL 6v6 4v4
Platinum No limit No limit NA NA
Gold NA 1 No Limit No limit
Silver 1 0 1 1
Steel & Iron 0 0 0 0


3.3 Player eligibility - ­All players on a team must be listed on their team roster at least 18 hours prior to the agreed upon match date and time in order to be eligible to play.

3.4 Roster Confirmations - Teams must check rosters and work out roster issues before the match begins. Be honest with your opponent about your player's roster status. Once both teams are set to Ready, we ­consider this an agreement to move forward with all connected players (including any unrostered players that might be in the server).

3.5 Ringers (mercs)­ and Unrostered­ Players - Any player not listed on your roster is not permitted to play in your match. If you need to use an unrostered player for any reason, written permission from the leader of your opponent team is required. This permission must be documented in the Match Comm panel.

3.5.1 When requesting approval to use an unrostered player, you are required to provide links to Steam profiles (and UGC player profiles if available) to the leader of the opponent team prior to the match time.

3.5.2 Once a specific unrostered player has been approved in writing in the match comms, that player may particpate in the entire match and cannot later be disputed.

3.5.3 Teams do not have to allow any unrostered players in the match if they do not want to.

3.5.4 UGC Admins will never force a team to allow an unrostered player.

3.5.5 If the other team is using an unrostered player and you did not give explicit written permission in the Match Comms for that player to participate in the match, please ask the leader of the opponent team to remove this player from the server. If the unrostered player does not leave the server by 15 minutes past the agreed upon match time, please contact your Division admin immediately. 

3.6 Late Joining Players - ­Once a match is live, only rostered players may join the server (and only when a substitute is needed or your team has less than the default number of players in Rule 1.2.­ NOTE: We do not expect team leaders to check eligibility of late joining players during a live match. If a late joining player is later determined to be an unrostered player, any scores accumulated while that player is in the server will be nullified.­

3.7 Team participation - Players may only be rostered on 1 team per league at a time. This rule extends to a person and not a specific Steam account.

Examples

1.) A given player can be rostered on 1 HL team, 1 6v6 team and 1 4v4 team at the same time.
2.) A player cannot be rostered on 2 HL teams.

3.8­ Alias accounts -­­ Additional steam accounts (also known as alias accounts) owned by the same player may not be rostered without explicit admin permission.

3.8.1 Players who are found to be using an alias account (without admin approval) will be subject to suspension and/or banishment from the league. Suspension will also apply to the­ player's main account.­ Teams who roster such players may be subject to suspension as well.

3.9 Roster Lock - ­­A roster lock will ­be in effect starting on the default match day of Week 7­ of the regular season. Players cannot be added after this lock for any reason.­ Rosters will reopen once playoffs have ended.

3.10 Team names - Teams are encouraged to be creative when naming their teams but should refrain from using team names that could be considered offensive. Admins reserve the right to change your team name if it is considered offensive. Repeated offenses may lead to player/team suspension. 

3.11 Roster names - Each player on the roster should be listed by the name that they most commonly go by in the community.

3.11.1 In-game name and clan tag - ALL rostered players are now required to change their in-game name to match their rostered name and to wear their clan tag in all casted matches. If your opponent team refuses to follow this rule, please contact your Division Admin immediately.

3.11.2 Failure to follow this rule can result in player/team suspension. 

3.12 Team & Player Avatars - Use of offensive avatars on our site may lead to player/team suspension. 

4. Servers updated: Fri, 6/3/16

4.1 ­­Server responsibility:­­ It is both teams' responsibility to ensure a server is available to play the match.­ If the Home team does not have a server, the Visiting team may host.­ If neither team owns a server, it is both teams' responsibility to secure a suitable server for the match.­ UGC has a limited number of servers for matches and any team may request one by.­ Servers are loaned on a first-come-first-serve ­basis.­ To rent a UGC match server click here.

4.1.1 If neither team has a server and no UGC servers are available, the match must be rescheduled to a date when a server will be available. If this occurs, please notify your Division Admin immediately.

4.1.2­ The Home team (listed first in the schedule) has choice of server for the first half, and for the third (OT) round. The Visiting team (listed second on the schedule) chooses which server to use in the second half.

4.1.3 ­The team providing the server must provide the ­address and password in Match Comms or an alternate messaging source at least 15 minutes before match time.

4.2­ Only dedicated TF2 servers from professional hosting companies may be used in an official UGC match.

4.2.1 Home-based servers of any kind and quality are strictly prohibited from being used in official UGC matches. If you are caught using a home-based server, matches played on your server will be overturned and you will lose the right to be home team for the duration of the season.­

4.2.2 Server location - ­Servers must be located in the geographical region of your division. Examples: North American division matches must be played on servers located in the United States, European division matches must be played on servers located in Europe, Asian matches must be played on servers located within the Asian region and Aus/NZ matches must be played on Australian­ servers. South American division matches should be played on South American servers unless a better server is available in Central or North America. A Canadian server may be allowed for North American division matches, if approved in advance by Admins.

4.3­ Servers must have a MINIMUM of 19 available slots. This is to accommodate both teams and SourceTV.­

4.4 Whitelists and Configs -­ All UGC matches must be played on servers running the official UGC item whitelists and configs found in our files section. It is the responsibility of team leaders and server administrators to ensure that these files stay up to date on your server. If a team feels their opponent's server is running outdated versions of these files, they must first contact the opponent team’s leader to resolve the issue. If a problem still persists, then an admin should be contacted. Make sure to properly document all conversations.­WARNING: Once both teams begin a match by setting their status to Ready, both teams accept current server settings even if they are incorrect. Make sure to resolve these issues BEFORE setting your team to Ready!

4.4.1 If during the game you notice a player using a banned weapon or an officially banned cosmetic item, pause the match (this will not count as a normal pause) and ask them to stop using the item. If they refuse, please contact an admin immediately. Likewise if you are unable to use a weapon that is supposed to be allowed, pause the match (this will not count as a normal pause) and ask them to rectify the issue. If they refuse or are otherwise unable to do so please contact an admin immediately. Moving the match to a new server may be required if the host team is unable to update their whitelist in a timely manner. New cosmetic items (not yet listed in the official whitelist) are not subject to dispute in this manner.

For the most up to date copy of the whitelists and configs, please refer to your league's download page: HL Downloads6v6 Downloads & 4v4 Downloads.

4.45 VAC (Valve Anti Cheat - Secure Mode) must be enabled and sv_pure 2 must be set for all matches.­

4.6 ­Mods - Manimod, Sourcemod, AMX Mod and AMXX Mod and the like are allowed as long as they do not interfere with the match. A csay command here and there will be tolerated, as long as it was in the admin mod config and is not insulting to anybody. Admin mods may only be used for setting the config, checking the amount of time left, and changing maps. Please disable all plugins that could affect any aspect of the match, including Donator plugins. If any player from the opposing team (the Visiting team) is kicked, banned or moved to Spectator during a match for any reason due to any installed mod, the hosting team will forfeit all points earned during the round, unless the Visiting team agrees otherwise.

4.7 Server connection issues and crashes -­ Should a server have connection issues (including but not limited to: both teams experiencing extreme packet loss ­or lag)­ or if the server crashes outright and the team captains agree in writing that the server has become unplayable, the round will be stopped and restarted on another server. When a server crashes, any rounds scored­ must be retained. Rounds that have not yet concluded will be voided. Please see below for examples.

Examples:

5CP Map:­Your server crashes after 15 minutes of gameplay. The home team has ­capped all 5 control points 3 times (score is 3-0). The home team is in the process of capturing the middle command ­point in ­the fourth round when the server crashes. The score at the time of the crash was 3-0. Partially captured rounds are not counted. Teams should move to a new server and start Round 4 over again.

PL maps: The game is in the first half and the home team has just finished their attack round setting a time of 7 minutes and 30 seconds. Teams switch sides and the visiting team is now attacking. The server crashes 3 minutes into the visiting team's attack round. The visiting team's attack round must be started over. They will still have a goal of 7 minutes and 30 seconds set by the Home team.

Koth maps: The home team has won 2 rounds and is currently controlling the point in the third round. The server crashes while the home team has control of the point (with 30 seconds left on the clock). The score is considered to still be 2-0 and the third round must be replayed.

If your server crashes and both teams are not able to come to a resolution on how to proceed, please contact your Division Admin immediately. Server crash disputes need to be handled live while they are occurring.

4.8 Server Pauses - ­­Each team is allowed one server pause per half to deal with unexpected player drops from technical issues or to deal with a server-wide connection issue. Each team is allowed 1 additional pause in an Overtime round. Pausing should not be used for minor issues such as 1 player experiencing a ping spike.

4.8.1 Anyone may pause the match, but that person must announce the reason for the pause immediately after it is initiated or, if possible, before the pause is initiated.­ Additionally, a match may only be unpaused by the team that initiated the pause.­ The other team may not unpause the match unless otherwise specifically instructed by an Admin.­

4.8.2 All unpauses should be preceded by a 15 second warning through in-game chat.­

4.8.3 A pause may last up to a maximum of 15 minutes. *NOTE* 15 minutes is a guideline, not a strict limit.­ If teams cannot come to a resolution after this 15 minute period has passed, then an admin must be contacted.

4.9 ­If it is found that a team intentionally crashed or restarted a server, they will automatically lose the match and further action will be taken, including temporary or permanent suspension.

4.10 Team Ping Differences - ­If the team providing the server has an average TEAM ping greater than­ 100ms (over the other team's average ping), the match must be moved to the other team's server or a neutral server, such as a UGC server. If the hosting team refuses to move the match, please contact your Division Admin immediately. This rule does not apply to teams nor players that are playing outside of their home region. (such as a Euro player in an NA division).

4.10.1 Ping manipulation (also known as ping masking) - Ping manipulation of any kind is prohibited. This includes but is not limited to using console commands to alter the value of your ping.

4.11 SourceTV is required to be active and recording for all official UGC matches.­ The STV-delay must be 90 seconds and cannot be altered. The UGC server configs will auto-record a SourceTV demo, be sure to stop recording by executing the ugc_off.cfg file after your match has completed.

4.11.1 SourceTV Spectators - The team hosting the match is required to give the IP (and password) of the SourceTV proxy to their opponents. The host of the proxy is also required to have at least 3 spots open. The proxy may be password protected.

4.11.2 If the SourceTV proxy is unable to handle spectators on a team server, you must ensure that an STV is recorded of the match. If this is the case, you must make a copy of the STV demo available to your opponent within 48 hours.

4.11.3 Live spectators in the server are not allowed. Please set a join password on the server and request those not in the game to refrain from joining.­ Spectators are encouraged to watch the match through SourceTV. ­UGC Admins are exempt from this rule spectator rule. Any admin that requests to live spectate a match must be accepted to the server.

4.11.4 It is the responsibility of both teams to check that SourceTV is running before readying up and playing their match. If SourceTV was not running after both teams ready up and the match was played, then it cannot be disputed afterwards.

4.11.5 STV demos must be saved for the entire active season.

4.11.6 ­All teams are required, if directed by ­an Admin, to submit SourceTV (and or POV) ­demos to each other or to an admin within 48 hours after the last round of the match was played.­­

4.11.7 ­Failure to provide an SourceTV demo (and/or POV demo) to an admin can result in a match being overturned or a player/team suspension.

5. Match Play updated: Thu, 6/2/16

­

­

5.1­ Minimum player count - Each team must meet the minimum player count requirements spelled out in Rule 1.2 in order to ready up and play the match. Teams are allowed up to 15 minutes past the agreed upon match time to gather the minimum number of required players. In the interest of fair play and good sportsmanship we encourage teams to be flexible and allow additional time for your opponent to gather their players. We also ask teams to consider rescheduling should an issue arise at the last minute and one team is unable to field the minimum number of players.

5.1.1 If your opponent team has not readied up by 15 past the agreed upon match time, please contact your Division Admin immediately.

5.2 Mid-match­ break - Teams are encouraged to take a break after the first half of the match is completed. This break should not last more than 10 minutes. Team leaders are encouraged to remain in communication with one another during the break, especially in the event that 10 minutes becomes insufficient. If a team is refusing to ready up after 10 minutes please contact your Division Admin immediately to resolve the issue.­

­

5.3 Reporting Matches - Upon the completion of a match,­ the­ winning team must ­report the scores via the UGC website. Only team leaders with a dedicated team leader login can report match scores. To ensure that accurate scores are reported, please pay close attention to the submission form. Also, please read section 1.3 of the rules and the weekly news to understand how scoring works for the type of map being played.

5.3.1 Winning teams must report Match Scores 11:59pm (your local time zone) on the day following the default match day. Contact your Division Admin immediately if you can not meet that reporting deadline. If the winning team leader has not reported a match result by 24 hours after a match has been played, it is acceptable for the losing team to submit the Match Scores. Failure to play and report a match by 11:59pm (your local time) on the 2nd day after the default match day and neither team has contacted a UGC Admin, both teams may receive forfeit losses for that match.

5.3.2 If you have made an error in reporting the scores, please contact your Division Admin immediately.

5.3.3 ­When reporting scores, the team leader ­will be able to enter a Match­ Writeup for others to read. Please remember that these comments will be publicly available for all to view, therefore please be polite. ­The Match­ Writeup­ field is not to be used for submitting disputes against the other team. If an issue occurred ­in your match that requires admin intervention, please contact your Division Admin once the match has concluded.­

­

5.4 Forfeits (default wins): If a team can not supply the minimum number of players required to play a match by15 minutes past the agreed upon match time, ­the opposing team may request a forfeit.­ If you think that your match is going to result in a forfeit, please contact your Division Admin immediately. The admin may request a group Steam Chat between leaders from both teams to understand the issue that is preventing the match from being played. ­Please try to be reasonable and fair with your opponents, playing a match is always preferred over a dispute or a forfeit win.

5.4.1 Documented proof of the situation that lead to the forfeit MUST be posted in the Match Comm panel. This includes (but is not limited to) in-game screenshots (with time stamps) ­showing the other team­ did not have enough players by the appropriate time as well as any relevant chat logs between the 2 teams. You must also demonstrate that you exhausted every means necessary to attempt to get the match played. Failure to document the Match Comms regarding your forfeit will result in the match remaining unplayed.

5.4.2 Scoring for forfeits - Teams will receive the following Match Points for Forfeit Wins:
-Silver, Steel & Iron: +2.5 Match Points (If your opponent team has clearly dropped from the league prior to your match please alert your Division Admin immediately. If no other opponent is available to play against, you will be awarded +5 Match Match Points in this case). 

-Platinum & Gold: +5 Match Points

5.4.3 Penalties for Forfeits - Teams with 2 or more forfeit losses will be removed from scheduling. Teams removed may be temporarily set to Not Ready or permanently suspended at Admin discretion.

5.5 Match Abandonment - If an entire team leaves a match prematurely, that team forfeits the match as a whole (including every point scored). If a partial match has been played, the other team will be awarded full match points for the match only when the partial score is in their favor.

Control Point map example: The first half of the match has ended and the Home team is in the lead with 3-1. During the half-time the Visiting team decides to leave the match and not play the second half. The Home team will be award the win and will receive +3 in the Points For ranking column and +5 in the Match Points column. The Visiting team will receive zero points.

6. Player & Leader Responsibilities updated: Thu, 6/9/16

6.1 Sportsmanship - Good sportsmanship is an important part of this league and all teams should be treated with respect. 

6.1.1 Examples - Bad sportsmanship includes (but is not limited to) remarks that attack another player's ethnicity, sexual orientation, gender or religion. Another example of poor sportsmanship is spawn camping while ignoring the map goals, such as camping the enemy spawn while ignoring the cart on a Payload map.

6.2 Recording Personal Demos - ­All players in an official UGC match are required to record POV demos. This can be done by typing "record demoname" in console (without quotes). ­At the end of your match type "stop" (without quotes) in the console to end the demo.

6.2.1 All demos must be saved for the entire active season and must be provided to an Admin within 48 hours of a request. 

6.2.2 Approved file sharing sites - When a POV demo is requested by an Admin, it must be uploaded to one of the following approved file sharing websites: Dropbox or Google Drive.

6.2.3 Random POV Checks - Admins will check for POV demo recording compliance on a weekly basis. Teams will be chosen at random and all players who participated in the match that week will be required to submit their demos. Admins will contact Team Leaders directly, and Team Leaders are responsible for collecting the demos and making them available to the Admins.

6.2.4 Punishment for POV Non-Compliance - Failure to provide a POV demo upon admin request will result in the following actions for each player that fails to submit a POV demo:

1st Offense - 1 week suspension
2nd Offense - 2 week suspension
3rd Offense - 8 week suspension

6.2.5 Players who receive a 1st offense for not providing a POV demo will be subject to repeated spot checks throughout the season to ensure compliance.

6.3 NA HL Platinum POV Demo Exchange - Each Team Owner may request a maximum of one POV demo from any player in the match. This request should be made Team Owner to Team Owner within 24 hours of match completion and the POV link must be shared within 48 hours of the request. A record of the request must be kept. At this time, this program is limited to the North American HL Platinum Division only.

6.3.1 Any POV demos exchanged in this program are considered private unless specifically released to the public by the recording player. This means that POV demos should not be reproduced (in whole or in part as video clips) in publicly accessible locations, and the original link cannot be shared outside of your team.

6.4 ­Team switching and Spectating - Switching to your opponent's team or going to spectator during a live match is strictly forbidden and players who do so may be suspended.­ Points earned that round may be removed if it is ruled that team switching affected the match.­ If you need to go AFK during a match, do not switch to spectator.

7. Cheating & other offenses updated: Fri, 6/24/16

7.1­ Cheating of any kind is strictly prohibited. Our scope of review for cheating is not limited to official UGC matches. There are so many methods of cheating it is impossible for us to list them all. However we will list some of the most common below.­

7.2 Map, weapons and­ game engine exploits - ­The intentional use of exploits of map flaws, weapons and game engine bugs are­ not allowed. Use of exploits in a match can result in either the round being replayed or the offending team may lose the round.­

  • Example #1: Engineer buildings may not be placed in areas in which the opposing team is unable to destroy them. This includes but is not limited to maps that allow­ you to build a teleporter inside the spawn room itself (such as on Ashville). Exception: Some maps, like cp_steel and cp_gravelpit, have a protected area outside of the spawn room which is still behind gates (this area is defined as your team's base). You are allowed ­to build engie buildings in your base (as long as it's not in your actual spawn room).­­
  • Example #2: Players may not shoot through solid surfaces or doors that are intended to be closed. This includes but is not limited to the A door on cp_steel. Splash damage through surfaces are that are meant to be permeable such as fences and grates is ok.
  • Example #3: Engies are not permitted to build a teleporter in the small closed off room at Red's last CP on pl_upward.

­

7.3 ­The use of ANY external program, wrapper or hook, be it a modified .dll, an .exe injecting hook, or ANY file or program that hooks on to the source engine and gives a player additional HUD information, attributes, abilities, or significantly alters gameplay is ILLEGAL and BANNABLE.­This includes specifically (but not limited to) the use of a wallhack, aimbot, autodet, anticonc, speedhack, third person view, esp of any type, radar of any type, and trueaim ("sniper dot" for non-sniper classes.)­

7.4 ­Using the server or console commands to give any part of your team an unfair advantage is cheating. This does not include scripts regarding flag status, class status, health status, incoming calls, or the like. If you are in doubt about a particular script, post it on our forum for advance approval by an admin.­

7.5 VAC Ban policy (Effective for all new VAC bans after May 13th 2015)

7.5.1 Players with VAC bans - Players who receive a VAC ban of any type after May 13th 2015 will be automatically banned from rostering in any of UGC's TF2 leagues unless cleared by an Admin.

7.5.2 Source Engine VAC Bans - A player with a Source Engine VAC ban (that prevents the player from joining a TF2 VAC secured server) will be banned from the league for a period of 6 months from the date the account is VAC banned. In all cases, the ban period applies to a person and not a single Steam account. Alias accounts created to evade this VAC policy will lengthen the duration of the player ban. After the ban period has expired, these players will be permitted to register a new alias account and continue participating in the league.

7.5.3 Non-Source Engine VAC Bans - A player with a VAC ban that does not impact their ability to connect to a VAC-secured TF2 server may appeal the ban policy by filing a support ticket under the "VAC Appeal" category. Players may be required to join a VAC-secured TF2 server. Once a player is cleared they may choose to roster their VAC Banned Steam account or they may choose to use a new alias account when approved by an Admin.

Other offenses

7.6 Aliasing (defined as playing under a different Steam account than your main account)­­ as a method to avoid a previous ban­, to hide your competitive experience from your opponent or to play in a lower division will result in a permanent league ban. Bans are issued to PERSONS not ­Steam IDs. ­

7.6.1 If you are caught aliasing in a lower division or you are ­rostered on more than 1 team in the same league with an alias account the following actions will be applied; a.) Your alias(es) will be permanently banned from the league and b.) Your main account will suspended or possibly banned.­

7.6.2 In an alias dispute the burden of proof is on the accused player(s), not the Admins. If a player cannot sufficiently prove the alias account is not theirs, they will be subject to a suspension or ban.

7.6.3 Sometimes there are valid reasons to play under an alias account and players may do so only with explicit Admin approval.

7.7 ­Account-sharing­ (defined as giving out your Steam username/e-mail and password  to a third-party to play as you in a match) is strictly prohibited.

7.8 Match Betting/Gambling - Team Leaders and individual players who are found to have bet on their own matches, regardless of the match outcome, will be banned from the league and any matches bet on must be replayed. This rule also applies to placing bets through alias accounts or other third parties. Punishment for betting on your own team may also extend to the entire team if multiple players are found to have taken part in the bet. If this occurs, the match in question will be overturned (when applicable).

7.9 Admins reserve the right enforce suspensions/bans at anytime for any reason whether a clear rule was broken or not. Suspensions/bans can result from (but are not limited to): Cheating, aliasing, account-sharing, impersonation of an Admin or another player, betting, posting personal information, and abuse/harassment. The scope of consideration for such punishment is not limited to official UGC matches. 

7.10 Punishment for Cheating - Players who are caught cheating in an official UGC match will be banned from the league for 1 year. When a player has been found guilty of cheating, the match that the dispute originated from will be overturned. The Anti-Cheat Team may also elect to review demos from prior matches that occurred within 2 weeks of the match that lead to the ban. If cheating is found to have taken place, those matches may also be overturned as well.

8. Match Disputes updated: Thu, 6/2/16

8.1 Match Disputes - If you feel a rule has been broken by your opponent during an official UGC match please make all attempts to get your match played before pursuing a dispute. We ask all teams to be reasonable and flexible with each other. This can include but is not limited to waiting an extra few minutes to ensure the match gets played or allowing your opponent to have additional pauses. Playing a match is always preferred over a dispute or a forfeit win.

8.1.1 Before submitting a dispute please try to contact your Division Admin to resolve the issue while it is happening live. If your Division Admin is not available please try reaching another admin from our Discord chat room. 

8.2 Submitting a Dispute - I­f no admin is available then your Team Leader should file a Support Ticket. Support Tickets can be filed from the Team Leader homepage by clicking on League Support > Support Tickets. Use the "Match Dispute" topic. All match disputes must be submitted within 48 hours after your match has ended. Disputes submitted after this deadline may not be honored.

8.2.1 If your Team Leader is unavailable to submit a dispute ticket then any individual player may also file a dispute ticket. To do so, use the Steam login button on the UGC homepage and from your Player homepage click League Support > Support Tickets. Use the "Match Dispute" topic.

8.2.2 Required documentation - The burden of proof in a dispute is on the team that submits the dispute. Please provide as much detail as you can in the dispute email. This must include a summary of the dispute, what rules you think were broken, screenshots, chat logs and STV (and/or POV demos).

8.3 ­While a dispute is pending, public discussion of the dispute is prohibited on the UGC forums.

8.4 Admins involved in a dispute - ­Any Admin who happens to play for a team that is involved in a dispute is not allowed to participate in that dispute due to conflict of interest.

8.5 Dispute Resolution - ­Admins will try to handle all disputes as quickly as possible, however some disputes may require more time depending on the complexity.­ Once a dispute has been resolved both teams involved in the dispute will be notified via the email we have on file for each leader.

8.5.1 Outcomes from match disputes are decided on a case by case basis and may include (but are not limited to): a forced rematch, score reversal, match reversal, and/or player/team suspension.

9. Team Rankings and Titles updated: Wed, 12/9/15

9.1 Ranking.­All UGC Teams are ranked on our current season's rankings web page. Rankings are reset after pre-season, so that only regular season matches are included in final rank calculations. Rank calculation is done using the values shown at the top of the rankings web page. The rankings page will automatically be updated as match results are accepted by admins each week of regular season matchplay.­

9.2 Title Playoffs.­Elimination playoffs are used after the end of regular season to determine the season's title winners or champions. The setup of these playoffs may vary slightly from season to season. Generally speaking, playoffs will be a 4 or 5-week single or double elimination bracket using rank seeding. Playoffs will be played on popular, mainstream maps.

9.2.1 ­After the last match in the regular season, playoff seeding is determined by regular season ranking of all teams as shown on our current season rank page.­ ­UGC admins will determine the final regular season rankings after including all approved match results prior to playoffs. Seeding will then follow rank numbers.­

9.2.2 ­Playoff Brackets - The current schedule web page will display playoff brackets during Playoff weeks.

9.2.3­ Playoff Eligibility - Teams are allowed to miss no more than two (2) regular season matches to be eligible for playoffs. If teams miss more than two, they can continue to play out the season but will not be included in playoff brackets.

9.3 Final Ranking.­- At the end of playoffs, a final season rank page will be kept for each season.­ This is separate from any titles won by teams in playoffs.­

9.4 Title Winners.­Teams that are awarded season titles as part of our playoffs will be listed on our web page. We will keep a durable record of all season title winners and champions on our league web page.

10. New teams updated: Sun, 12/13/15

10.1 To create a new TF2 team, goto our team signup page and complete the application process.

10.2 If your team is approved, it will be placed in a *New Teams division based on your region. Note: Teams in these *New divisions will not be scheduled to play matches.

10.3 In order to be scheduled for matches your team will need to be in one of the following divisions: Platinum, Gold, Silver, Steel, Iron or a Regional division.

10.4 To get placed in one of these divisions you must first have the default number of players on your roster for your league. See rule A2 at the top of this page for default player counts.

10.5 Once your team has the default number of players, the leader must submit a Division Change request from the leader panel. 

10.6 Admins will review the request and place your team according to the general placement guidelines outlined in Rule 3.1.1.

11. Rule Administration updated: Sun, 1/24/16

11.1 ­The Rules set forth on this page may be altered or updated at any time. It is the sole responsibility of every team/player to keep up to date with these Rules.­

11.2 Occasionally Admins may enforce a map-specific rule during the season. These rules will be posted in the weekly news. It is YOUR responsibility to review the news page.

11.3 Leaders/players should not take rule enforcement into their own hands. It is NOT up to you if your opponent should receive a forfeit loss for a given situation. Always contact your Divsion Admin for dispute resolution.

11.4 ­We reserve the right to interpret all of the Rules set forth on this page as we see fit in each situation. ­­