UT CTF iCombo
Rules


Untitled Document

1. General

1. Players who violate the following rules may be given a card. In serious cases the supervisors may consult with the ClanBase Crew and a decision to impose a temporary or permanent ban from all ClanBase competitions may be taken. A player can be given 3 types of card:

Yellow card : This card is given out for small rule violations. When a yellow card is given in some cases a match result could be changed in favor of the opposing player. Other then that this card mostly is a warning. A second yellow card is to be considered as one red card.

Red card : The match in which they received this card will be changed into a forfeit loss. In some cases this card is handed out together with one or more player bans. A second red card falls in the category 'Two red cards' below
.
Two red cards: A player that has been given two red cards will be kicked from the cup. In some cases a second red card is handed out together with player and/or an entire player ban(s) for 1 or more seasons.

Only 1 card can be given for each match. In case of several violations only the most severe card will be handed out. However, all extra punishments for each of the rule that was violated are still applied. When a player is given a red card all previous given yellow cards are removed.

2. Abusive behavior towards a Supervisor, Referee or opponent, at any time during the cup season, can be punished by the supervisor as they see fit. This could mean a yellow card, red card or just a plain kick from the cup.

 

5. Clans and Players

  1. Clans who quit the cup or who are removed from the cup for 2 noshows/forfeits are likely to be excluded from the next cup season.
  2. Players always have to be easily identifiable to cup admins, opponents and spectators. Therefore, players must use easily identifiable nicks which are the same as (or very closely resemble) those registered on their both on IRC and in-game. Sanctions: Yellow Card.
  3. A clan can only use players during a match who are shown on their and have not played in the same cup for another clan. Using a player who is on your APL, but is not allowed to play (f.e they played for another clan in the same week) will result in a Red Card and match forfeit.
  4. All other players can only play after they're added to the Allowed Player List having fulfilled the criteria in the table below.
  5. A player must be on the Allowed Playerlist (APL) before being allowed to play a match. If a player plays who isn't on the APL the clan will receive a Red card and a forfeit loss. When a player would have been allowed to be added to the APL (thus would have no problem going through the new member procedure) the clan will only get a Yellow card and the match result will not be changed.
  6. Any player who has legitimately been on the clan's Allowed Player List during the cup (and then subsequently removed) can be re-added immediately provided they haven't played for any other clans since the removal. This player will not count as an addition to the APL.
  7. If a player is on the of more than 1 clan in the cup, they are only eligible to play for 1 clan of their choice. To play for another clan during the cup they must meet the following criteria.
    • Their new clan are not in a lower division than the previous clan.
    • The clan have not already added 1 new player during the Playoff Stage.
    • The player must spend 1 matchweek (from Monday to Sunday) without playing for any clan in this cup. For Example if the player played on the Thursday of matchweek 1, they will not be eligible to play for their new clan until Monday of matchweek 3.
    • A matchweek is a week in which matches are scheduled to be played according to the official match roster, this includes the Wildcard week directly after the Group Stage. Any extra weeks off before playoffs/semi-finals etc are not considered to be a matchweek.

  8. I want to add a new player to my APL!
    1. Has the player already played for another clan in this cup? Yes Higher Division: not allowed
    Same or Lower Division: NMP, go to step 4.
    No Go to step 2
    2. Did the player play in the corresponding cup in the Spring 2010 Season? Yes Player can only play 1 division lower than last season, go to step 3.
    No Go to step 3
    3. Has the player already played for your clan in the cup? Yes Add the player, they can play right away.
    No Go to step 4
    4. Do you want to add during the Group Stage? - Not possible in Summer Cups
    No Go to step 5
    5. Do you want to add during the Playoff Stage? Yes NMP, max. 1 player per season
    (if Group Stage total is <3)
    No I think you did something wrong!
    What is the New Member Procedure (NMP)?
    1. Add the player to your clan
    2. The player must spend or have spent 1 entire matchweek (Mo-Su) before or during the group phase without playing for any clan in the cup.
    3. Fill out the
    4. Happy gaming!
  9. A player who played a match for a clan whilst not being on the will receive the following punishment for player and clan:-
    • If the player would have been allowed to play, but was not on the then the clan and player receive a Yellow Card.
    • If the player would NOT have been allowed even if he was on the then the clan and player receive a Red Card (and forfeit the match).
  10. Any attempt by a clan to deceive the Supervisors by letting a player fakenick, or providing deliberately false information (including faking match scores) will result in the clan being removed from the cup. Additionally any players involved in the match may be banned if it can be proven that they were aware of an attempt to break the rules. If this attempted deceit occurred in the last week of group matches or later then the player(s) will also be banned from the next cup season. In serious cases (e.g. lying even when warned) the Cup Supervisors may consult with the Cup Chiefs and a decision to impose a temporary or permanent ban from all ClanBase competitions may be taken.
 


