1. League Rules            
These are the official rules for MLIGZP IX. These rules will NOT be changed. In the event that a loophole or poor foresight severely threatens the integrity of the league, the admins may modify these rules, upon majority vote, for the benefit of this AND future leagues. Any major rule change will be announced on the news page and will be up for discussion. If you are a captain or would like to be a captain, take the time to know the rules. Rules will be strictly enforced.

Note that if a player is found severely abusing the league, regardless if its covered in the rules, said player could be removed from the league upon majority admin vote.
1.1 League Format            
MLIGZP IX will be a season format where each team will play every other team once and feature a single-elimination playoff bracket. Matches will take place on Sundays and Thursdays.

Hours of League matches:
8:00 PM EST
9:00 PM EST
10:00 PM EST

EST = Eastern United States Standard Time

01:00 GMT
02:00 GMT
03:00 GMT

- Only 1 Division containing 10 teams
- Check the Schedule for playoff seeding.
1.2 League Point Format            
Each match consists of two maps and no tiebreaker. Teams will be awarded 3 points for each map win, 1 point for each map loss and 0 points for each map forfeit. The 6 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 better capture ratio overall will advance. If still tied, 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.

*** Team sizes - 10 per team
2. Match Rules            

2.1 Servers            
The admins are responsible for having at least one MLIG-sanctioned server available for each match that meets the Server Settings requirements (see next section). PM your match admin 10 minutes before match time if you have a server preference and the admin will try to accommodate your request. If the server is NOT MLIG approved, but is setup correctly, (mapvote, anticheat, etc.) it will be allowed only if both captains AND the match admin agree.

MLIG servers must be approved by MLIG Admins. All server passwords and information must be disclosed to admins for fair and efficient play on-season and during the off season in #MLIG.

Approved MLIG Servers:

See #MLIG on
2.2 Map Selection             
Each round of the regular season will consist of 2 maps selected from a predetermined map list (see next section). Each team will select 1 map from the list for that round and disclose their selection to the match admin 30 minutes before match 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 once again, 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 on the site will have their map pick played first on the second team's server choice. You may not choose the same map twice during the regular season.

The quarter-final and semi-final rounds of the playoffs will be a best of 3 maps with each team choosing 1 map from the entire maplist. A team may not choose the same map in both the quarter-final and semi-final matches. The higher seeded team will play their map selection first.

The final round of the playoffs will be a best of 5 maps with each team choosing 2 maps from the entire maplist. The teams will play the higher seeded team's map selection first and then third.
2.3 Tiebreaker Selection            
TB maps (Tiebreaker) are only used in the Playoff season. There are no TB's in the regular season.

Tiebreakers for Quarter & Semi Finals

- Beginning with the higher seeded team, each team will take turns discarding maps from a pool of eligible maps until only one map remains. The pool of eligible maps will consist of all maps that neither team has picked so far in the playoffs* (tiebreaker maps from previous rounds will be included in the pool).

Tiebreakers for the FINALS

- The team with the most caps after 4 maps can decide who eliminates a map first. If both clans have the exact same number of caps after 4 maps, then the Higher seeded team gets to decide who eliminates a map first. A map already picked in the final cannot be picked for the final TB round.

* All maps are reset at the beginning of the finals match
2.4 Colour 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 lower seeded team.

MLIG Tip: Why does this matter? - Colour choice can affect a team with ping, sight, etc.
2.5 Match Scheduling            
All matches are scheduled by the MLIG admins and times will be posted on the MLIG 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 section 2.5a.

MLIG Admins do not pick schedules, all teams are placed into a randomization tool and scheduled based on random chance.
2.5a Forfeit Loss             
Fielding players is an important aspect in MLIG. There are two scenarios as to forfiet issues when a team cannot field 5 players.

When Match Admin is present:

- If a match admin is present within 15 minutes from the start of match time (as described by the MLIG Schedule), then both teams will have 15 minutes from the arrival of an Admin to field 5 players. For example, if Rebellion arrives at 8:02 when the schedule has the match starting at 8:00 PM, then both teams will have fifteen (15) minutes from 8:02 to field five players (till 8:17 PM).

When Admin is not present:

- Matches without Match admins can occur. If an admin is predetermined to be not attending a match, then both teams have 15 minutes from the start of the match time as described in the MLIG schedule to field five (5) players. If 15 minutes from the start of match time has passed, and an Admin has not shown up (and they were supposed to), teams can screenshot an F1 stats (must have SmartCTF to work) to show admins that their entire team has been in the server for 15 minutes and the other has not. If a forfiet issue arises, then admins can take a look at the screen shot to determine who gets the forfiet.

If neither team can field 5 players in any circumstance, both teams will receive forfeit losses for both maps. In the event that a team cannot field 5 players 10 minutes after the completion of a map admin or no admin, then that team will receive a forfeit loss for that map. It is possible for both teams to receive a forfeit loss if neither team is ready.
2.5b Rescheduling            
Each MLIG team is given (2) WildCards , these WildCards can be used to re-schedule an official regular season match for whatever reason.

The re-scheduled matches can take place :
On a non-MLIG day, or on a MLIG Match day but NOT during any match times.

WildCards are only used in the regular season. WildCards must be used to re-schedule a match unless both captains agree on a reschedule. An Admin may only alter the conditions of a WildCard after a review with the other Admins and both team captains.

Teams are suggested to only use WildCard when real problems arise, such as connection problems in their team, or un-forseen issues with schedule or date.

When a WildCard is used, the team may PM an MLIG Admin in up to 15 mins from (so if match is at 8:00, you have until 8:15 to use a WC) the original match time to start the process. The team captain must talk with the opposing team and immediately re-schedule the match to another day and time. The re-schedule must occur before the regular season ends. Both teams must agree to the re-schedule date and have approval from a MLIG Admin. Everyone is busy these days, and we all must make sacrifices for the others in order to have a functioning league.

- WildCards are not allowed during the Playoffs.

- Once a WildCard is used, the opposing team cannot use a WildCard to re-schedule the WildCard match.

- If both team captains agree to a re-schedule, then a WildCard is not needed.

Consequences :

- If the team using the WildCard fails to propose a re-schedule date within 2 days after the match, the Admins have the right to hand out a forfiet loss for that team

- If the opposing team fails to respond with discussion to the WildCard using team within 2 days after the match, the Admins have the right to hand out a forfiet loss for that team.

- If neither team can come to an agreement, the Admins will force the match to the nearest match date, on the time slot that only has one match playing. Both teams can risk a forfiet loss if they do not show. The admins can force the match to a later date than the next match date if needed.
2.6 Connections             
All connections are accepted and legal, with one exception. 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 and forfeit the maps where this occurred.
2.7 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.
2.8 Server Settings             
Required Mutators:
Instagib, SmartCTF 4D, BDBMapVote3.04 or MapvoteLA13, Monster Announcer (Preferred)

Required Server Actors:
UTPureRC7G, ACE 0.8h, SecureValidate, ServerCrashFix

Server Settings:
Max Team Score:10
Time Limit: 20 minutes
Sudden Death Overtime: True
Tournament: On
Max Teams: 2
Friendly Fire: 0%
Game Style: Hardcore
Game Speed: 100%
Air Control: 35%
Bots: Off
Force Respawn: Off
Tick Rate : 65

Configured Internet Speed / Netspeed: min. 5000, max 20000 at all times during the match. Furthermore, any change of net speed during any map while in the server is forbidden. Violating any part of this rule will result in a forfeit loss of the map the violation occurred in.

Servers must have the latest anti-cheat installed
ACE v0.8h

Players who have problems caused by ACE 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 nploader allowone

Any player allowed to play through use of the above command is required to upload all of his/her demos to an admin within 48 hours of the scheduled match time. Failure to submit these demos on time will result in a forfeit loss on the applicable maps.

It is the responsibility of all participants, admins, captains, and players to ensure that all the settings are correct prior to starting the match. Once both teams have clicked in they have agreed to the current settings and no map can be replayed due to settings that are in conflict with those on the rules page. The lack of HUD during a match does not merit a pause or a restart of the map as it can easily be fixed within seconds. If serious errors are missed the admin staff will make a ruling based on a case by case scenario.
3. Team Rules            

3.1 Captain Responsibilities             
Captains will be selected from a list of applicants by the admins. Captains will be required to:

a) Name their team.
b) Draft a competitive team.
c) Assign a co-captain.
d) Maintain the team's roster.
e) Make team decisions, such as lineup, map, colour and server.
f) Remind your teammates to record demos of official MLIG matches.
g) Take SmartCTF screen shots of their matches and provide them to the admins if admins did not do so themselves.
h) Collect evidence and provide it to the MLIG admins when accusing another team of breaking the rules.
i) Create a team channel.
j) In the event MLIG has MLIGServ, the captain have the option to notify admins of server choices, map choices, etc. by using it

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 (can be admin overridden).
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 5 or more players on a team agree to the removal of a captain, the captain will be removed from the league. The co-captain or player with the highest salary on the team will then become captain, or he may promote another player to the role of captain/co-captain (can be admin overridden).

This vote must be logged and documented. It can also take place in the Admin channel for official logging (contact an admin).

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 10 (TEN) players. They will be acquired through a draft process on IRC using a bot. The draft order will be determined each round by the team's overall salary up to that point in the draft. The team with the lowest overall salary will draft first each round. Each team will have a salary cap that they cannot exceed, but they also must maintain a roster of 10 players at all times.

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

Over the course of a few days, all players, admins and captains will be asked to submit player ranking lists. As of right now, ranking lists cannot be saved on the site (it prevents any further editing) so you must PM an admin or make a post in the ranking thread with your rankings. 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 choose to add and drop players from their roster at anytime by informing an MLIG admin or by posting in the designated trade thread so that your request is timestamped. Teams must remain under the salary cap and also must maintain a (TBA) player roster at all times. If a team drops below 10 players for any reason the spot(s) on the roster MUST be filled to bring the team back up to 10, even if it requires dropping additional players to free up salary.

Teams will be locked and unable to make transactions during the start of a match (this means the start of map 1), 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.

MLIG Tip: Why is trading useful? Peoples skills are not fine-tuned. Trading allows you to fine-tune your team to make the most chance at winning! Make sure you review the salary!
3.5a Trade Limitations             
Captains will be limited to 4 moves per week (this includes adding people from free agency and trading without teams).
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 free agent 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 (TBA), even if it requires dropping additional players to free up salary.

Note that if a captain or co-captain removes themselves from their roster, they will be removed from the league and possibly future leagues.
3.7 Player Inactivity and Insubordination             
If a player misses 2 consecutive matches, a team can drop that player and contact an admin concerning an inactivity drop. The player may be exchanged for a player of that captain’s choosing from the FA pool. This player is now inaccessible for any trade transactions. If the inactive player returns later in the season before the roster lock date, the player’s original team gets first choice as to whether or not they’d like to re-add that player to their roster.

If a player is found to be not showing or refusing to play for a certain team due to their dislike of the team or its captain, then that player may be removed from the league entirely per captain request and legitimate evidence against that player. Everyone is drafted to unexpected teams at times. The draft process is meant to make the league as balanced and interesting as possible, not to stack teams. If you will only play for certain players or captains, then do everyone a favor and simply do not sign up.
3.8 Multiple Teams            
No player may play for any team other than the one they are listed under on the MLUT website. Any player caught breaking this rule will be removed from MLIG. 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, using packet loss and latency inducing tools, 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 MLIG and all MLIG 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.

All players previously caught or removed for any of the above reasons will not be allowed to play. *** Pending review
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 Boosting and Map Exploits            
Teamwork is a large part of any team-oriented multiplayer experience. Boosting is encouraged as long as they are all legal boosts. Legal boosts are any that involve: aiding a flag carrier move quickly from base to base or to the flag, to accessible spots in a map that ARE NOT glitches but designed parts of the level. Boosts that enable players to reach or utilize map bugs are illegal and will result in the team forfeiting their map.

The MLIG Final Map list thread will contain information on what boosts are allowed and what boosts are not.

Purposely dropping/stalling the flag where it CANNOT be picked up/returned by players is also illegal and will result in the team forfeiting their map. Also, the use of map exploits by a single player to gain an advantage on unsymmetrical maps are also illegal (the wall dodge in EC2 on the red side, etc).
4.1d Frogjumps / Bunny Hops / Backshooting            
Frog Jumps and/or Bunny Hops are illegal and any player found doing them will forfeit the map for their team.

Back shooting for no reason thereby ruining the flow of the match is discouraged. Back shooting is tactical when a team mate has the flag, or one is trying to prevent the opposition from covering an enemy flag carrier.
4.1e Demos             
Every player must record a demo of each map played and keep this demo for 1 week after the match. (Specs cannot demo for you.) 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. Demo manager makes this automatic, though you should always check it is recording by either making use of ACE's feature at the top or typing demorec to see if one is currently active.

