MLCTF FACTIONS
1
1.1 League Format

Major League Unreal Tournament Factoins, hereafter referred to as Factions, will be a season format and feature a single-elimination playoff round. There will be 9 teams organized into one division. Factions regular season will feature a six week schedule, with each team playing 1-2 matches per week, best two of three maps per match. Matches will be held on Sunday and Wednesday. The top 7 teams will advance to the playoffs, all teams being seeded together. For seeding purposes, in the event of a statistical tie, the team with the fewest map forfeits will be the higher seed. If both teams have an equal number of map forfeits, the team who recorded the least map losses will be the higher seed. Failing that, the team who won the head-to-head matchup will be the higher seed. If the teams in question have not played, the team with the higher efficiency [ PF / (PF + PA) ] will be the higher seed.

1.2 Season Standings

Factions regular season standings will be based on a points system as follows:

Win match 2-0: 3 points
Win match 2-1, 2 points
Lose match 2-1, 1 point
Lose match 0-2, 0 points
Forfeit match, -1 points

Team standings will be based on total points accumulated during the regular season.

1.3 Playoff Format

The playoffs will feature a single elimination bracket between the top eight teams. 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 seven teams will play as follows:

(1) 1st Place vs.
BYE

(2) 2nd Place vs.
(7) 7th Place

(3) 3rd Place vs.
(6) 6th Place

(4) 4th Place vs.
(5) 5th Place


2.1 Match Rules

Each round of the regular season will consist of a pool of three maps, preselected by the admin staff. The team with the lower overall salary (Team 1) will have first choice to select their map from the pool of three, then their opponent (Team 2) will select a map. The remaining map will serve as the tiebreaker, if needed.

Map List:

CTF-AreaN23-LE103
CTF-Azcanize-MLUT
CTF-Bleak-CE100
CTF-BollWerK105
CTF-CoretCE105
CTF-Cynosure][LE105
CTF-FaceLE200
CTF-Gataka-SE
CTF-Gauntlet
CTF-Glacier][-CE105
CTF-Infested-MLUT101
CTF-LavaGiant
CTF-Lucius(Undetermined Version)
CTF-McSwartzly][
CTF-NovemberCE105
CTF-Orbital-LE102
CTF-Ranel-JoltEdition
CTF-Revenge-LE102
CTF-Schmydro-MLUT103
CTF-Terra-LE102
CTF-Vaultcity-LE102

The map schedule will be as follows:

Week 1 - Bollwerk, Cynosure, Infested

Week 2 - Terra, Azcanize, Schmydro

Week 3 - Gauntlet, Orbital, AreaN

Week 4 - Glacier, Bleak, Coret

Week 5 - McSwartzly, Gataka, Vaultcity

Week 6 - LavaGiant, Revenge, Lucius

Week 7 - Face, NovemberCE, Ranel

Team 1's map pick will be played first, and Team 2 will have the choice of color and server. Team 2's map pick will be played second, and Team 1 will have the choice of color and server. For the tiebreaker, if needed, the team with the better cap spread will have the option of choosing whether they wish to select the server to be played on OR the color they wish to play. Whichever they choose, their opponent will have the choice of the other. If the cap spread is tied, the first choice will go to the team with the most overall player points (Points and/or frags that cannot be verified due to disconnects will not be counted). If they have equal overall points, the team designated as Team 1 will have the first choice. Team captains should meet together with an admin on irc no later than 30 minutes before matchtime to complete the map selection process. Team captains must give their server and color choices to the admin at that time. No changes may be made afterwards.


2.2 Playoff Rules

The quarter-final and semi-final rounds of the playoffs will be a best of three maps with each team choosing one map from the above maplist. A team may not choose the same map in both the quarter-final and semi-final matches. The higher seeded team's map selection will be played first on the lower seeded team's server. The final round of the playoffs will be a best of five maps with each team choosing two maps from the entire maplist. The higher seeded team's map selections will be played first and then third on the lower seeded team's server. Throughout the playoffs, tiebreakers will be decided in the following manner: both team captains will meet with an admin on IRC 30 minutes before match time. Each captain will take turns eliminating maps from the list of unplayed maps until one map remains. The higher seeded team will choose whether they want to eliminate a map second or have server OR color choice for the tiebreaker.

2.3 Match Scheduling

All matches are prescheduled by the Factions staff and times will be posted on the Factions website. If teams wish to reschedule their match, both captains must agree and inform an admin no less than 24 hours before the scheduled match start, otherwise the original date and time will be used. Teams are allowed ONE reschedule up to the day before the next round begins. 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 are enumerated under sections 2.3a through 2.3f.

Captains are required to meet with ad admin on irc to provide their server/map/color picks by thirty minutes before their schedule match time. Failure to do so will result in a forfeit. If neither team has their information at the deadline, Rule 2.3a goes into effect.

2.3a 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.3b 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) clicked members in the correct server, 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. The timer will start the countdown and continue counting only when all five (5) members are clicked and if one member reconnects during that countdown, the timer is paused until that member clicks again.

