|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| Community Websites |
 |
|
| Game Mods |
|
|
| Tools |
|
|
|
|
|
| |
 |
|
|
|
|
|
TEAM FORTRESS CLASSIC 1 vs 1 RULES
1. League Information [top]
1.1. UGC's player Fortress Classic 1v1 Soldier Ladder was created to offer an organized competitive environment for rookie and veteran fortress players alike to battle for the purpose of having fun while improving their skills.
1.3. UGC is committed to serving the community's wishes. All suggestions, opinions, questions & comments can be directed to league administrators. The league administrators can be found here: Staff. Players can and should make suggestions in the forums. We will continually strive to make the league a better place for its participants and the community.
2. Scheduling Information [top]
2.1. Ladder Schedule
2.1. Match day/time for the 1v matches is determined by the players. Schedules shall be posted by Thursday, and players have until the following Wednesday to play and report scores. Match time/day may be negotiated on IRC, via email, on the UGC forums, etc.
2.2. Divisions
2.2.1. The 1v TFC Soldier Ladder may be subdivided with divisions based on player skill levels.
2.3. Title Shot and Title Matches
2.3.1. Players in the UGC TFC 1v1 ladder will compete on an ongoing basis for a ladder title.
2.3.2. Title shots will typically be awarded to the two players with the longest winning streak, regardless of their relative ranking within the division. Note that the ladder admin may choose to schedule a Title Shot match at their own discretion based on players' records and overall division balance.
2.3.3. Once there is a Title Shot winner they will be scheduled against the current Title holder. If the Title holder successfully defends their Title, they will advanced to the next division.
2.3.4. If there is no current Title holder (the title holder has moved up in divisions or has left the league) the player will be scheduled against the next Title Shot winner. Once a player has won a Title Shot match, they are guaranteed a Title match, even if they lose subsequent matches in the interim. The winner of the two Title Shot players will then become the Title holder.
2.3.5. Players may also be placed in a higher or lower division at any time. If your ladder administrator deems that having you in your current division is unfair to the other clans in that division, he/she reserves the right to move you up or down at any time. Any player may request this by sending an e-mail or PM to the appropriate ladder administrator.
2.3.6. UGC reserves the right to reset the ladder or move individual players at its discretion. This will not affect player's permanent records.
2.4. Tournament Rules
2.4.1. Periodically UGC will hold Tournaments. The dates and times will be announced well in advance on the TFC 1v1 home page.
2.4.2. Tournament Eligibility 
Player eligibility for the tournaments is you must have joined at least five weeks prior to the start or the tournaments. If there are not enough players that are available for the tournament in a division, then the division will play with fewer than the normal number of seeded players, with the highest ranked player(s) receiving byes for round 1 as appropriate. If there is a tie between 2 players for a tournament spot where their +/- is the same, as well as their winning percentage, and the loser will NOT gain entrance to the tournament, a match will be played prior to the start of the tournament. PF and PA is not a valid ranking system for the tournament.
2.4.3. Tournament maps will be voted on by league administrators and players.
2.4.4. Tournament Schedule
2.4.4.a Week 1 Of the Tournament
In each Division:
1st place and 2nd place players will have a BYE or non-tournament match.
3rd place and 6th place players will play.
4th place and 5th place players will play.
2.4.4.b Week 2 Of the Tournament
In each Division:
The winner of 3rd place versus 6th place will play 2nd place.
The winner of 4th place versus 5th will play 1st place.
2.4.4.c Week 3 Of the Tournament
In each Division:
The two winners of Week 2 will play each other to determine the champion of their division.
2.4.5. All players not in the tournament or players eliminated from the tournament will continue to hold matches and compete for title shots concurrently while the tournament is being held.
3. Server Issues [top]
3.1. Only dedicated servers in the continental United States running on a T1 or better connection can be used for matches unless both players agree ahead and in a logged form.
3.2. Servers must have at MINIMUM of 3 available slots. This is so the server may accomodate both players, and either HLTV or the rare occasion where an admin will spectate.
3.3. Any server on which a round is played must be running the UGC_tfc1.cfg. This can be found on the files page. This is mandatory. No exceptions. Period.
3.4. VAC (Valve Anti Cheat) is required to be enabled for all matches.
3.5. Adminmod, AMX Mod and AMXX Mod and the like are allowed to be run as long as they does 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. Adminmod 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. This includes any anti-spamming plugin. If any player from the opposing player (the visiting player) is kicked for any reason due to admin mod, the home player will forfeit all points earned during the round, unless the visiting player agrees otherwise. Let this be an incentive to either not run admin mod or to disable the plugins.
3.6. Spectators in the server are not allowed unless agreed by both players. Please password the server and admonish those not in the game to refrain from joining in. However, you must reserve one slot for an admin spectator as stated in 3.2 above.
3.7. Server Connection Issues and Crashes
3.7.a. Should a server start to have connection issues (it starts giving both players extreme packet loss, lag, and makes the match generally unplayable), or if the server crashes outright, and the players verbally agree that the server has become unplayable, then the round will be stopped and restarted elsewhere. If 10 minutes have passed since the FIRST connection issues occurred, then whatever score that has been accumulated counts as the round, if it has been LESS then 10 minutes since the connection issues started, then the round will be replayed and the score reset.
3.7.b. If it is found that a player intentionally crashed a server, they will automatically lose the match and further action will be taken, including temporary or permanent suspension. This kind of bad sportsmanship will not be tolerated.
3.8. Player Ping Differences
If the player providing the server has an average player ping advantage of greater than 100, the round must be moved to the other player's server or a neutral server if the nonhosting player requests. If the hosting player refuses to move the round, and the other player provides screenshots/dems evidencing the ping advantage, the round may be awarded to the nonhosting player regardless of who won the round played. Note this does not apply to INDIVIDUAL players that are at a ping disadvantage for an extenuating reason (dial-up connection, international players).
3.9. Using HLTV
3.9.1. UGC does not require the use of HLTV in the 1v1 ladder. However, the hosting player may record HLTV at his/her discretion as outlined below.
3.9.1.a. HLTV Recordings
All players are required, if requested by the opponent, to submit HLTV demos to each other within 24 hours after the last round of the match is played. Personal demos are not required to be submitted to the opponent.
3.9.1.b. HLTV Spectators
HLTV SPECTATORS ARE ALLOWED if agreed on by both players. If one player wants spectators and the other does not, then spectators will not be permitted.
4. Player Rosters [top]
4.1. The 1v1 ladder is "every man for himself" - that is, only one player per roster. This player must be listed on the roster on the UGC web site by 11:59:59pm EST the night before the match is played, regardless of the day agreed on by players.
4.2. Players already accepted to the probation program with a sponsoring player in 5v or 7v may play in the 1v ladder, however personal dems must be given to the opposing player on request.
4.3. Players listed on the TFC banlist may apply to play in the ladder by posting a statement in the UGC 1v forums. Other 1v1 players will then vote whether to allow the banned player to compete, with a majority vote required for approval. Approved banned players are required to submit personal dems to their opponent on request.
5. Match Play [top]
5.1. Prematch
5.1.1. Schedules go up by Thursdays. Please attempt to contact your next opponents right away. We recommend you try their IRC channel or website. Alternatively, if they are registered with our forums, you can contact them through a private e-mail. Contacts over the public forums should be a last result.
5.1.2. The Home player hosts the first round, and the visiting player the second round, unless otherwise agreed.
5.2. Starting A Match
5.2.1. Every player is allowed fifteen (15) minutes after the scheduled match time to have server ready, and HLTV ready if used.
5.2.2. Forced Forfeits
If a player "no shows" or refuses to join the server within 15 minutes of the agreed match time, and the server is properly configured with VAC, league config, and all necessary league plugins:
they can and will be forced to forfeit if the opposing player chooses that option. If there are extenuating circumstances (splayer crashing, some can't join a particular server, etc) then the players may agree on a new match time or are to find an admin. If an admin is unavailable, players are instructed to join #ugc-tfc and discuss the matter in public, whether or not an admin is present. The public record will stand in case of a dispute.
5.2.3. Please avoid telling your opponents that you will not be able to play the match if you are uncertain of this fact. If you tell your opponent that you player will be unable to play the match for whatever reason, then your opponent will receive a forfeit win. THIS AGREEMENT IS BINDING!
5.3. Playing A Match
5.3.1. All matches are to be played traditional 1v1 soldier "mulch" style.
5.3.2. Each round should include a 1-minute prematch, and will end when the first player reaches 20 kills.
5.3.3. Each player will enter a shared yard or open arena between bases/respawns. Once in the arena, each player must stand at opposite sides from each other corresponding to their base/respawn?s entrance. Each player must signal that they are ready to begin fighting by jumping once. Once both players have jumped once to signal they are ready to fight and have landed on the ground they may begin fighting immediately. Once a player has signaled that he/she is ready to fight they are not allowed at any point to return to their base/respawn unless they either die or kill their opponent. After a player has been killed or has killed himself while in deathmatch, each player must report immediately back to their original starting positions in order to signal once again to their opponent and fight.
5.3.4. All weapons allowed except secondary grenades (nails).
5.4. Starting Subsequent Rounds
5.3.1. 10 minute breaks are allowed in between each round of play. This time can be ignored if both players agree to it before-hand. Players are encouraged to remain in communication between rounds in the event there are problems making the transfer between servers.
5.3.2. If a player is not ready for round2 (and any successive rounds) after the agreed on break and by the end of that round's prematch (total of 10 minute break plus 1 minute prematch), that player is entitled to a maximum of TWO additional restarts (though more MAY be granted at the discretion and agreement of the hosting player.) Please be courteous to the visiting player in the event there are problems arising from the transfer of servers.
5.5. Completing the Match and Overtime Rules
5.4.1. Match winner is determined by totaling the round 1 and round 2 scores for each player. The highest total score wins the overall match. By way of illustration:
Round 1: PLAYER [AAA] 20 - PLAYER [BBB] 10
Round 2: PLAYER [AAA] 15 - PLAYER [BBB] 20
Winner: player [AAA] 35 points total
Loser: player [BBB] 30 points total
5.4.3. If the match is tied after two rounds of regular play, the match may be reported as a tie. Alternatively players may agree to a full third round, or sudden death if desired.
5.6. Reporting Matches
5.5.1. WINNING Player Reports Scores
After match play is over, THE WINNING PLAYER is to report the scores. This can and should be done via the UGC website. Match write-ups may be edited at any time by an admin, should he or she feel that something needed to be added, removed, or changed. Inappropriate match comments may be grounds for suspension or expulsion from the league.
5.5.2. Winning players have until 11:59:59pm EST on WEDNESDAYS to report scores after their match. Failure to do so will result in a nullified match for both players. If you have made an error in reporting the scores, please send an e-mail to the appropriate ladder administrator. If there is a dispute over the reporting, logs and demos will be required.
5.7. Forfeits
5.6.1. UGC defines a forfeit as the following:
Any player that fails to field after 15 minutes have elapsed from the agreed starting time in the absence of an agreement otherwise. This applies to each individual round (Does not include break time agreed on by both players). Once a player forfeits any round, that player forfeits the match as a whole.
5.6.2. Penalties for Forfeits
We will not tolerate forfeiting. If a player forfeits their first UGC match after joining or rejoining the league, they may be suspended for one (1) week. A player who has played at least one match since joining or rejoining and forfeits one match will not be penalized. If a player forfeits two consecutive matches, they may be removed from the league IMMEDIATELY and without contact. Note that if a player has a scheduled BYE week inbetween two forfeits, it is STILL two consecutive forfeits. If a player forfeits two non-consecutive matches
(there is at least one week inbetween the forfeits where the player has played a match), then they may be suspended for one (1) week. Should a player forfeit three matches, they may be removed from the league IMMEDIATELY.
5.6.3. Forfeits = Loss. Rankings include forfeit wins and losses.
6. Rankings [top]
6.1. All UGC Players are ranked first by your +/- record, then by your winning percentage, then by your winning streak.
6.2. When a player moves up or down a division, the player's rank info will be reset to 0-0, however the player's overall and previous records, including any titles earned, will be preserved.
6.3. Players may also be placed in a higher or lower division at any time. If your ladder administrator deems that having you in your current division is unfair to the other players in that division, he/she reserves the right to move you up or down at any time. Any players may request this by sending an e-mail or PM to the appropriate ladder administrator.
7. League Maps [top]
7.1. All maps to be played in matches are chosen by the UGC admins, and are displayed on the schedule page each week. Players may however substitute any maps if both players agree unless it is a title match. Map substitions on a title match require approval of the ladder admin even if both players agree.
8. Sportsmanship [top]
8.1. Good sportsmanship is an important part of this league and all players are to be treated with respect. Any foul language is offensive. If you are not sure if it's offensive, don't use it. This goes for before, during and after any match. We expect mutual respect.
8.2. Recording Personal Demos
8.2.1. All players in a UGC match are required by UGC to record personal demos. This can be done by pulling down console ["~" Key by default] and typing "record demoname" without the quotes [ "" ]. To prevent the demo from being corrupted, type "stop" in the console upon completion of the demo. If you drop during a round, begin recording a new demo with a new name IMMEDIATELY after you join the server.
8.2.2. All demos must be saved for 2 weeks. If a player can not provide the personal demos, they will cause the player to forfeit all rounds played with that player. UGC does not require passing out personal demos to anyone but UGC official admins upon request, unless the player is a probation player, or approved banned player.
8.2.3. Cheap Disputes
This rule is not to be used for "Cheap dispute wins". HLTV if available will always be viewed first to determine which players demos must be looked at. However, suspensions may still be given out to individual players should we find out that they are neglecting to record demos every week.
8.3. Teamswitching during a match is disruptive to the match and to the opposing player. Players teamswitching during prematch of the live round or during live match play may be suspended, and points earned that round possibly removed.
8.4. Proof of bad sportsmanship should be brought to an administrator's attention privately. We will look over the accusation and make a decision. Server logs, HLTV demos or personal demos with a brief description of dispute in .TXT format are required to be sent via e-mail to the head admin.
8.5. Punishments
1st offense = 1 week suspension
2nd offense = 2 week suspension
3rd offense = Removal from the league
8.6. Administrators have the last word in all disputes. Arguing with their decision will result in a 2 week suspension.
8.7. PLEASE NOTE: The disciplinary actions outlined above are GUIDELINES. They are NOT written in stone. Actual punishments will be determined on a case by case basis, and are most often chosen after considering the severity of the infraction, the infraction itself, and any previous infractions made by the player(s) in question.
9. Cheating [top]
9.1. 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.
9.2. Substitute players are not permitted to play in UGC's 1v1 ladder.
9.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.)
9.4. Using the server or console commands to give any part of your player an unfair advantage is cheating. This does not include mm2 scripts regarding flag status, class status, health status, incoming calls, or the like. Any console command that aids in centering a players view is illegal.
9.5. All of the above will be considered cause for removal from the league, if proven guilty.
9.6. UGC reserves the right to enforce any other leagues' bans, or deny access to any player/player that we feel would not be able to live up to UGC standards. It has always been this way, but now it's in the rules section.
9.7. Anyone who is proven to have used a cheat/hack in a match, a non-match competitive environment or on a public server (FF, TFC and TF2) after September 1, 2007 will be banned from match play at UGC in all Divisions, mods and ladders.
This includes any unlocked server, as well as pickups, scrimmages, gathers, or competitive environment such as 1v1, 2v2, tryout, or practice, even if the server is passworded. The ONLY time the use of a hack would not be a bannable offense is if it is used to view a dem, used alone locally for "testing", or on a passworded LAN or server AND with the PRIOR notification of ALL other players present. It is suggested that if you choose to risk doing this, you record a dem and you give a mm1 notification within the dem.
9.8. The ban policy for the TFC 1V ladder will be a timed ban "three strikes you're out" policy.
First offense: 1 year ban
Second offense: 1 year ban
Third offense: permanent ban
An offense is defined as active cheating in a match in ANY tfc, FF or TF2 league, competitive environment, or public server as defined above, or aliasing while banned.
Aliasing is defined as altering your name, splayerid and/or IP as a method to avoid the ban punishment and continue league play. Bans are issued to PERSONS not just to splayerids.
9.9. Login-sharing
"Login-Sharing" is defined as giving out the username/e-mail and password associated with your Splayer Account to a third-party to whom the Splayer account does not belong. This is a violation of Splayer's subscriber agreement.
ALL parties caught sharing accounts on or after September 1, 2007 will be removed from UGC and added to our banlist as follows:
1. Login-sharing with a banned player
Login-sharing with a currently banned player is a permanently bannable offense for the PROVIDER regardless of the situation in which the login-sharing occurs, and ALL IDs of the provider will be banned. "I didn't know it was a banned player" is no excuse. Any logins that can be shown to have been used by a banned player prior to November 22, 2005 will be placed on the ban list as compromised, however the previous owner of that login will not be banned personally.
2. Login-sharing with a non-banned player in an FF league with login-sharing rules
Login-sharing with a non-banned player in a league that has policies against login-sharing is illegal if the login sharing was used to allow a non-rostered player to participate in a match. This will result in a 6 month ban for BOTH the PROVIDER of the ID as well as the USER/receiver of the ID. However, ALL parties, both the provider and recipient, caught sharing accounts in this manner in UGC matches after July 11, 2005 will be removed from UGC and added to our banlist for six months.
3. Login-sharing with a non-banned player in a league without login-sharing rules
Login-sharing with a non-banned player in order for the recipient to participate in a match in a league that does not regulate login-sharing will result in a 3 month ban for BOTH the PROVIDER of the ID as well as the USER/receiver of the ID.
The sale, transfer, or gift of splayerids to a friend or family member is not a bannable offense, although it DOES violate Splayer's subscriber agreement. If you still choose to hand your account information to a third party, it is in your best interest to notify the leagues in which you play that you have given away that SplayerID and no longer have access to it.
May these rules be incentive NEVER to share your login with ANYONE, and NEVER to accept or use the login information of another player. If you are unsure of the security of your account, we advise you to change your password.
10. Disputes [top]
10.1. Submitting A Dispute
10.1.1. If you have a dispute to submit, you are to email UGC at tfcdispute@ugcleague.com with details about your dispute. Be sure to include the following information: what player you are from, who you faced in the match you are disputing, in what ladder the match was, what rules were broken, and what evidence you have of this. This must be done within 48 hours after match is played. The 48 hour rule does not include cheating disputes, those have no deadline.
10.1.2. By not submitting a dispute within the 48 hour period immediately after your match, you are acknowledging the fact that you did not find any fault with the other player's style of play in any way, shape, or form, even if they found fault with yours. In other words, should you find out a couple of days later that you are being disputed against, we will NOT accept any counter-disputes from your player. The only exception to this would be if a player is suspected of using a hack (i.e. aimbot, wallhack, anticonc, etc) during the match.
10.1.3. We encourage all players who feel that their opponents did not play a clean game to dispute the match, regardless of what the outcome was. This will help us to locate and possibly remove all players and/or players who have no regard for the rules.
10.1.4. Before disputing a match and handing the logs/demos over to an administrator, make sure there is sufficient evidence found within.
10.1.5. All disputes must include timestamps of the listed violations. You don't need to detail every single violation but timestamps are now required for disputes to be accepted. Please take the time to review the demos prior to submitting a dispute. Please give us as much detail as possible so we can better process the dispute.
10.2. Resolving A Dispute
10.2.1. Administrators will try to handle all disputes as quickly as possible, however some disputes may require more time depending on the complexity.
10.2.2. Please help us in resolving the dispute by giving us all proof available, including demos, screenshots, and server logs [in raw form, not parsed]. Please do not email demos unless instructed; please upload and include links to evidence in your dispute.
10.2.3. Administrators are to be left alone while the dispute is being investigated. Things like, "when will the dispute be done" only prolongs matters for both players.
10.3. Admins Involved In A Dispute
10.3.1. Any administrator who happens to play for a player that is involved in a dispute, is not allowed to participate in that dispute due to conflict of interests.
10.4. Cheap Wins
10.4.1. UGC will not tolerated players using the rules for "Cheap Wins". UGC will determine if the rule broken effected the match played.
10.4.2. UGC will not tolerate frivolous disputes. Please review your disputes before submitting them. If you need a time extension, talk to your ladder admin, they have the power to grant you an extension. If players continue to file frivolous disputes, disciplinary action will be taken.
10.5. Dispute appeals
10.5.1. players involved in a dispute may submit an appeal ONCE and ONLY ONCE and must submit an appeal within 48 hours of receipt of dispute results. The appeal must be submitted to the dispute email address with the details of the appeal, and may include new evidence. If the dispute player accepts the request, the dispute will be reopened but only matters specifically written in the appeal will be re-addressed. The second ruling is the ruling that will be final and no further appeals will be accepted.
11. Joining UGC [top]
11.1. All Players joining the Ladder must provide current splayerid and will be reviewed for any past cheating allegations, and contact info given.
11.2. All players must have an active IRC channel in which he/she can be contacted [preferably on irc.gamesurge.net] in order to join UGC.
11.3. Required contacts must be filled out with the use of the Joining forms and info within your access to the UGC web site. The players will be e-mailed or notified on IRC soon after being accepted into league.
12. Rule Updates [top]
12.1. The rules set forth on this page may be altered, or updated at anytime. It is the sole responsibility of every player/individual to keep up to date with these rules.
12.2. In addition, admins may enforce map specific or general rules at any time during the season. These rules will be posted by the administrators on the main news page of the ladder. As long as these rules are either on the news page or the rules page, they WILL be enforced. It is YOUR responsibility to review the news page. If the post is deleted and the rule is not transferred to the official rules page, it will no longer be enforced.
12.3. We at UGC reserve the right to intepret all of the rules set forth on this page as we see fit in each situation, independent of each other. They should be clear enough, but in the event that there is some confusion about what a rule means or how it applies in a given situation, please ask an admin to clarify it BEFORE you break it. We will no longer accept any excuses that a rule was too unclear.
13. Agreement Policy [top]
13.1. Agreement Policy: If two players playing each other during the season wish to change a rule for their match or to allow a unrostered player to play and both players agree to the change, BOTH players must get in contact with their division admin PRIOR to the match and let them know what changes are being made for the match and that they agree to it. Banned players are excluded from this policy. Once both players have contacted one of their division admins and the change has been approved, it will be permitted in match play. Most changes to matches will be accepted as long as they keep the playing field even.
|
|
|
|
|
|
