Major League IGCTF II
1. League Rules
These rules should now be considered official. Later changes are possible, but any major rule changes will be announced in the forums and on the main news page as well.
1.1 League Format
The second edition of Major League Instagib Capture the Flag, hereafter referred to as MLIGCTF II, will be a season format and feature a single-elimination playoff round. There will be two (2) divisions, both containing six (6) teams. The season portion of MLCTF II will see each team have one (1) match with every other team in its own division for a total of five (5) matches.
1.2 League Point Format
Each match consists of two maps and no tiebreaker. Teams will be awarded three (3) points for each map win, one (1) point for each map loss and zero (0) points for each map forfeit. The four (4) teams with the most points at the end of the regular season in each division will advance to the playoffs. In the event of a tie, the team who has recorded the most game wins (not map wins) will advance. Should both teams have an equal number of game wins, the team that won the head-to-head matchup between both teams will advance. If the teams had split, the team with the better capture ratio in the head to head matchup will advance. If one of the teams had forfeited a map during the head to head, it will be considered an 8-0 loss for the purposes of calculating capture differential. If the teams are still tied in capture ratio in their head to head matchup, the team with the least number of forfeit losses will advance. If both teams have an equal number of forfeit losses, they will play a one map tiebreaker on a map determined by the admins.
1.3 Playoff Format
The playoffs will feature a single elimination bracket between the four (4) top teams from each divison. The quarter-final and semi-final matches will feature a best-of-three format and the finals will feature a best-of-five format. The eight (8) teams are seeded as follows:

(1) 1st Place :: Division 1
(2) 1st Place :: Division 2
(3) 2nd Place :: Division 2
(4) 2nd Place :: Division 1
(5) 3rd Place :: Division 2
(6) 3rd Place :: Division 1
(7) 4th Place :: Division 1
(8) 4th Place :: Division 2

code:
---------------------------------------------------
1 __
8   \__
       \___
     __/   \
3 __/       |
6           |
            |_______
4 __        |
5   \__     |
       \___/
     __/
2 __/
7
--------------------------------------------------




2. Match Rules
2.1 Map Selection
Each round of the regular season will consist of 2 maps selected from a pre-determined map list. Each team will select one (1) map from the list for that round and disclose their selection to the match admin at game time. Once the match admin has announced each team's map selection, neither team may change their map choice. The one exception to this is if both teams pick the same map. Should this happen, the admin will allow both teams to resubmit their map selection. If both teams decide not to change their map selection, that map will be played twice. However, if both teams change their map pick but end up picking the same map, the map that was selected by both teams initially will be the first map played and the map that was selected by both teams the second time will be the second map played for the match. The team listed first one the site will have their map pick played first on the second team's server choice.

The quarter-final and semi-final rounds of the playoffs will be a best of three (3) maps with each team choosing one (1) map from the entire maplist. A team may not choose the same map in both the quarter-final and semi-final matches. Should a tiebreaker be required, they will play the first map on the tiebreaker list that was not chosen by either team. The higher seeded team will play their map selection first.

The final round of the playoffs will be a best of five (5) maps with each team choosing two (2) maps from the entire maplist. Should a tiebreaker be required, they will play the first map on the tiebreaker list that was not chosen by either team. The teams will play the higher seeded team's map selection first and then third.
2.2 Maplist
Week 1:
CTF-EspritLE105
CTF-Dreary
CTF-RainbaseCE
CTF-Command-CE3

Week 2:
CTF-DiamondSword_CE
CTF-ExtortionCE
CTF-Abase
CTF-Revenge-LE102

Week 3:
CTF-Bollwerk105
CTF-Maelstrom
CTF-CoretCE105
CTF-SprintaCB3

Week 4:
CTF-NovemberCE105
CTF-Control
CTF-EternalCaves2
CTF-DukuCB3

Week 5:
CTF-OrbitalLE102
CTF-Gauntlet
CTF-Scandinavium_riffcustom
CTF-BrokenLimitsCB5


Entire Maplist (Playoff TEAM PICK Purposes)
Note that TB maps are predetermined, and listed farther below.
------------------------------------------------------------
CTF-EspritLE105
CTF-DiamondSword_CE
CTF-Bollwerk105
CTF-NovemberCE105
CTF-OrbitalLE102
CTF-Dreary
CTF-ExtortionCE
CTF-Maelstrom
CTF-Control
CTF-Gauntlet
CTF-RainbaseCE
CTF-Abase
CTF-CoretCE105
CTF-EternalCaves2
CTF-Scandinavium_riffcustom
CTF-Command-CE3
CTF-Revenge-LE102
CTF-SprintaCB3
CTF-DukuCB3
CTF-BrokenLimitsCB5


