2.1.1. All UGC Fortress Forever 5v matches are to be played on Wednesday nights at 9:00 PM EST.


2.1.2. Moving a Match

If two clans that are scheduled against each other wish to move the match to a different time/day, it is acceptable as long as both clans agree (see agreement policy). If one clan wishes to and one doesn't, or they cannot agree on another date/time, then the match will be played on the scheduled division time. However, matches must be played at latest 24 hours after the scheduled time of the division as to not hold up schedules for the following week.


2.1.2.a. If there is a case where a match must be moved, both clans must contact the head admin of their division/ladder and let them know what day/time match will be played. This must be done at least 24 hours ahead of time.

2.1.2.b. All matches can be played anytime before required match date/time, as long as both clans agree to play before match time. Please keep a file of agreement. We recommend using the UGC leaders' forums to log the agreement. Alternatively teams may use IRC, preferably #ugc-ff or #ugc-support.

2.1.2.c. All matches that are rescheduled must be played within 24 hours past the original match date/time. Due to the need for prompt reporting and ranking purposes, teams that cannot fulfill this requirement will suffer a forfeit. In the event that both teams refuse to play, both teams will suffer a forfeit.

2.2.1. The 5v Fortress Forever Ladder may be subdivided with divisions based on team skill levels.

2.4. Playoff & Championship Week

2.4.1. The following will determine the playoff schedule for each division.

2.4.2. Clan eligibility for the playoffs is you must have joined during the first five weeks of the season start (this means 8 weeks into the season, including preseason.) In other words, all teams who have signed up for up to and including the week 8-match day are eligible for playoffs. If there are not enough clans that are available for the playoffs in a division, then the division will play with fewer than the normal number of seeded teams, with the highest ranked team(s) receiving byes for round 1 as appropriate. If there is a tie between 2 clans for a playoff spot where their +/- is the same, as well as their winning percentage, and the loser will NOT gain entrance to the playoffs, a match will be played during the off week to determine who makes it to the playoffs. PF and PA is not a valid ranking system for the playoffs, if two clans are still tied after that, they will have a seat-determining match in the week break before playoffs.

2.4.3. Week 1 Of Playoffs

In each Division:

1st place and 2nd place teams will have a BYE.
3rd place and 6th place teams will play.
4th place and 5th place teams will play.

2.4.4. Week 2 Of Playoffs

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.5. Week 3 Of Playoffs

In each Division:

The two winners of Week 2 of Playoffs will play each other to determine the champion of their division.
All playoff & championship match rounds will be played the same as regular season.
[same rules and issues apply]

2.4.6. Playoff maps will be voted on by league administrators and clans.

2.5. Tournament Rules

2.5.1. Periodically UGC will hold Tournaments. The dates and times will be announced well in advance on the FF 5v5 home page.


2.5.2. Tournament Eligibility

Clan eligibility for the tournaments is your team must have joined at least five weeks prior to the start or the tournaments. If there are not enough clans that are available for the tournament in a division, then the division will play with fewer than the normal number of seeded teams, with the highest ranked team(s) receiving byes for round 1 as appropriate. If there is a tie between 2 clans 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.5.3. Tournament maps will be voted on by league administrators and clans.


2.5.4. Tournament Schedule

2.5.4.a Week 1 Of the Tournament
In each Division:

1st place and 2nd place teams will have a BYE or non-tournament match.
3rd place and 6th place teams will play.
4th place and 5th place teams will play.

2.5.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.5.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.5.5. All teams not in the tournament or teams eliminated from the tournament will continue to hold matches and compete for title shots concurrently while the tournament is being held.

3.7. Server Connection Issues and Crashes

3.7.a. Should a server start to have connection issues (it starts giving both teams extreme packet loss, lag, and makes the match generally unplayable), or if the server crashes outright, and the teams captains 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 team 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. Team Ping Differences

