Rules
RHOD Rules:
League format:
The league will be performed in a single round-robin style (all teams in a division play every other team in the division). Matches are a best of 5, using the weekly drop tonnage order (see below).
All matches are played using the assault mode. If teams have difficulty in synching in assault mode, if both teams agree, the match may be played in conquest mode. However, no team should feel pressured to change.
Drops will be based on 12v12
780 700 540 620 860
Teams can be no more than 40 tons under the max tonnage.
NA Playoffs: The top 2 teams in each division will receive a playoff birth, as well as the other top 2 teams (in terms of points won). The tie-breaker is drop differential (drops won – drops lost). The playoffs are single elimination, with a random tonnage order for each round.
EU Playoffs: Since EU season 2 is one division of 10 teams, there will be no playoffs. The team with the highest points at the end of the season will be the winning team.
Match determination:
Winner of the match is the team that MWO declares as the victor (i.e., has the most mechs standing at the end of the match or wins on base capture). The winning team is the team that wins a the best of 5 series (e.g., 3 wins, 2 losses; 2 wins, 2 ties, 1 loss). If teams decide to play capture mode, then the winner is as declared by MWO (i.e. the team with mechs left standing, or that has captured the max number of points).
Match Restarts:
If a team has 1 or more mechs disconnect, or otherwise have a bug preventing reasonable play in the first minute of play, and before a mech is destroyed, then it is re-dropped.
Rosters:
Teams may only use players that are on their roster, and are eligible for that week's match (e.g. if the person is added prior to week 3, the person may not be used for a week 2 match, but could be used for a week 3 match).Teams are responsible for ensuring that the player's name used in the MWO Mercs game is on the roster (minor differences, such as abbreviations are okay).
Teams that use ineligible players (e.g., players not on their roster), will forfeit those drops in which the players were used.
Player Roster Changes:
Once a person is registered to a team, the person can only change teams once during a season. If a player participated with one team during a week's match, and the person joins another team, the person cannot play for that other team during the same scheduled week's match.
(Note: Players are allowed to play on separate teams within the NA and EU leagues, and changes by the player in one league, do not count against changes in the other league.)
Roster Unlock Schedule
Teams may add a player to their roster up to 24 hours prior to a scheduled match. Roster lockdown will be at the start of the 2nd to last week of the season. At that time, no further roster changes will be allowed.
Changes in rules
Additional rules may be implemented to clarify and address issues. Further, rules and league format may change due to subsequent patches and changes in game, including, but not limited to, changes in matchmaking, and game modes.
Match Scheduling
Matches are to be scheduled and played during the assigned week. Teams have a one week grace period to complete the match. If an extension is needed, both team captains should message the league officials for permission. Failure to schedule and play any event match by the deadline day could result in forfeit losses for both teams.
Team Captains (or other team official) are required to contact their opponent through the RHOD forums prior to the match deadline date to establish the match time. While communicating via other third party applications (IRC, Skype, STEAM, etc.) is a commonplace, RHOD will only accept communication logs from the RHOD forums. Any team having trouble scheduling a match within these guidelines needs to contact an Official immediately for assistance.
Teams must be prepared for situations where all required drops are not able to be played during the same night due to the matchmaking system. Teams should plan accordingly, and it is recommended that teams set a backup date as a part of the scheduling negotiations.
Match Scheduling After the Deadline Day
Teams are NOT allowed to schedule or play their matches after the match deadline day (which includes the one week grace period) without explicit permission from the an Official. Teams that require an extension to their match deadline day, should contact the referees. Permissions are given by on a per-case basis
Teams have fifteen (15) minutes after the agreed upon (or default) time to be readied up and ready to launch (as well as between each round). A team failing to comply will be subject to penalty. Forcing a team to wait for players is disrespectful and unsportsmanlike.
Sportsmanship
Members must meet MWO's Terms of Use & Code of Conduct. See: mwomercs.com/terms and mwomercs.com/conduct Teams may not disconnect purposefully within the first minute of play (e.g. to force a map change, to restart a game if they feel they've made a mistake, etc.). A team that does so, may lead to forfeiture of games, or removal from the league.
Modification of game files:
Changes permitted--
Draw distance: (e.g. e_MaxViewDistance = 1990)
e_MaxViewDistSpecLerp = 1
]e_ViewDistRatioCustom = 100)
Time to zoom: (e.g. gp_mech_view_zoom_transitiontime = 0.05)
Keybindings
Field of View
Mouse sensitivity, smooth, accel
Changes not permitted--
Removing trees
Changing thermal or night vision settings
Removal of film grain
Enhanced zoom fidelity (i.e. clarity)
Aimbots
Recommended Procedure:
Have both group leaders on the same voice communications server, and have someone who is not a group leader count down for launch (example, "Three, two, one, DROP"). On the word "DROP"; both group leaders hit launch.
Confirm in All Chat (or voice coms) that you are facing the correct opposing team.
When the counter ticks down, the game is live.
If a team loses one or more players to disconnection within the first minute of play, and before a mech is destroyed, call a TIME in All Chat and report the situation to your opponent. This drop will not count, and will need to be re-dropped.
If there are disconnects during the live match, that is unfortunate. The match will still count.
Teams will report the results using the match reporting function in the league module.
In the case of a re-drop, teams may change their drop-dec, but may not take more than 5 minutes to do so. (Note: This is to help address two issues. 1) A team uses a drop dec that they feel works best if the other team doesn't know what they are taking.If a team was forced to use the same drop-dec the team might be at a disadvantage. 2) A team player's mech is locked in, so they want to swap to a different mech).
Forfeiting drops:
Drops may be forfeited for the following reasons
Using an ineligible player
Showing up more than 15 minutes late to the agreed time
Taking more than 15 minutes in-between drops
FAQ:
Q: Does a team have to field the same 12 people every drop?
A: No, feel free to rotate any pilots on your roster into the drops.
Q: I played in the Euro League, can I also play on my team in the US league?
A: Yes.
Q: Can I stream my matches?
A: Yes, but best practice is to confirm with your opponent if they are okay with you streaming.
Q: Is there a max size to a roster?
A: No
Drop Tonnage:
Drop tonnage orders:
Week 1:
780
700
540
620
860
Week 2:
700
540
620
860
780
Week 3:
540
620
860
780
700
Week 4:
620
860
780
700
540
Week 5:
860
780
700
540
620
Week 6:
780
700
540
620
860
Week 7:
700
540
620
860
780
Week 8:
540
620
860
780
700
Week 9:
620
860
780
700
540
6
Как очень верно заметил там Dungeon_Keeper мы должны следовать духу, а не слову закона.
