Rules
              
Season 6 Rules
              The rules are preliminary and subject to change. 
              
              CTITC rules
              
              §0.1 CTITC was started for the enjoyment of CTI gaming, to come 
              together with friends, and to meet more friends. 
              §0.2 CTITC is NOT set up for deciding who is the best islandmaker 
              or who has the best PC, etc...
              §0.3 CTITC is lead by the administration and all decisions are 
              made by the administration. The CTITC administration includes:
              
              Chipp [AFC]
              Coward Heart [SWEC]
              Fanatic [AFC]
              Iron [PLAF]
              Mahlkav [SWEC]
              Scipio [AFC]
              Soy Roy [PLAF]
              
              §0.4 CTITC admins encourage constructive help with scripting, game 
              filechecks, and islandmaking. 
              §0.5 If a person or team cant find fun & amusement in CTITC they 
              can resign from the league or may be asked to resign. 
              §0.6 CTITC forum is used for discussion about CTITC. Using foul 
              language, spamming, flamming, insulting signatures towards players 
              or CTITC, and general poor sportsmanship conduct will not be 
              permitted.
              §0.7 Any bug, exploit or problem may and should be reported in the 
              forum. Admins will examine the complaint and will try to find a 
              solution, but spamming, flamming, or continued arguing about the 
              bug or complaint is forbidden and could lead to warning(s) and a 
              possible league ban.
              
              
              1 Teams
              
              §1.1 Each team must have at least one CTITC Team Leader (TL) who 
              is responsible for match bookings.
              §1.2 A team must register at least 7 players and have their 
              squad-XML available before the season start.
              §1.3 Only team members are allowed to participate for a team and a 
              player may only play for one team in the Cup,
              §1.4 A Team can register new players for their team during the 
              season, New players must be registered at least 2 hours before 
              match they plan to play in. (§1.3)
              §1.5 All registered players are to use a version of OFP that has a 
              legal ID. This ID must be posted in team registration.
              §1.6 Fake ID may be reported to the CTITC administration.
              §1.7 If a team tries to play a tournament match with banned 
              player(s) or refs, then that team will be banned for the rest of 
              the season. Teams are responsible for keeping their banned players 
              out of matches.
              
              
              
              2 Matches
              
              §2.1 All matches are played using a CTITC-version of the mission 
              designed for the season on a CTITC approved server. The current 
              missions are crcti_0.93_@ctitc6b and crcti_0.93_@cr09_ctitc6b for 7 
              vs 7. Approved islands for Season 6 are feta, sinulver2, and 
              anilymver2. 
              §2.2 All Match parameters must be decided in the match schedule 
              thread prior to game day. Match parameters include: choice of 
              island, mission, match time/day, team side (East or West), spawn, 
              and referees. (Refer to section 4 for referees.) 
              §2.3 The side (east or west), island, and mission is chosen by the 
              home team. Fixed spawn point ( north/south) and view distance are 
              chosen by the away team. Refer to rule §2.11 for finals.
              §2.4 A proposed match time in the match booking thread must be 
              responded to within 48 hours. If it is not, it will be regarded as 
              accepted and match will be scheduled for that time and day.
              §2.5 A match is restarted if anybody looses connection within 2 
              minutes from start, no restart after 2 minutes except if both 
              teams allow it.
              §2.6 In the event of the disconnection of an entire team, the 
              surviving team is awarded a town win 5 minutes after last member 
              of the opposing squad disconnects. 
              §2.7 A match is replayed if the server crashes.
              §2.8 A team must have at least 5 human players at start, i.e. max 
              2 AI squad leaders at start.
              §2.9 If a match is not won within the time limit of 3 hours the 
              match is considered a draw.
              §2.10 If a team fails to show up for the scheduled match with a 
              minimum of 5 human players, the referee(s) can choose to declare 
              it a WO after a minimum of 30 minutes and a maximum of 60 minutes 
              after the proposed match start. The referee(s) will determine how 
              much time is allowed before declaring a WO. If only one team shows 
              up for match, refer to rule §2.4 and award the ready team a win on 
              WO. Winning team then receives +2 points and the other team -2 
              points.
              §2.11 The Final is to be played on the island and mission that has 
              been chosen for the majority of games throughout the tournament. 
              The highest seeded team will choose side, and the lowest seeded 
              team will choose spawn position. The final will be a best of three 
              games played.
              §2.12 A players ping cannot exceed 350ms at start of game and 
              cannot exceed a high level of ping or low bandwidth to be 
              determined by the referee(s) as being detrimental to the game. 
              Referee(s) will then have the option to call the game to be 
              re-scheduled, or ask a specific player or players to leave the 
              game in order for it to continue lagfree. Referee(s) ping(s) are 
              exempt from this rule. In addition, the mission will warn of low 
              bandwidth and will lock the player or players, along with their 
              associated AI, if bandwidth drops below a limit preset by the 
              crCTI mission. If scheduled game server has a slow connection as 
              determined by the referee(s), the game can be moved to an 
              alternate CTITC approved server. There will be no protests allowed 
              regarding ping or bandwidth performance after game ends. 
              
              
              3 Exploits
              
              §3.1 50% of a building must be visible. Players cannot do the 
              following to CTI buildings: they can not stack inside one another, 
              wall in, hide inside existing island structures, place in water, 
              or float in the sky. 
              §3.2 CTI buildings and MHQ have to be reachable on foot by ground 
              level. No ladders or stairs, player built or not, vehicles, other 
              players, island structures, or island terrain will be considered 
              as objects to gain access to the MHQ. Players cannot stack CTI 
              buildings, vehicles, or CTI objects on top of the MHQ. Exception 
              to §3.2 is when MHQ is being moved through or over water. While 
              MHQ is being moved through or over water, players may not wall in 
              the MHQ or stack CTI buildings, vehicles, or CTI objects on top of 
              the MHQ.
              §3.3 Exploits will be addressed during game, it will be the 
              referees decision to either stop the exploit usage, stop the 
              match, or let it continue to be protested later - CTITC admins 
              will make final decision on which team is the winner or if a 
              rematch is needed.
              §3.4 All players are to use a mod-folder with the name: @ctitc6, 
              which should include all addons used in the tournament. During 
              connection to a match, load only that mod-folder. This is to make 
              sure everyone uses the same addons.
              To clarify this; players are to have the following addons folders 
              in the @ctitc6 folder called "@ctitc6addons", this folder should 
              have the following files:
              
              anilymver2.pbo – 2,950kb 
              baracken.pbo – 9,574kb
              cr09.pbo – 106kb
              cti_markers.pbo – 1kb
              ctiobjects02.pbo – 460kb
              cwkzodiac.pbo – 12,564kb
              feta.pbo – 3,156kb 
              kegak107.pbo – 928kb
              sinulver2.pbo – 4,323kb
              
              §3.5 If a player creates an ammobug, that player is responsible to 
              attend to it, if the player fails to work it out, the game is 
              either won by opposing team or replayed, referee(s) decision. This 
              is to make sure that the game is as lagfree as possible, and to be 
              sure that the ammobug was not made on purpose.
              §3.6 Moving vehicles or MHQ outside of the island boundary or 
              sending vehicles or MHQ with AI outside of the island boundary is 
              forbidden. In the event of accidentally moving a vehicle or MHQ 
              outside of the island boundary, players will have two minutes to 
              return the vehicle or MHQ to inside the island boundary or forfeit 
              the game. 
              
              
              4 Referees
              
              §4.1 Any registered player can be a referee. Both teams have to 
              agree on referee(s). Administration won't accept any complaints 
              about referee(s) after the match is played. Don't play if u don't 
              trust the referee(s)
              §4.2 Global channel is to be used by team leaders and referee(s) 
              only on the referees request. If a player spams, flames, and/or 
              uses foul language in the in game chat line, he/she can be kicked 
              by the referee(s), and will not be allowed to play the game. This 
              includes any sound spam. Should the player be kicked before the 
              game, another player can replace him/her, but if the player gets 
              kicked during the game, the team will have to do without him/her 
              regardless of how many players the team has online.
              §4.3 A player can be reported to CTITC, on the grounds stipulated 
              in §4.2, if the players use of spam or foul language has been 
              severe. The administration will decide what measures to take, and 
              can suspend the player from the CTITC forum and league. An admin 
              can not take part if the admin and the player in question belong 
              to the same team.
              §4.3 Players banned from CTITC cannot participate as referees 
              during matches. 
              §4.4 If anybody reports a possible fake or non-registered ID 
              BEFORE the match starts, the referees will check the questionable 
              players ID against the CTITC forum "Team Registration". If ID is 
              not found there, the player will not be allowed to play. (§1.4) 
              Complaining after match will not be accepted as a protest. All ID 
              inquiries must take place before the match starts
              
              
              5 Mixed
              
              §5.1 Voice_quiet.pbo, modified voice.pbo, missing voice.pbo, and 
              resource.cpp or any modified resource.bin file is not allowed.
              §5.2 CTITC does not allow any additional sound or sky texture 
              packs. Stock OFP sounds and sky textures are the only sound and 
              sky texture files allowed during league matches.