2.3c 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) clicked members in the correct server, 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. The timer will start the countdown and continue counting only when all five (5) members are clicked and if one member happens to reconnect during that countdown, the timer is paused until that member clicks again.

2.3d 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.3e 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 are clicked, Team B forfeits the map and Team A is awarded points for a map win.

2.3f Forfeit Loss - Excessive admin abuse

Including, but not limited to, Excessive pm's, teamspeak interactions and the like will not be tolerated. Admins are busy at match time and dont have time for explaining rules/arguing. Come prepared. Do not misplace your anger on the admins. Admins are chosen for their integrity and will be treated as such during match time under penalty of forfeit/removal from the league. All cases Will be reported and decision rendered. Check yourself before you wreck yourself. (and your team) Pug is pug, Dont bring it to matches. Play your match and it will be reviewed.

2.4 Connections

Factions 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. Also, any attempt to lag oneself, another player, or a server is strictly forbidden. Any players found to be in violation of this rule will be suspended from league play until further notice.

2.5 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.6 Servers


:: Bleach Factory - Chicago ::
unreal://68.232.183.167:7777?password=pug

:: The Nation of Domination - Chicago ::
unreal://69.28.220.106:7777?password=pug

:: TSM's Training Grounds - Chicago ::
unreal://68.232.176.48:7777?password=pug

:: The Saloon - Dallas ::
unreal://68.232.163.221:7777?password=pug

:: TempleServers.com - Georgia ::
unreal://72.5.86.40:7777?password=pug

:: Gotham City - New York ::
unreal://208.167.224.74:7777?password=pug

2.7 Server Settings

FWS off, Redeemer off

2.8 Ping Equity

Teams may choose any of the above servers for the maps where they have server selection. However, if SmartCTF shows an average ping difference between the teams greater than 20 ms, the admin may, at the request of the opposing team, enforce a server switch to a more equitable location. If the new location gives a better average ping difference, the match will proceed at that location.


2.9 Demos

Every player is required to demo every map. If you disconnect in the middle of a map and rejoin, it is your own responsibility to restart the demo. Each team may request 3 demo's per regular season from other players. Admin staff will follow up with the accused players and get them uploaded so that the accusers may investigate said demo's. All demos must be requested BEFORE the next map starts, not after the match is complete. You have 1 hour after the final map to request demo's from that particular map.

Punishment for not supplying a demo will be as follows for the REGULAR SEASON.

1st Offense: 1 game suspension. Player will be ineligible for all maps in the next match.
2nd Offense: Team forfeits the map in question
3rd Offense: Team forfeits the match in question
4th Offense: Player is removed from the league.

If a demo is requested in the playoffs and not supplied the map will ALWAYS be forfeited.

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) Assemble a competitive team from the list of available players. See 3.3.
c) Assign a co-captain. A co-captain must be assigned prior to the first match of the season otherwise a forfeit will be the punishment for every upcoming match until a co-captain is set.
d) Make team decisions, such as lineup, map, color and server choices.
e) Take SmartCTF screenshots of their matches and provide them to the admins.
f) Collect evidence and provide it to the MLUT admins when accusing another team of breaking the rules.
g) Idle in #mlut channel when on IRC in order to receive messages from admins.

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 five (5) or more players on a team agree to the removal of a captain, the captain will be removed from the league and possibly banned. 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. This is a game but take your team serious.

3.3 Player Salaries

All Factions players will be listed with a corresponding salary based on their compiled skill ranking as decided upon by the admin staff.

3.4 Team Creation/Salary Cap

Each team will consist of eight players. Captains may choose their teams from any players in the league with the following stipulations: Players will be organized into four tiers based on their assigned salaries. Captains will be restricted in the number of players from each tier they can acquire as follows:



Furthermore, while the teams will have no hard salary cap overall, a strict cap of $4100 will be enforced on each map of each match. The 5 players on a team must have an overall combined salary lower than this number. No exceptions will be made.

3.5 Trading

Trading players between teams in Factions will be moderated by admins only. Two captains wishing to make a trade should approach an admin to explain the situation. Captains are encouraged to protect their players and not take any trade offers lightly. Try to consider the integrity of the person offering the trade, whether the trade is fair and balanced to the rest of the teams in the league, and most of all, whether the trade actually helps your team's chances of winning the Factions Championship. Admins reserve the right to amend or deny any trades deemed inappropriate. Please note that all teams must have 8 players on their roster, so trading two players for one will be impossible. Once a team has been eliminated from playoff contention, they will be allowed no further trades and their roster will be locked (in order to prevent team dumping).

3.6 Free Agent Signings