If the team providing the server has an average TEAM ping advantage of greater than 100, the round must be moved to the other team's server or a neutral server if the nonhosting team requests. If the hosting team refuses to move the round, and the other team provides screenshots/dems evidencing the ping advantage, the round may be awarded to the nonhosting team regardless of who won the round played. Note this does not apply to INDIVIDUAL players that are at a ping disadvantage.

3.9.1. UGC requires the use of Source TV and all matches must be recorded.


3.9.1.a. Source TV Crashes

Source TV must be recording throughout the entire round. That means ALL THIRTY MINUTES. If Source TV drops during prematch and is restarted before prematch ends, then the round need not be restarted. However, if Source TV is not in the server anytime between prematch ending and the round ending, and it is pointed out in mm1 that Source TV has dropped, the round must be restarted with Source TV running and the round will continue with the CURRENT time left and scores (give or take a minute).


3.9.1.b. Source TV Spectators

Source TV SPECTATORS ARE ALLOWED if agreed on by both clans. If one clans wants spectators and the other does not, then spectators will not be permitted. If a Source TV is passworded, and players from one team are in it, an equal number of players from the opposing team must be allowed to watch from the Source TV proxy. Remote reporting will not be permitted. NOTE: YOUR CHAT IS RECORDED ON Source TV-DO NOT INSULT THE OTHER TEAM IF YOU DO NOT WANT THEM SEEING IT LATER. If Source TV proxy is unable to handle spectators during match, then this should be respected and no one is to join proxy. But in this case, leaders are allowed to ask for Source TV proxy IP's for viewing server info to insure configs are set right.

3.9.2. All teams are required, if requested by the opponent, to submit Source TV 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.3. If an administrator has requested Source TV demos and it is not supplied, the team responsible for recording the demo that round may face disciplinary action including, but not limited to, loss of points for that round and/or a 1 week team suspension unless proof that the other team agreed to run the proxy or that no proxy would be run, e.g. an IRC log, can be provided.

Exception Teams will be allowed 2 roster changes/additions between weeks 15 and 16 after the rosters have been locked. The additions must be made through an admin and must be made PRIOR TO the last 24 hours before the week 16 matches. No other additions are allowed after that time for winning teams that advance to week 17/18.

4.3. Changing Teams

No player will be removed from an active roster by an admin without the player's consent. The preferred method to change rosters is through team leaders first. If your former leader will not remove you, contact your division admin; however admins will still notify your former leader that you have been removed. Excessive roster rotation will be reviewed and may be grounds for a suspension.

5.1.1. Schedules go up within 48 hours of match play. 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. All Leaders should be in contact with their opponent 30 minutes before the agreed-on match time to confirm server information. This may be affected through IRC, ICQ, MSN, Xfire, or Email.

5.1.3. When the records are tied, the Home team hosts the first and third rounds, and every odd numbered round thereafter. The status of Home or Visitor can be determined by referring to the posted schedule. Otherwise, the higher ranked team hosts the 1st and 3rd rounds of a match, and every odd numbered round thereafter, while the lower ranked team hosts the 2nd round, and every even numbered round thereafter.

5.1.4. On Capture the flag maps the visiting team chooses which team color to play first. Team colors are to be alternated each subsequent round. On command point maps the visiting team chooses whether to attack or defend first.

5.1.5. All Teams should have at least one leader/team captain join channel #ugc-ff (gamesurge.east) at least forty (40) min before match time (This rule is flexible). This makes contact between teams much easier. Any such team leader/team captain must be wearing team tags when entering IRC channel. This rule is flexible as the intent and spirit of the rule is to insure that the teams can exchange server ips and passwords as well as provide the required Source TV information.

5.1.6. We urge all of our teams not to wait until match day. Contact the opposing team no later than 24 hours before match time.

