1. League Rules
|
![](imgs/spacer.gif) |
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
|
![](imgs/spacer.gif) |
The fourth edition of Major League Instagib Capture the Flag, hereafter referred to as MLIGCTF IV, will be a season format and feature a single-elimination playoff round. There will be two (2) divisions, both containing five (5) teams. The season portion of MLCTF IV 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
|
![](imgs/spacer.gif) |
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
|
![](imgs/spacer.gif) |
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 |
2. Match Rules
|
![](imgs/spacer.gif) |
|
2.1 Map Selection
|
![](imgs/spacer.gif) |
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
|
![](imgs/spacer.gif) |
Week 1:
CTF-Bollwerk105
CTF-DiamondSword_CE
CTF-SprintaCB3
CTF-Gauntlet-IG
Week 2:
CTF-EternalCaves2
CTF-OrbitalLE102
CTF-ExtortionCE
CTF-EpicmanIG
Week 3:
CTF-CoretCE105
CTF-Dreary
CTF-TerraIG][
CTF-EspritLE105
Week 4:
CTF-Revenge-LE102
CTF-DukuCB3
CTF-Command-CE3
CTF-Scandinavium_riffcustom
Week 5:
CTF-NovemberCE105
CTF-Control
CTF-BrokenLimitsCB5
CTF-RainbaseCE
Entire Maplist (Playoff TEAM PICK Purposes)
Note that TB maps are predetermined, and listed farther below.
------------------------------------------------------------
TBD
:: Quarterfinals ::
Team1 Choice
Team2 Choice
TB1: SprintaCB3
TB2: Gauntlet-IG
TB3: TerraIG][
:: Semifinals ::
Team1 Choice
Team2 Choice
TB1: Scandinavium_riffcustom
TB2: DukuCB3
TB3: OrbitalLE102
:: Finals ::
Team1 Choice
Team2 Choice
Team1 Choice
Team2 Choice
TB1: Revenge-LE102
TB2: BrokenLimitsCB5
TB3: EspritLE105
TB4: EternalCaves2
TB5: RainbaseCE |
2.3 Color Choice
|
![](imgs/spacer.gif) |
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
|
![](imgs/spacer.gif) |
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
|
![](imgs/spacer.gif) |
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
|
![](imgs/spacer.gif) |
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.4d Forfeit Loss - Between Maps
|
![](imgs/spacer.gif) |
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
|
![](imgs/spacer.gif) |
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
|
![](imgs/spacer.gif) |
MLIGCTF IV 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 Fair Ping
|
![](imgs/spacer.gif) |
It is extremely difficult to find a level playing field in this age of the Internet.
MLIGCTF has decided upon a simple guideline to use to determine if the server chosen for the match is considered "neutral", or fair.
North American Setups
A fair Ping spread for a neutral server will be an average of 50 ms for both teams for the majority of players.
Team A pings 70-100, Team B pings 100-120 (50ms spread) This server is Neutral and should be used as the ONLY server for the match.
Team A pings 50-150, Team B pings 75-200 (150ms spread) This server is NOT Neutral, though if it is playable for both teams, COULD be used as part of a 2-server match.
Every effort should be made to find a NEUTRAL server for matches to minimize delays and confusion |
2.7 Servers
|
![](imgs/spacer.gif) |
The admins are responsible for having at least one MLIG IV-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 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
|
![](imgs/spacer.gif) |
Central servers only
UTDC 1.7c or UTDC 1.8
EUT, current version
20 minute map
NO caplimit
Mapvote with all MLIG IV 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
|
![](imgs/spacer.gif) |
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
|
![](imgs/spacer.gif) |
|
3.1 Captain Responsibilities
|
![](imgs/spacer.gif) |
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
|
![](imgs/spacer.gif) |
Should a team be unhappy with their team captain, they may hold a team vote of non-confidence to remove him. If 60% of the 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
|
![](imgs/spacer.gif) |
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
|
![](imgs/spacer.gif) |
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
|
![](imgs/spacer.gif) |
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 ten (9) player roster at all times. If a team drops below ten (9) players for any reason the spot(s) on the roster MUST be filled to bring the team back up to ten (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. Team rosters will be locked 2 days before playoffs start.
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
|
![](imgs/spacer.gif) |
Captains and assistant captains are allowed to make transactions during the five rounds of the regular season. They are allowed one (1) transaction during the entirety of playoffs. |
3.6 Player Holdout
|
![](imgs/spacer.gif) |
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
|
![](imgs/spacer.gif) |
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
|
![](imgs/spacer.gif) |
No player may play for more than one team in a single round. Any player caught breaking this rule will be removed from MLIGCTF IV. 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. |