:: Quarterfinals ::
Team1 Choice
Team2 Choice
TB1: CTF-DiamondSwordCE
TB2: CTF-RainbaseCE
TB3: CTF-Scandinavium_RiffCustom

:: Semifinals ::
Team1 Choice
Team2 Choice
TB1: CTF-OrbitalLE102
TB2: CTF-RainbaseCE
TB3: CTF-CoretCE105

:: Finals ::
Team1 Choice
Team2 Choice
Team1 Choice
Team2 Choice
TB1: CTF-OrbitalLE102
TB2: CTF-CoretCE105
TB3: CTF-EspritLE105
TB4: CTF-SprintaCB3
TB5: CTF-RainbaseCE
2.3 Color Choice
During all matches, the team that has not chosen the map to be played is allowed to choose color. During the playoffs, the choice of color for the tiebreaker maps is granted to the higher seeded team.
2.4 Match Scheduling
All matches are prescheduled by the MLIGCTF staff and times will be posted on the MLIGCTF website. If a team cannot field an adequate lineup (5 legal players) at match time, they will be subject to a forfeit loss. The specific rules for a forfeit loss due to a lack of players are enumerated under sections 2.4a through 2.4e.
2.4a Forfeit Loss - Double Forfeit
If neither team can field a team of five (5) players fifteen (15) minutes after the designated start match time or arrival of an admin, whichever is later, both teams receive a forfeit loss for both maps, neither team receiving any points.
2.4b Forfeit Loss - 15 Minutes
If Team B cannot field a team of five (5) members fifteen (15) minutes after Team A has provided five (5) members, provided that it is after the designated match start time or arrival of an admin, whichever is later, Team B forfeits their map pick and Team A receives points for the win.
2.4c Forfeit Loss - 25 Minutes
If Team B cannot field a team of five (5) members twenty-five (25) minutes after Team A has provided five (5) members, provided that it is after the designated match start time or arrival of an admin, whichever is later, Team B forfeits Team A's map pick and Team A receives points for the win.
2.4d Forfeit Loss - Between Maps
If neither team can field a team of five (5) players within ten (10) minutes of the completion of a map, provided an admin is present, both teams receive a forfeit loss for the next map, neither team receiving any points.
2.4e Forfeit Loss - Between Maps
If, between maps, Team B cannot field a team of five (5) members ten (10) minutes after Team A has fielded five (5) members, provided an admin is present and all five (5) members of Team A signal their presence, Team B forfeits the map and Team A is awarded points for a map win.
2.5 Connections
MLIGCTF II is an open ping event, and as such, nearly all connections are accepted and legal. However, a person cannot be on a LAN (local-area network) with the server. Any players found to be in violation of this rule will be suspended from league play until further notice.
2.6 Server Selection
Each team's map selection shall be played on the other team's server selection. However, teams are encouraged to play on the server that presents the best ping for both teams.

During playoff tiebreakers, the server choice is given to the higher-seeded team. However, teams are encouraged to play on the server that presents the best ping for both teams.
2.7 Servers
The admins are responsible for having at least one MLIG2-sanctioned server available for each match, that meets the Server Settings requirements (see next section). PM your match admin if you don't have a server preference (that you can set).

If you have a specific server preference (that's a common server, such as BTB, EO, k3mist's, Sephir's, etc.), let the admin know and the admin will try to accomodate your request. However this server is not guaranteed - it must be setup correctly, possible to mapvote to the correct config, or the server admin must be around.

If you have a specific server preference AND you have admin to it, let the match admin know. As long as it meets the server requirements, and people have no trouble connecting to it, it should be allowed.
2.8 Server Settings
Central servers only

UTDC 1.7c or UTDC 1.8
EUT, current version

20 minute map
NO caplimit
Mapvote with all MLIG2 maps (correct version), or a server admin must be around to force a map

MUST show IPs (i.e. on the F2 screen), or a server admin must be around to take a screenshot of all IPs.
2.9 Server Crash
In the event that the game server crashes during a match, the match will restart with the amount of time that was remaining when the server crashed. If the score was tied prior to the crash then any overtime played in the restart will be official. If the match was not tied any captures made prior to the crash will be added to the score once the clock reaches 0:00. If overtime is required at that point, teams will restart the map again with the first team capturing winning the map.
3. Team Rules
3.1 Captain Responsibilities
Captains will be selected from a list of applicants by the admininstrators. Captains will be required to:

a) Name their team.
b) Draft a competitive team.
c) Assign an assistant captain.
d) Maintain the teams roster.
e) Make team decisions, such as lineup, map, color and server.
f) Remind your teammates to record demos of official mligctf matches.
g) Take SmartCTF screenshots of their matches and provide them to the admins.
h) Collect evidence and provide it to the MLUT admins when accusing another team of breaking the rules.