5.2.1. Every team is allowed fifteen (15) minutes after the scheduled match time to have server ready, Source TV ready, and a full squad into the server for round 1. Please avoid excessive squatters in the prematch. You should be organized enough to determine what your roster is in advance. There is no penalty for this, but as the prematch counter dwindles, it becomes increasingly frustrating for the opposite team.

5.2.2. A team that assembles the league required minimum but states that they are waiting on remaining players, and likewise a team with a FULL (as opposed to a league minimum) roster is STILL entitled to additional resets provided that the current prematch ends prior to (15) minutes mark after the scheduled match time. Though more MAY be granted at the discretion and agreement of the hosting team.

5.2.3. A team must have 6 members ready to play by fifteen (15) minutes after the scheduled match time. Otherwise, they will receive a forfeit loss. If a team does not have the required minimum by the time the first prematch counter expires, they are entitled to an additional two (2) resets, or a total of fifteen (15) minutes as described above.


5.2.4. Forced Forfeits

If a clan can not produce enough players or refuses to join the server within 15 minutes of the official 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 team chooses that option. If there are extenuating circumstances (steam crashing, some can't join a particular server, etc) then team leaders are to find an admin. If an admin is unavailable, team leaders are instructed to join #ugc-ff and discuss the matter in public, whether or not an admin is present. The public record will stand in case of a dispute. If there is no public record, the clan that could not produce enough players or refused to start the match within 15 minute of the official match time, will forfeit the match upon the request of the opposing clan.

5.2.5. Please avoid telling your opponents that your team will not be able to play the match if you are uncertain of this fact. If your team leader (listed as a contact on the contacts page) tells your opponent (anyone on their roster) that your team will be unable to play the match for whatever reason, then your opponents will receive a forfeit win. THIS AGREEMENT IS BINDING!


Example

For example, if it is Saturday afternoon and your team leader PM's a member of the other team and states that your team will not be able to play the following night, then they can immediately report a forfeit win. You may NOT change your mind the next night, even if you have a full roster ready to play. It is not fair to the other team to expect to not play and find out that the match is going to be played. Please note that the agreement must be logged and proof must be given to an admin upon request.

5.3.1. 10 minute breaks are allowed in between each round of play. This time can be ignored if both teams agree to it before-hand. Team leaders are encouraged to remain in communication between rounds in the event there are problems making the transfer of teams between servers.

5.3.2. If a team 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 3 minute prematch), that team is entitled to a maximum of TWO additional restarts (though more MAY be granted at the discretion and agreement of the hosting team.) Please be courteous to the visiting team in the event there are problems arising from the transfer of servers.

5.4.1. Match winner is determined by totaling the round 1 and round 2 scores for each team. The highest total score wins the overall match. By way of illustration: Round 1: TEAM [AAA] 50 - TEAM [BBB] 100
Round 2: TEAM [AAA] 150 - TEAM [BBB] 50
Winner: TEAM [AAA] 200 points total
Loser: TEAM [BBB] 150 points total


5.4.2. Flag captures after the score screen appears

If a flag is captured after the score screen appears at the end of the match, it does not count towards the round score for that team. If it was too close to call in the game, logs will be used to ascertain the correct scores. The scores that are shown in the logs will be used. Lag is not a handicap, logs will determine the order of what occured first. The lines to look for would be the line that states that the match has ended and the line that mentions "Dropoff." If "Dropoff" occurred before the round ended, the cap counts. Otherwise, it does not.

5.4.3. If the match is tied after two rounds of regular play, the match will continue as an overtime round of the default teamsize (5v5.)


5.4.3.a. Overtime on Capture the Flag Maps

This is sudden death overtime where the first flag capture wins the match and ends the round. For maps that have both flag capture points and points for other map objectives, only a flag capture will award a sudden death winner. If there is no flag capture in the 30 minute period, then any other points awarded by the map will be used to determine the winner.


5.4.3.b. Overtime on Command Point Maps

Another two rounds must be played. Each round ends when command point 1 is captured. The team with the higher defense score is the winning team.