Captains will have the ability to remove members from their team for good cause. If a captain wishes to remove a team member, he must go to a Factions admin and explain the situation. If the admin agrees that it is reasonable to remove this player from the team, the captain will have the ability to choose a substitute from the list of unsigned free agent players. The admin will have the right to revoke this choice if it is deemed detrimental to the league. The player removed from the team must petition an admin for instatement back on the free agent list.

3.7 Player Inactivity

If a player misses two consecutive matches, a team may contact an admin with an inactivity request. The player will be removed from the league and will not be placed back into the free agent pool, and possibly removed from the league. Captains are encouraged to exercise this option only as a last resort to resolving the issues with the player. All actions will be handled based on available evidence and league queries.

4 Game Rules

4.1a Cheats

All hacks, bots, radars, cheats and non-GUI (advanced preferences) controlled tweaks are illegal. This includes, but is not limited to, any kind of automated aiming bot, a trigger-bot, any form of radar, server-crashing bugs / tools, packet loss and latency inducing devices, external timers, HUD timers (besides the one PURE provides), and anything in that same vein or spirit, or any cheats/hacks/tweaks that causes a player to be kicked from the server (no ambient sounds/light boxes/no shadows/etc.). Please use your brain as this is a zero tolerance policy. Any violations will be reviewed and may result in a PERMANENT EXPULSION for the offending player from all MLUT related events and a forfeit loss of the match in question for the offending team. These rules are not finite and can be changed or modified at anytime to address any situation. Those caught by our cheat protection will be subject to punishment. The only allowable tweak is shortened death messages. Every other tweak is illegal for MLCTF. Lets be honest, in this day, if you cant run ut99, you shouldn't be in a Pro League.

In addition, players can be convicted of the above (with admin vote) 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.1b 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.1c Spectators

Should any players be caught spectating a match without the consent of an administrator, And not immedeatly leave if asked, they risk a possible suspension/forfeit from league play. (You are allowed to spectate pugs, not matches) Should they be a member of a team in play, the offending team will receive a forfeit loss for the map in question. Further actions will be reviewed.

4.1d Frog Jumps

Frog Jumps and/or Bunny Hops are illegal in MLCTF play. If a player executes a Frog Jump in a match, accidentally or otherwise, the player must immediately drop the flag and allow the other team to return it. If demo, admin or eyewitness broadcast evidence show that the player or team that Frog Jumped captured or continued to attempt to capture a flag after the violation, the map will result in a forfeit loss for that team. In the event that something is missed it will be put under review.

4.2 Server Admin

If a player logs into 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 another 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 being reported for G-line. (Done)

4.4 Aliasing

A player may not use multiple identities over the course of the season. The name a player uses must be identical to that tracked by the admins and the alias they signed up as. 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.

If a team wishes to alter their names as part of their tag or team 'theme', they may contact an admin to discuss a solution that is fun but still clearly shows who every player on the team is.

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 Piston Portal Camping

Piston portal camping is illegal. This includes sitting on either side of a portal with a charged piston and/or anything in the spirit of portal camping, such as but not limited to, repeatedly running through a portal with a charged piston. Any violations will result in a forfeit loss on the map in question for the offending team.

4.7 Game Bugs

Exploiting game bugs is illegal, such as, but not limited to, the armor bug, or any bugs which may allow you to translocate and retain the flag or teleport the flag across large distances (warp). Any violations will result in a forfeit loss of the map in question for the offending team.

4.8 Map Bugs

Exploiting map bugs is illegal, such as but not limited to, dropping flags into areas they are not supposed to. Through walls and/or doors and the Terra flag drop. Drops through visible openings such as but not limited to, those on McSwarztly and Orbital are legal, with the exception of the Terra flag drop. Any violations will result in a forfeit loss of the map in question for the offending team.

4.9 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. Issues will be handled on a case by case basis. If a player continues to spam taunt binds after one (1) admin warning, his team will forfeit the map and he will be denied permission to play for the rest of the match. If required, further actions will be discussed with said teams captain.

5. Administration

5.1 Administrative Powers

All Factions admins have the power to make any changes to information on the MLUT website. Please have patience for changes. Should a captain or player notice any mistakes, he should contact an admin. Should a captain, player or other admin feel that an admin is abusing their power, he or she may file a grievance with the head admin and a vote will be conducted regarding the topic.

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. In the event of a tie, the head admin will cast the deciding vote.

5.3 Availability

In the event that there is only one (1) available admin for any Factions event, said admin has the authority to resolve all conflicts within the scope of the rules. These actions will be reported to the admin staff. If deemed unethical or not to be handled within the scope of the rules will be put to an admin vote and a ruling will soon follow.

5.4 Asterisk (*)

The Factions admins reserve the right to alter any rule in any way at any time as they see fit if there is a passing majority admin vote. This is to protect the integrity of the tournament in case of a loophole or something being overlooked.
Moderated By: FACTIONS Admins

MLCTF FACTIONS Features