In the absence of the official captain, the co-captain will act as the captain. In the absence of both the captain and the co-captain, the available player with the highest salary will act as captain.
3.2 Captain Replacement
Should a team be unhappy with their team captain, they may hold a team vote of non-confidence to remove him. If four (4) or more players on a team agree to the removal of a captain, the captain will be removed from the league. The player with the highest salary on the team will then become captain, or he may promote another player to the role of captain.

Should a captain not take his or her duties seriously, he may be removed from his position as captain by the league and may face suspension.
3.3 Team Creation
Each team will consist of nine (9) players. They will be accquired through a draft process on IRC using a bot. The draft order will use the snake format, and begin with the captain with the lowest salary, and continue on in ascending order. Each team will have a salary cap that they cannot exceed, but they also must maintain a roster of nine (9) players at all times.

If a team drops below nine (9) players for any reason the spot(s) on the roster MUST be filled to bring the team back up to nine (9), even if it requires dropping additional players to free up salary.
3.4 Player Salaries
All MLIGCTF players will be listed with a corresponding salary based on their compiled skill ranking.

Over the course of a few days all players, admins and captains will be asked to submit player ranking lists using the integrated ranking program found on the MLUT site. All players are encouraged to use this program. You are able to edit your list at any time and save the changes. Once you are finished, you can submit the list to the admins via the website. The admins then review the lists, and the ones that we believe are accurate enough will be approved.

All approved lists will be averaged, then each player will receive a compiled ranking and will be assigned a salary based on a graduated pay scale.
3.5 Transactions
Captains and assistant captains can add and drop players from their roster at anytime using the MLUT website. Teams must remain under the salary cap and also must maintain a nine (9) player roster at all times. If a team drops below nine (9) players for any reason the spot(s) on the roster MUST be filled to bring the team back up to nine (9), even if it requires dropping additional players to free up salary.

Teams will be locked and unable to make transactions during a match, and will remain locked until the match is over. Teams will be unlocked following the match, unless they were eliminated from the tournament, or have been mathematically eliminated from the playoffs.

Even if teams are not locked physically on the website, they are considered locked based on the above rules and any transactions breaking those rules will be reversed.
3.5a Transactions Limit
Captains and assistant captains are allowed to make a total of ten (10) transactions during the five rounds of the regular season, with a limit of two (2) transactions per round. They are also allowed one (1) transaction during the entirety of playoffs. If a transaction is not used in a given round, it will become void for use in future rounds.
3.6 Player Holdout
If a player feels he is being treated unfairly, he may present his case to the admins and we will contact both him and his captain to resolve the dispute. Should an inquiry find that the captain is at fault, the player will be returned to the freeagent list at his current salary.

The team can not reacquire that player and the spot on the roster MUST be filled to bring the team to nine (9), even if it requires dropping additional players to free up salary.

Please note that if a captain or co-captain removes themselves from their roster, they will be removed from the league.
3.7 Inactive Player
If a player misses two (2) consecutive matches, a team can drop him and contact an admin with an inactivity request and the player will be removed from the league. If the player is picked up during the inactivity request the transaction will be reversed.
3.8 Multiple Teams
No player may play for more than one team in a single round. Any player caught breaking this rule will be removed from MLIGCTF II. Captains who attempt to violate this rule will be removed from the tournament and have any maps played with the violating player forfeited to the opposing team.
4. Game Rules
4.1 Cheats
All hacks, bots, radars and cheats are illegal. This includes any kind of automated aiming bot, a trigger-bot, any form of radar, server-crashing bugs and tools, packet loss and latency inducing devices, HUD timers, and anything in that same vein or spirit. Please use your brain. All violations will result in an PERMANENT EXPULSION for the offending player from MLUT and all MLUT related events. It will also result in a forfeit loss of the match in question for the offending team.

In addition, players can be convicted of the above without being caught by server cheat protection. Admins reserve the right to take into account all evidence regarding said player, including but not limited to: demos, screenshots and server logs.
4.1a Skins
Players may not use any skins other than those included in a default installation of Unreal Tournament, and may not alter the appearance of any of these skins by any means.
4.1b Spectators
Should any players be spectating a game without the consent of an administrator, they risk a possible suspension from league play. Should they be a member of a team playing in that match, the offending team will receive a forfeit loss for the map in question.
4.1c Boosts
Boosts that enable players to reach or utilize map bugs are illegal and will result in the team forfeiting their map.
4.1d Frog Jumps
Frog Jumps and/or Bunny Hops are illegal and any player found doing them will forfeit the map for their team.
4.1e Demos
Every player must record a first-person demo of each map he plays and keep this demo for fourteen (14) days after the match. If a player joins the server after the start of a map, it is his responsibility to ensure that he starts recording a demo before commencing play.