5.4.4. Ties that Remain after Overtime

If after the first overtime round (or rounds in the case of command point) is played and a winner has not been determined overtime rounds may be rescheduled to be played the following night picking up where the match left off. This agreement must be posted in #ugc-ff as a matter of public record. Clans can also agree to nullify the match after the first overtime is complete and there is still no winner.

5.5.1. WINNING Team Reports Scores

After match play is over, THE WINNING TEAM is to report the scores. This can and should be done via the UGC website. We have gone to great lengths to automate this process and allow for almost instantaneous reporting. Please allow for 30 minutes before inquiring as to the status of your report. The team captain will be able to log in and enter not only the scores, but a match summary for others to read. THIS IS NOT THE PLACE TO FILE A COMPLAINT. Address all complaints via e-mail or private messaging (forum, IRC, etc) to your division admin, which can be found by viewing the Staff page. Please remember that these comments will be available for all to view, so watch what you write. Match summaries 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 clans have until 11:59:59pm EST of the following day to report scores after their match. Failure to do so will result in a nullified match for both clans. 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.6.1. UGC defines a forfeit as the following:
Any clan that fails to field at least the minimum required members (as noted above) after 15 minutes have elapsed from the scheduled starting time in the absence of an agreement otherwise. This applies to each individual round (Does not include break time agreed on by both clans). Once a clan forfeits any round, that team forfeits the match as a whole.


5.6.2. Penalties for Forfeits

We will not tolerate forfeiting. If a clan forfeits their first UGC match after joining or rejoining the league, they may be suspended for one (1) week. A clan who has played at least one match since joining or rejoining and forfeits one match will not be penalized. If a clan forfeits two consecutive matches, they may be removed from the league IMMEDIATELY and without contact. Note that if a clan has a scheduled BYE week inbetween two forfeits, it is STILL two consecutive forfeits. If a clan forfeits two non-consecutive matches (there is at least one week inbetween the forfeits where the clan has played a match), then they may be suspended for one (1) week. Should a clan forfeit three matches, they may be removed from the league IMMEDIATELY.

5.6.3. Forfeits = Loss. Rankings include forfeit wins and losses.

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 team to forfeit all rounds played with that player. UGC does not require passing out personal demos to anyone but UGC official admins upon request.


8.2.3. Cheap Disputes

This rule is not to be used for "Cheap dispute wins". Source TV 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.

GAMEPLAY AND STRATEGY

8.3. Class Restrictions:
Class restriction is (1) for HWGUY.
Class restriction is (2) for ENGINEER.

8.4. Turtling: At no time should there be more than 3 Defensive players.

8.4.a. There is NO limit to the amount of offensive units a team may run at any given time. You may run three (3) offense, four (4) offense, even five (5) offense. As long as there are no more than three (3) players defending your base. If a player on the offense shoots and kills the enemy flag carrier, they will be considered a defender. If a player on the offense attempts to secure areas of the enemy base (i.e. pipetrapping the entrance, guarding the door, etc), then they will STILL be considered a member of the offensive squad, as long as the setup doesn't interfere with the enemy offense's normal direct route(s) out of the base and to their cap point.

8.4.b. If you have the max number of D allowed and it consists of an engineer, at any time during the match he may leave his sg up to help guard the flag and make O runs to the enemy base. This is not a problem as if there would be 2 D left behind with a SG and 3 O running to the enemy base.

8.4.c. If you have a 3 D set up and using 2 O running to the enemy base and one of the O decides to use engineer as a tactic, this is fine as long as he does not set up a sg to help guard the flag, as he would be considered a part of D and the D would equal up to 4 D, 1 D over the turtling limit.

8.4.d. If you are running offense, and ANYTHING you have done (i.e. build a SG, build a dispenser, set a pipetrap, drop caltrops, drop napalm, drop mirvs, drop spy pills, etc.) could potentially prevent the enemy offense from reaching or capping your flag, you will be considered a defender. However, this does not include setting up anything in the enemy base as described above in rule 8.4.a.

