MKTour Lounge Season 12 Launch Notes

[GoHuFlame]

MMR Reset

All players have been moved closer to the median. The algorithm for this reset, calculation was based on current MMR previous season, events played, matches won, winrate.

Rule Changes

II. NAMES

Removed:
A. ... Names can be changed ONCE during the current season. You can change back to your Registry name at any time, but you will still be unable to make further name change requests.

Previous:
A. ii. Every player is allowed to request nickname changes, but after one request they need to wait 90 days to request another name change. They may request to change back to their previous Registry name at any time though, but they will still be unable to make further name change requests for 90 days.

Updated:
A. ii . Every player is allowed to request nickname changes, but after one request they need to wait 2 months to request another name change. They may request to change back to their previous Registry name at any time though, but they will still be unable to make further name change requests for 2 months.

IV. GATHERING LINEUPS

Previous:
G. Once the host is decided, he must share the Room Code. The first person to share a code will be considered the host of the match.
i. All codes must be placed in the tier-codes channels.

Updated:
G. Once the host is decided, he must share the Room Code. The first person to share a code in the corresponding #room-code-channel will be considered the host of the match.
i. Codes cannot be deleted by the host, if this occurs the host will receive -50 MMR strike.
ii. The host should not take more than 5 minutes to open a room after a reopen, otherwise the host will receive a host flag.

Previous:
H. If there is no host for a mogi 15 minutes after the poll ends, the entire lineup will receive -50 MMR strike.

Updated:
H. If there is no host for a mogi 10 minutes after the poll ends, the entire lineup will receive -50 MMR strike.

V. MATCH RULES

Previous:
A. ii. Failure to start a room with the correct settings may result in an individual host flag.

Updated:
A. ii. Failure to start a room with the correct settings may result in an individual host flag. If mogi is cancelled for incorrect settings, host will recieve host ban and -50 MMR strike.

Added:
B. Hosts that start the room with less than 8 players, close the room for no reason, or otherwise cause unnecessary disruptions will receive -50 MMR strike, and may be prohibited from hosting in the future.
i. If a sub needs to join the mogi, the host must restart the room, even if a team has no DCs available.

Added:
E. i.
Ex.
Room Code: 01
No strike: minute :06
1st strike: minute :07 at minute :11
2nd strike: minute :12

Removed:
F. ii. In case that a player disconnects before the first race of a mogi starts, the room must be restarted. This rule only applies once, if a player disconnects before the first race a second time the room should continue without closing. A player should provide video proof (video clip, stream, etc.) of their disconnection if requested; otherwise they will receive 1 strike. If the host does not restart, the first race will not count.

Added:
F. ii. After 15 minutes have passed without the mogi having been started, it may be cancelled, once the Lounge Staff has been previously tagged.

Previous:
K. In FFA format events. In case the player leaves the event at the beginning and comes back to finish the mogi, they will receive a strike if missed at least 4 races.

Updated:
J. In FFA format events. In case the player leaves the event at the beginning and comes back to finish the mogi, they will receive a strike without MMR loss if they missed at least 3 races.

Previous:
L. Teams missing a player for at least 4 races will lose MMR proportional to the amount of races the player missed; for example, teammates of a player who missed 4 races will receive 8/12 loss, or 6/12 loss if the teammate misses 6 races. The player who missed at least 4 races will have their MMR loss increased proportional to the number of races missed; for example, a player who missed 4 races will receive 16/12 loss. Players who miss 6 races or more will also receive a strike.

Updated:
K. Teams missing a player for at least 3 races will lose MMR proportional to the amount of races the player missed; for example, teammates of a player who missed 3 races will receive 9/12 loss, or 6/12 loss if the teammate misses 6 races. The player who missed at least 3 races will have their MMR loss increased proportional to the number of races missed; for example, a player who missed 3 races will receive 15/12 loss.

Previous:
D. Players who have an incorrect tag for more than 2 races will receive a -25 MMR strike.

Updated:
N. Players who have an incorrect tag (2v2 & 4v4) or Lounge name (FFA) for more than 2 races will receive a -25 MMR strike.

V. DISCONNECTIONS AND LAG

Added:
E. iii. The CPU points will be distributed in the following way: the player disconnected that have more points in that race will receive the higher position points from the CPU bot.

Previous:
F. In FFA format events. Reopens in the first match is mandatory when a CPU appears. Players who disconnect twice in the first race will receive a strike without MMR loss though.

Updated:
F. In FFA format events. Reopens in the first match is mandatory when a CPU appears. Players who disconnect twice in the first race will receive 50 MMR strike.
i. If a player is disconnected three times, the player must be replaced for a sub. The player will not receive an additional strike for having a sub, but the previous penalty will be increased to -100 MMR strike.

VIII. CONDUCT

Added:
C. Players who consistently engage in toxic behavior will receive 3 days of mute, and may receive increased punishment on repeated instances.

Added:
E. Using, sending or reacting with racist emojis will receive 7 days of mute.

Added:
J. Additional prohibitions may be added, for which you should consult the ⁠#server-rules channel.

IX. RESULTS

Removed:
A. An online war table generator can be found here:
https://hlorenzi.github.io/mk8d_ocr/table.html

Added:
C. i. In case the race provides two different results to players, the screenshot valid is the one that host has. If host doesn’t have the screenshot, the race will not count. The host will receive a host flag in this case.

Added:
D. iv. Reporters who spam in results-channels will receive reporter banned role.
v. To report a late join strike, the reporter must attach a screenshot of the room for the missing player for easy verification. Reports without a screenshot will be analyzed by the Staff.

In addition to the changes mentioned above, the following changes have been made:

1. Correction of minor text errors.

2. Order of rules to have them in a clearer way.

3. Minor corrections that did not need to be detailed and that do not affect the previous rules.

Thank you.

- MKTC Lounge Staff