If foul play is suspected in a match, a player must submit an inquiry directly to an admin. An accusation MUST be made before 11:59pm EST the day AFTER the match, or it will not be considered. The player making the accusation of foul-play, must submit his/her own demo to the admins, along with an explanation of the accusation, which player is in question, and the location in the demo of suspicious play. If the accusing player cannot supply their own demo, the inquiry will be dropped. If review of the accuser's demo reveals no suspicion of foul-play, the inquiry will be dropped. The admins will inspect the accuser's demo, and if there is the possibility of foul-play, the admins will request and then review the demo from the player in question.

Should the player or players in question be unable or unwilling to fulfill the admin staff's demo request promptly, the following punitive structure will be followed:

1st Offense: The map(s) in question will be forfeited to the opposing team and the player(s) in question will be officially warned.

2nd Offense: The map(s) in question will be forfeited to the opposing team and the player(s) in question will be suspended for one (1) official match.

3rd Offense: The map(s) in question will be forfeited to the opposing team and the player(s) in question will be removed from the season.
4.2 Server Admin
If a player logs in to a server as administrator prior to a match, the player must logout when complete, and reconnect to the server. At no time may a player login as administrator during the match. Doing so will result in a forfeit loss for the map in question for the offending team, and a possible suspension for the offending player.
4.3 Connection Fraud
All connection fraud is illegal, including but not limited to, faking your ping or disturbing anothers connection through any means. Any violations will result in a forfeit loss of the map in question for the offending team. The offending player will be suspended from play for the current season with the possibility of a longer ban.
4.4 Aliasing
A player may not use multiple identities over the course of the season. The name a player uses and that will be tracked by the admins defaults to the name they used to sign up. If at any time a player refuses to use the name they signed up with when asked by an admin to change it during a match, they will be denied permission to play. Repeated offences will result in a player being suspended from play for the rest of the season.
4.5 Ringing
Using a ringer (a player not on your eligible roster, who is generally posing as an eligible player) is a serious offence. Using a ringer will result in the offending player, as well as any captains or co-captains present, being banned indefinitely. In addition, the team will forfeit the maps in question and be disqualified from play for the remainder of the season.
4.6 Map Bugs
Exploiting maps bugs is illegal, such as but not limited to dropping flags into areas they are not supposed to be able too such as through walls and/or doors. Any violations will result in a forfeit loss of the map in question for the offending team.
4.7 Fake Flag Drops
Dropping of the flag to obtain a tactical advantage while not in danger of the flag being returned is illegal. Players caught exploiting this tactic will forfeit the map.
4.7a Flag Passing
Dropping or passing of the flag to a teammate is legal. The passing of the flag must be completed within five(5) seconds of the drop to stop the exploitation of rule 4.7.
4.8 Taunts
Excessive use of text taunts is illegal. Using taunts bound to movement keys, firing keys, weapon switch keys, or any other frequently used bind in the game, is illegal. First violations will result in a warning. ANY Repeated offence will result in the player being removed from the player list for the current season.
5. Administration
5.1 Administrative Powers
All MLIGCTF admins have the power to make any changes to information on the MLIGCTF website. Should a captain or player notice any mistakes, he or she may contact an admin to make any changes. Should a captain, player or other admin feel that an admin is abusing their power, he or she may file a grievance with the MLIGCTF II head admin. The MLIGCTF administration will then look into this claim
5.2 Conflict Resolution
Any and all problems (including those not governed in the rules) will be resolved by an admin vote. All admins have one (1) vote and can choose not to vote if they so please. In the hopes of keeping things moving, all open votes have a twenty-four (24) hour window in which admins can place their vote. There may, however, be exceptions to this twenty-four (24) hour window, should the vote be for something that does not require immediate resolution.
5.3 Conflict Of Interest
Admins are not allowed to vote on any issues that involve a team that they are a member of. They may provide feedback and their input, but their vote will not count in determining the final outcome.
5.4 Asterisk
The admins reserve the right to alter any rule in anyway they see fit if there is a passing admin vote. This is to protect the integrity of the tournament in case of a loophole or something being overlooked.
Moderated By: MLUT

MLIGCTF II Features