2. Tournament Layout

1. You will play 1 game a week against another clan in your group and the amount of teams going through will depend on how many clans we have per group, division. 

3. Supervisors

1. The cup is supervised by LiQuidfire and WinegumS who are responsible for enforcing the rules, scheduling matches that aren't scheduled on time by the players, and recruiting and coaching Referees and Writers.
For any problems, contact the Cup Supervisors on the cup's IRC channel or through the e-mail address linked below the menu on the Front Page of this cup.

2. If several Referees are signed up the Cup Supervisor(s) decides who will referee the match but if this happens then Christmas must be in July!

4. Referees

1. A Referee is someone who helps our Hosted Cup during the season. Referees are able to enter matchreports and matchresults for cup matches, outside the cup they are regular ClanBase users. Referees who abuse their position may be removed from the Referee lists.

2. Referees are appointed by the Cup Supervisor. If you want to become a Referee, use the Admin Signup link in the cup menu and sign up there. We would like to get 1 admin from every clan, all you need to do is enter your match result and upload some screens.

3. A Referee makes sure the match is played according to the rules, records demos, takes screenshots, enters match results and makes match reports (with screenshots) on ClanBase.

4. If there is no Referee available to admin your match, please follow these steps:

Go through the server testing procedure as explained in these rules. In case of a conflict or disagreement, consult a supervisor or a cup admin in the cup channel.

Keep logs of everything that is said on IRC. Sanction: Yellow Card.

Send the match result and the screenshots to the supervisor by email immediately after the match, so we can make a report for you!

5. Players

1. Clans who quit the cup or who are removed from the cup for 2 noshows/forfeits are likely to be excluded from the next cup season.

2. Any attempt by a player to deceive the Supervisors by letting a player fakenick, or providing deliberately false information (including faking match scores) will result in the player being removed from the cup. So remember use your Clanbase nicks as normal!

6. Server Settings

1. Each clan is allowed to propose their own server as long as it obliges to the server settings which are stated under the Rules section. Please note that is the clans responsibility to find a server for themselves, the admins/referees will not do this for you! Though if you do need a server join #ut.comboinsta and we will try and sort one out.

2. It is not allowed to change any server settings after the match has started without both players agreeing to it. Failure in following this rule will result in a default loss of the match.

3. Servers must have UTPure installed or ACE. Servers running more current versions will be favoured over servers running outdated versions.

4. ConfiguredInternetSpeed / Netspeed: min. 2500, max 15000 at all times during the match. Furthermore, any change of netspeed during any map is forbidden. Violating any part of this rule will result in a forfeit loss of the map the violation occured in.

5. Servers must have UTDC installed. This anticheat should be set so it allows all operating systems to connect and play. Servers running more current versions will be favoured over servers running outdated versions.

6. Players who have problems caused by UTDC when connecting to the match server can be allowed to play by the match referee or server admin through use of the following command: mutate utdc allowone

Any player allowed to play through use of the above command is required to upload all of his/her demos to the ClanBase FTP within 72 hours of the official match time.

Failure to supply all these demos, supplying broken demos or supplying demos missing more than 20% of a map will result in a forfeit loss of the entire match.