8.6. NO potshots: [Offense shooting offense as they move past each other. This includes successive potshots killing a single player. It does not include occasional knee jerk reactions to the enemy on a few occasions throughout a match. Do not return fire. If you believe potshots are excessive, then take it up with an administrator. Once potshots are returned, and it appears to the reviewing admin that potshooting has been adopted by both teams, neither team may complain.] This includes successive potshots killing a single player. This also includes anything that would damage an offensive runner of the other team including med kits, crowbars, spy pills, caltrops, demo class pipes, rockets, and grenades of any type. It does not include occasional knee jerk.

8.7. NO Taunting. Def. of taunting: When a Defensive configuration is set up at an entrance of a base[or line of NO yard D zone] and the enemy Offense primes grenades, throws grenades or shoots at D configuration. This allows D to pursue its enemy who is trying to harm him/her. If O shoots at the D, don't expect them not to start yard D.

8.8. Yard Defense: [GENERAL RULE- You cannot set up a defensive configuration in a yard. A defensive configuration is defined as any entity evidenced to be playing defense for its team. This includes, but is not limited to, a single player, multiple players, dispenser, pipetrap, sentry gun, and pyro class or spy class grenades. A yard or the yard is defined as that area immediately outside your last exterior battlement from which you can typically see the enemy's battlements. Enclosed yards are your yard. Examples include, but are not limited to, Well the bunker between the forts and the immediate water exit on either side is a yard or the yard and may not be defended unless otherwise provided below. Once the water exit extends laterally along side the respective and mirrored yards, defense is allowed, 2fort the bridge area between the battlements is a yard or the yard and may not be defended unless otherwise provided below. On maps where there are distinct yards for each team connected by a single common area, defensive configurations are allowed at ALL TIMES in your yard. The common yard is considered the yard and no defensive configurations are allowed.]

8.9. EXCEPTION:
• Yard D is permitted when the flag has been moved into the yard.
• If the flag has been moved into a position visible from the yard you may defend the flag as if it were in the yard. Rule applies to exits with doors as if they were open. The flag is considered visible if any part of the flag can be seen.
• Dettable entities located in the yard may be defended until entity has been destroyed.

Any defensive configuration in the yard may extend to the threshold of their battlements. In other words, just before their battlements begin. Your defensive configuration, including but not limited to, player fired projectiles, sentry fired projectiles, emps, pipes, nail grenades, spy class or pyro class grenades or the like, may not strike enemy flesh beyond the threshold of their battlements, except for splash damage. If offensive players return to retrieve the flag, you may continue to defend the yard until the flag resets to the original cap position, is taken out of the yard by the opposing team or reenters your teams base (see exception listed above concerning the if flag is visible from yard rule). Once the flag resets, or is moved inside your battlements, you must abandon all yard defensive configurations, e.g. detonate your pipes, detonate or disassemble any standing dispensers, and dismantle any sentry guns) and return to inside your battlements. Look outs are okay, but they may not fire until fired upon, as per the taunting rule. The opposing offensive may fire on any defensive configuration, look out or otherwise, in any yard. Note that it does not matter whether or not the flag is being carried-if it is located outside the defending team's battlements (and in accordance with the terms above) it is fair game for the defense.

8.10. Defense from the battlements (aimed at the yard) is not allowed if the flag has not been moved outside those battlements or the flag is not visible from the yard. Obviously this rule cannot be applied uniformly due to the fact that maps are so varied in their layout. Some common maps and their respective yards that may not be defended except as set forth above include:

8.11. 2fort- The area between the battlements, including the bridge.