Requesting Demos:

If foul play is suspected in a match, a captain must submit an inquiry directly to an admin no later than 24 hrs from the start of the match. The player making the accusation of foul play should submit their own demo with a few details, such as specific times which are fishy. Failure to do so will result in no action being taken. The admin will then request the demo from the accused and give it to the accuser. If the accuser still feels after reviewing the demo that foul play was involved then the admins will investigate.

Each team can request a maximum of 1 demo per map of the opposing team. More demos can be requested only if the match admin agrees something fishy is going on.

Should the accused be unable or unwilling to provide a demo, the following punitive structure will be followed:

1st Offense: The map(s) in question will be forfeited (or replayed) according to the opposing team's captain's discretion and the player(s) in question will be officially warned.

2nd Offense: The map(s) in question will be forfeited (or replayed) according to the opposing team's captain's discretion and the player(s) in question will be suspended for 1 official match.

3rd Offense: The map(s) in question will be forfeited (or replayed) according to the opposing team's captain's discretion and the player(s) in question will be removed from the season.

In addition, players who are on the MLIG Watchlist must submit every map's demo that they play in. These players must do this within 24 hours or face the above consequences. Captains will be notified of any watchlist players on their team.
4.2 Server Admin            
If a player logs in as a server 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 another's 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.3a Packeting/ DDOS             
In recent seasons we have seen an increase of packeting ( sending a mass of information to disconnect one from the internet) of certain players for some reason. Unless we know the source of the attack with solid proof or enough circumstantial evidence, the admins are powerless to do anything to prevent this type of attack. In the event of a packet attack on you while a match, you must report this to the admin spectating your match, or to one of the other admins. During experiencing these attacks, we suggest the player affected take an SS of his PL or Ping to prove his case.

- If this packet attack just affects you, we recommend you sub out with another of your players.

- If this packet attack affects your whole team, we recommend you reschedule with the other captain for a later date and different location (speak with an admin to work this out).

- If this packet attack affects you and there is no way you can sub out (tactically fatal for your team) please consider re-scheduling the match (speak to an admin).

- If this packet attack affects the whole server the admins will offer no penalties and re-schedule the match to a different location. The admins will also contact the server provider and alert them of what is going on.

The MLIG admin team is doing all it can to make sure packet attacks are at a minimal or do not happen at all in this season. We strongly recommend you take our suggestions in order to ensure fair game play for all. We are sorry there are still middle school aged kids in this community.

*Contact your ISP to help with you constant packeting.

*Found Packeters will be banned from MLIG for a full year.
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 offenses will result in a player being suspended from play for the rest of the season.

If a team is playing with a certain theme, they must post that theme and who the players are in the MLIG forums. The Admins will then run a quick IP check before the match to confirm. Failing to do this will result in the above consequences.
4.5 Ringing             
Using a ringer (a player not on your eligible roster, who is generally posing as an eligible player) is a serious offense. 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 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 offense will result in the player being removed from the player list for the current season.
5. Administration            

5.1 Administrative Powers             
All MLIG admins have the power to make any changes to information on the MLIG website with a vote. 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 MLIG head admin. The MLIG administration will then look into this claim.
5.1a Tolerance/ Admin Harrasement            
Admins have the right to suspend players due to failure to cooperate, verbal harassment, and purposely inconveniencing any admin. Admins are using their free time to run the league and should be treated with respect.

Suspensions will be handed out as follows:
- First suspension will be for one map
- Second suspension will be for one match
- Third suspension will be for one week

If a problem arises with your match admin, take it up with another admin and/or the head admin.
5.2 Conflict Resolution            
Any major problems will be resolved by an admin vote. Admins can choose not to vote if they so please. In the hopes of keeping things moving, all open votes have a 24 hour window in which admins can place their vote. There may, however, be exceptions to this 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 Sportsmanship            
Any player using racial slurs or insulting remarks toward another team or player while in an official match will be removed from the match. Any repeated offenses will result in the player being removed from the player list for the current season.

Please be nice and thoughtful to your fellow league teams and players. We are all in this for fun and competitive play, being a better player does NOT give you the right to belittle others.
Moderated By: MLIG ZP IX Admins