These demos will not count towards the demo request limit, and the demos should be uploaded without request from the opposing player or the supervisor.

Players are not required to upload demos if the server is not configured to the ClanBase settings, unless specifically requested by the supervisors.

All uses of this command should be communicated to the supervisors so that they are made aware of any possible bugs that may need attention.

7. NetServerMaxTickrate: 30 - 35. Another value can be used only if BOTH clans agree. This means the servers tickrate has to be set so the packets in value on F6 (stat net) displays a stable value of 30/31.

9. All matches are to be played with the following settings:

Timelimit: 15

Friendly Fire: 0 %

Max Team Score: 0

Force Respawn: On

Tournament: On

Mutators: ComboGibND4.which can be download here - http://www.pookeruk.com/PooKer/UT/ComboGibND4.rar

10. Client Settings

1. Bonuspack models, custom models and skins are not allowed, these include models that have been 'tampered' with.

2. Excessive use of voice taunts are not allowed.

3. Excessive use of “say” binds is not allowed (eg after a flag capture).

4. Taunt/Fire and/or Taunt/Movement binds are not allowed.

5. Behindview in any use or form is forbidden in all cups except for the Bunny Track Cup where it doesn't offer an unfair advantage.

6. You must be using patch 436 or later.

7. ConfiguredInternetSpeed / Netspeed should be kept to min 2500 max 15000 during the whole match. Changing the netspeed while the map is being played is not allowed and will result in a forfeit loss of the map the violation occurred in.

11. Match Rules - general

1. The maplist for this cup is:
TBD

2. If no cup admin was present for your match, screenshots of all maps played must be sent to the supervisor(s) immediately.

3. A player can only pick each map ONE time in the groupstage. If a player picks the same map twice they will automatically receive a Yellow Card and forfeit that particular map.

4. Each player must record a 1st-person demo (of each map he/she plays) and keep this demo for 14 days after the match (Please pay special attention to restarting demorec after disconnecting from the server for any reason).

Players are required to upload up to 2 demos per group match and up to 2 demos per playoff match whenever requested by the opponent.

To request demos, a player must email both Supervisors with their request within 24h of the scheduled match start time. The Supervisors will forward the request to the opponent player. Requests that are not made via the Supervisors are never valid. After a request the player has 72hrs to upload their demo unless they have a reason overwise.

Supervisors may decide to request specific demos themselves. This can be done even if no demos or different demos have been requested by the opponent player.
There are no valid reasons not to record demos. If you can't demorec for any reason - do not play.

Failure to supply a requested demo will result in a default loss.

Failure to upload a complete demo will result in a default loss. Demos missing (broken or not recorded) more than 20% of the time played do not count as uploaded. Demos count as broken when they can't be played on systems following the client settings described earlier.

Repeated failure to supply a requested demo will result in a player cup ban.

The Supervisors and AntiCheat-team can demand someone to upload a demo of every map he/she plays in this cup. Failure to upload the demo within 3 days results in an immediate cup ban. Repeated failure results in a temporary ClanBase ban.

5. If you are using a different connection than normal (tunnel, friends house, etc) connection to play you must inform the admin and/or opponent about this before server testing begins.

6. Switching teams to force the game to pause or for any other reason once a map has started is strictly forbidden and will result in a red card and forfeit loss of the map in question.

7. Before the start of the map countdown or during dead moments in the game (when the game is paused), the serveradmin may take a screenshot of all the players using the UTDC screenshot facility.

The serveradmin must state clearly that a screenshot is about to be taken and will ask all the players to press F1 (ShowScores) and keep the scoreboard visible until the serveradmin confirms the screenshots have been taken. This helps to identify whos screenshots they are.

All of the players must comply and press F1 (ShowScores) when the serveradmin makes his announcement.

The game remains paused until the serveradmin has confirmed the screenshots have been taken.

The taking of unannounced screenshots is forbidden and can lead to a forfeitloss.

Some players will not have screenshots taken due to having a UTDC incompatible OS.