8.12. Crossover2- The bridge area(s) between the two yard exits of the respective teams. Note that this does not include the side tunnels or the water tunnels. Those can be defended to their exits, or entrances into the common area but defensive configurations may not intrude into the bridge area (nor can their intended effects) nor into the common body of water below. Once the enemy offense walks past the bridge and into the tunnel (side tunnel or main T), they are no longer in neutral territory and may be fired upon. When your flag is moved to this area, the entire bridge may be defended. The flag may be defended until the threshold of the enemy base, as described above. This means that once the enemy walks into their “yard”, falls into their pit, or passes through the grate into the pit, they are free from harm. You are allowed to chase them through the water.

8.13. Well- The bunker between the 2 forts, as well as their immediate water paths. Defensive configurations can be set up inside once the flag has entered that area, and may extend until the threshold of the enemy base. That means the flag is defendable until the enemy's front door and the water grate.

8.14 Thus if your yard is separated from their yard by a neutral area, that neutral area becomes common yard when the enemy offense has moved the flag to that point. The respective "yards" on either side of that neutral area or common yard are fair game for defense and defense may set up a configuration at any time.

8.15 Note that maps like dustbowl or cornfield are not subject to the yard defense rule, nor are any offense v. defense maps, or territory capture based maps, such as canalzone2. Reverse CTF maps such as torch2, however, are subject to the yard defense rule. As the flag is constantly being brought through the yard, theoretically yard defense is always allowed. However, on reverse CTF maps, yard defense is NEVER allowed. The defense must wait until the enemy offense enters their base before opening fire. Of course, taunting rules still apply. In O vs D maps or CP maps, the following rules will NOT be enforced: O vs O, chasing, and yard defense.

8.16 Any team found to be guilty of the above items will be reviewed for removal from the league and will have to wait a minimum of 30 days before they can apply to join UGC again. Careful consideration will be given before a team can be reinstated. All win/loss activity will be cleared. UGC reserves the right to determine what is and what is not offensive, excessive, or unsportsmanshiplike.

8.17. 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, Source TV demos or HL demos from every player with brief description of dispute in .TXT format are required to be sent via e-mail to the head admin.

8.18. Punishments

1st offense = 1 week suspension
2nd offense = 2 week suspension
3rd offense = Removal from the league

9.2.1. Multiclanners

The definition of a Multi-Team player: Any player who plays on 2 different teams within the same ladder. For example, if player #1 is on team A and B in the ladder, this constitutes an infraction. However, if the 2 teams are on separate ladders within UGC then that is not a violation. Also, If you agree to allow a player, you have done so for the entire match.

The definition of a Multi-Clan player: Any player currently participating in match play with a FF 5v clan other than their current, single UGC-FF 5v Clan, will be considered to be multi-clanning if the other league also shares multi-clanning rules.


9.2.2. Ringers

The definition of a ringer is as follows: Any player who is not on the Official UGC roster or a player who is not a part of the clan/guild.

Use of a player during a match that does not have a rostered steamid without explicit agreement by the other team in a logged form on the use of THAT player constitutes violation of the ringer rule. Once both teams agree on the use of a ringer, this agreement is for the entire match. Violation will result in forfeiture of points by the offending team in the round where the ringer was used. The violating team will serve a one-week suspension for the first offense, a two-week suspension for the second offense, and will be considered for removal from the league for further violations. The violating player may also be suspended from the league as well. Let this be incentive to all teams to ask an admin to add an unrostered player and to run Ringer Free and to ask that the hosting team is running Ringer Free before match play begins.

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 steamids to a friend or family member is not a bannable offense, although it DOES violate Steam'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 STEAMID 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.1.1. If you have a dispute to submit, you are to email UGC at ffdispute@ugcleague.com with details about your dispute. Be sure to include the following information: what clan 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 team'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 clan. 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 clans 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 clans 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.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 teams.

10.3.1. Any administrator 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 interests.

10.4.1. UGC will not tolerated teams 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 teams continue to file frivolous disputes, disciplinary action will be taken.

10.5.1. Teams 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 team 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.