8. No spectators are allowed. Punishments for violating this rule will be decided on a case by case basis by the Cup Supervisors and/or UT Game Supervisor.

12. Roster and Scheduling

1. A predefined roster determines which match must be played in which week. Group matches are to be played in the week specified in the roster. However if both players request it, a match can also be scheduled on the monday of the next week.

2. The exact match date and time must be arranged by the players before the Sunday that precedes the match week. The exact scheduling deadline is Saturday midnight CET.

3. To challenge another player, use the Roster page. To accept a challenge or make a counter challenge, use the Pending page. A challenge that was accepted can still be rescheduled until the scheduling deadline.

4. If by Saturday midnight CET the players still haven't succeeded in scheduling the match, the following procedure is to be followed:

Both players have to send an email to the supervisor before Sunday 22h CET, in which they explain what the problem is and specify all the dates and times (during the match week) on which they can play.

On Sunday, the supervisor will force any matches not scheduled by the players themselves without further consulting them.

If both players mailed the supervisor then he will pick a date on which both players can play if there is one. If there isn't then the supervisor will favour the more flexible player; i.e. the player that can play on the most dates. If there is doubt about which player is more flexible then the supervisor divides the week in 9 slots (7 evenings + Saturday afternoon + Sunday afternoon = 9) and counts the number of slots in which each player is available. Therefore a player that can provide 5 or more evenings/weekend afternoons on which it can play can be certain that the match will be scheduled on one of them.

If only one of the two players mailed the supervisor then he will always pick a date/time that suits that player.

If neither player sent a mail then he will schedule the match as he sees fit.

During the match week, any scheduled match, be it scheduled by the players themselves or by the supervisor, can only be rescheduled if both players agree on a new date/time in the same match week and if both inform the supervisor of this by email at least 1 day before the original date of the match.
[b][center] Match Proceedings [/b] [/center]

16. General

1. The match may not begin before the Referee is ready.

2. If the server crashes during a match, the map will be restarted only if the crash occurred less than 1 minute after the start, or during the 1st round for round-based games. In all other cases the remaining time (rounded to the closest minute and with a minimum of 2 minutes) or rounds will be played, after which the scores will be added to determine the map win.

3. The break between maps will be exactly 10 minutes unless the players ready up themselves. The match referee may force the map start if players don't ready up in time.

4. The match admin will pause the match whenever a player overflows or crashes. The pause may last no longer than 5 minutes (enough time to reboot and reconnect). The maximum total pause time is 10 minutes per map per player. The server can be paused no more than 5 times for the same player's problem (i.e. repeated lag bursts) during the entire match. After that, the player has to play with his problem. Tactical timeouts are not allowed.

5. Players always have to be easily identifiable to referees, opponents and spectators. Therefore, players must use easily identifiable nicks which are the same as (or very closely resemble) those registered on clanbase both on IRC and in-game. Sanctions: .

17. Before the Match

1. Meeting on IRC before the match:

Meeting time = 60 minutes before starting time.

Deadline time = 30 minutes before starting time.

Starting time = the scheduled starting time of the match.

2. The referee and each player gather on the match channel (Quakenet IRC) that is named on the roster page and in the reminder e-mail. No other channel name may be used. Channel logs will be used to keep track of the channel discussion.

3. If one player does not server test, then the opponent is free to pick the match server from the list in the IRC topic. Faking a players's presence by having someone else pose as him during server testing will result in a Red card and a match forfeit.

4. Players who do not test a server are considered to have ping 0 on that server for the final server decision.

5. If one player is not present 30 minutes before the start, then the other player may immediately decide on the server. This player is free to change its server decision later on if the opponent has shown up.

6. If one player is not present at the starting time the result will be entered as a no-show victory for the opponent. If the reason for not showing up is proven to be beyond their control (e.g. ISP problems for all players) the match can be rescheduled.

7. If a player cannot play they must use their wildcard before the scheduled match time or they forfeit the match.


8. Server negotiations:

Server testing begins 60 minutes before the match start, even when a referee is not yet present.

All proposed Server IPs should be in the topic 60 minutes before the match start, the latest time to propose a server to test is 30 minutes before the start. After this time a server can be proposed and tested ONLY if both players agree.

The topic of the match channel must always contain the proposed Server IP(s) of player A, the proposed Server IP(s) of player B. Example: Proposals A: [IP] | B: [IP].

The servers are tested in topic order until the players agree on a match server or all servers have been tested.

All players join the suggested server immediately and without any discussion or delay. Once on the server they make sure they have the proper settings for server testing.

Clans or players that are caught artificially worsening the quality of their connections during server testing will receive a Red card.

Players who have more than one connection or ISP should only use the one they intend to play the entire match during server testing. If they intend to test servers with more than one ISP/connection they should announce this to the referee and opponent in the match channel before server testing starts.

All players must stay on the server until the referee has taken notes and given them permission to leave the server.

If a player does not cooperate during server testing (typically by not joining the server being tested or by leaving it before the referee allows it) it will receive a Yellow card.


9. Server decision

Only visible aspects of the connection quality are considered. These aspects are: ping, stability of ping, smoothness of movement, packet loss indicator value (if available).

Any player not present on a server is considered to have ping 0 in all comparisons of the player' connections as well as in all calculations of average pings.

It is be up to the players to agree on a single server to play on. If they cannot agree then the referee will pick the fairest server given the following:-

1. ClanBase considers pings to be 'equal' when the pings of one player are no more than 125% the amount of their player.

Fair Ping Table (values in Milliseconds) Player A Ping (ms) Player B Ping (ms) 20 25 30 38 40 50 50 63 60 75 70 88 80 100 2. If a player only has lower ping than it's opponent on it's home country server(s), they are deemed to have PING ADVANTAGE for their server(s) and all other servers should be used in preference.

3. If both player have the PING ADVANTAGE for their proposed server(s), then the server with the smallest AVERAGE PING DIFFERENCE will be chosen.

4. As a last resort the referee can ignore the pings of any players with abnormally high pings due to routing/ISP problems when deciding on a server.

5. The referee can decide on a two-server match only if the advantages on the two servers give more equal circumstances than can be found on any single server.

6. A home country server is defined as being located in the same country as the player who performed the server testing, regardless of their personal country preferences on ClanBase. Checks will be based on their ips connected to the server.

10. When the referee has decided the server the players have 10 minutes to join the server. Any complaints regarding the server decision can be taken to the Cup Supervisors after the match. If a player fails to get in the server within 10 minutes they will forfeit the first map, unless it can be proven that they have a valid reason for not doing so.

11. If no referee is available for the match, then the players are still expected to show up on time, follow the above procedures and keep channel logs. If by starting time they still haven't agreed on a server, they should propose one IP each in the topic and then ask the supervisor or a referee who is available on IRC to decide. Both proposed IPs will be tested again before a decision is made based on the principles described above.

12. If two players have agreed on a server beforehand and have reserved it, they can skip the server testing procedure if they both inform the supervisor and/or the referee 30 minutes before the match starts. Once this is done, another server can only be used if both players agree.

13. Once a server has been decided upon, this decision stands for the entire match, except in the following circumstances: both players agree on a server change, the connections to the server have changed drastically for a player, or the server decision was based on information that was false or has changed. Only the referee can judge whether the latter conditions apply to a sufficient degree to warrant a server change.

14. The IP of the server(s) being used must always be put in the topic of the match channel, so the supervisor always knows where the match is being played.

18. After the Match

1. The matchresults can be entered by a Referee/Writer if the screenshots have been sent to him. You always have to send in the results and screenshots to the Cup Supervisors even if a Referee/Writer enters the score for you!

2. Demos can be uploaded or linked, we will use your demo for shot / cap of the week that will be made into a youtube clip!

 

19. Extra


These rules are work in progress and may change, if you have a question ask a sup. They will be completed before the first match week.

Bouncing is not allowed and will result in a loss!




Related links: