MK8DX 150cc Lounge Official Ruleset

Joining the Lounge
1. Upon joining the server, users send their MKCentral Registry account in the #mkcentral-links channel in our Discord Server. For help doing this, refer to this guide.
2. If you would like a specific nickname for the scoreboard and Discord server, you can ask for that too. If you already have a rank and would like to change your name, you can request nickname changes in #name-change-request. Players can change their lounge nickname once every 60 days; nicknames cannot be reverted during the 60 day period between changes.
  1. Nicknames may only contain letters (at least one), numbers, spaces, periods/full stops, hyphens or underscores.
  2. They must start and end with only letters or numbers, and must be between 2-16 characters.
  3. They also may not contain any vulgar language or impersonate another MKC user.
  4. In most cases, if your name can be used as a Twitter username, you can use it in lounge.
  5. Exceptions may be granted on a case-by-case basis.
3. Making an alternate account to join lounge will result in a heavy penalty in lounge and MKCentral.
  MKCentral Staff will find out if an alternate account is made, so it's highly recommended to not do so.
Ranking System
1. Once a staff member has seen your account, you will be placed into one of the following ranks:
  - Iron 1: 0-999 MMR
  - Iron 2: 1000-1999 MMR (Placement: 1500)
  - Bronze 1: 2000-2999 MMR (Placement: 2500)
  - Bronze 2: 3000-3999 MMR (Placement: 3500)
  - Silver 1: 4000-4999 MMR (Placement: 4500)
  - Silver 2: 5000-5999 MMR
  - Gold 1: 6000-6999 MMR
  - Gold 2: 7000-7999 MMR
  - Platinum 1: 8000-8999 MMR
  - Platinum 2: 9000-9999 MMR
  - Sapphire 1: 10000-10999 MMR
  - Sapphire 2: 11000-11999 MMR
  - Ruby 1: 12000-12999 MMR
  - Ruby 2: 13000-13999 MMR
  - Diamond 1: 14000-14999 MMR
  - Diamond 2: 15000-15999 MMR
  - Master: 16000-16999 MMR
  - Grandmaster: 17000+ MMR
2. If you are unhappy with your placement or feel that you should've been placed higher or lower, then prove it by playing matches. The system will correct itself quite quickly if you deserve a higher/lower grouping. If you have been inactive for at least 6 months, staff will consider a placement change.
3. Depending on your rank, you will see 1-2 channels that you can play matches in, listed below:
  - Tier G: Iron 1 + Iron 2 + Placement
  - Tier FG: Iron 2 + Bronze 1
  - Tier F: Bronze 1 + Bronze 2
  - Tier EF: Bronze 2 + Silver 1
  - Tier E: Silver 1 + Silver 2
  - Tier DE: Silver 2 + Gold 1
  - Tier D: Gold 1 + Gold 2
  - Tier CD: Gold 2 + Platinum 1
  - Tier C: Platinum 1 + Platinum 2
  - Tier BC: Platinum 2 + Sapphire 1
  - Tier B: Sapphire 1 + Sapphire 2
  - Tier AB: Sapphire 2 + Ruby 1
  - Tier A: Ruby 1+
  - Tier S: Ruby 2+
  - Tier X: Diamond 1+
Gathering Lineups (Lounge Queue)
1. In the #queue-join channel, players can type /c to queue into matches for each hour. Between :55 and :58 at each hour, the queue will close and rooms will be created in order of MMR.
  1. If a multiple of 12 players cannot be reached by the queue closing time, the last players to queue will be removed.
2. Once rooms have been created, players can click on buttons in their room threads to vote for a format. Clicking the button for the format you have voted for will undo your vote. Format votes are anonymous.
  1. Players who drop for any reason after the poll has been started will receive a -100 MMR strike.
  2. If the event is an FFA, only a host will be needed and the event can start immediately.
  3. If the event is a 2v2, 3v3, or a 4v4 mogi, teams will be randomized.
  4. Once teams are randomized, they are final and cannot be changed. Players who violate this rule will receive -50 MMR and a strike.
3. In the event that a sub is needed, players can use the /sub command to have the bot search for a sub in #queue-subs.
  1. Players can sub into a room if their MMR is within 500 of the lowest player or 500 of the highest player of that room.
4. If a sub cannot be found 20 minutes after the scheduled start time, an event may be canceled with no penalty to the remaining players.
5. If staff intervention is needed in a Lounge Queue room, players can use the !staff command.
Gathering Lineups (Tier System)
1. Using MogiBot, the first twelve players to say /c will play. Any players later than 12th on the list will be subs, given priority by their order on the list. If a player is unable to sub when needed or does not respond within 5 minutes, they will receive a -50 penalty and a strike.
2. The next player in the MogiBot lineup will always have priority when subbing into an event; if a different player subs in when the next player in the MogiBot lineup is able to play, they will receive -50 MMR and a strike.
3. Players cannot /d for 15 seconds after typing /c. A /c will automatically expire after 20 minutes have passed. A list of players can be found using /l.
4. Players are not allowed to type /c in a tier they are currently playing in until they have crossed the finish line at the end of the 12th race. For example, players are not allowed to queue up for a Tier D match while currently playing in one. Players who violate this rule will receive -50 MMR and a strike.
  1. Players are allowed to type /c in a different tier than the one they are currently playing in. For example, players are allowed to queue up for a Tier CD match while currently playing in a Tier D match. Nonetheless, players are still subject to penalties if they fail to join in time (rule V. a., V. b., V. c.).
  2. Players who leave an event before it finishes are not allowed to join a mogi until the event they left finishes the 12th race. Players who violate this rule will receive -50 MMR and a strike.
  3. These rules do not apply in the hourly Lounge Queue format; players may queue up for their next match immediately and do not have to wait for their current matches to finish.
5. After 8 races have passed in the current mogi, users not currently playing are allowed to start a new mogi.
6. Once lineups are gained, MogiBot voting will be used to decide on the format. The first twelve players who originally said can are allowed to vote. Anyone who is not part of the original 12 in the line-up is not permitted to vote.
  1. Players who drop for any reason after the poll has been started will receive a -100 MMR strike.
  2. If the event is an FFA, only a host will be needed and the event can start immediately.
  3. If the event is a 2v2, 3v3, or a 4v4 mogi, teams will be randomized.
  4. Once teams are randomized, they are final and cannot be changed. Players who violate this rule will receive -50 MMR and a strike.
7. If your rank role changes during a mogi and you are unable to see the chat of the mogi you are participating in, you can temporarily grant your old rank role to yourself in #temprole-requests. Players who abuse the temprole system in any way will receive -50 MMR and a strike.
Host
1. Players can queue as a host using the /ch command in MogiBot; if no host is chosen automatically after the format is decided, players can volunteer as a host by posting room ID or using the ^fc command in StatsBot. If the player is randomly chosen to be a host, they must post the room ID or their friend code within 2 minutes of the poll ending unless they have entered the room ID into MogiBot in advance. Failure to post the room ID or the friend code or refusal to host will result in 1 strike.
  1. Players who are hostbanned or chat restricted are not allowed to host an event.
  2. Players who violate i. will receive a 3-day mute.
  3. Please post the room ID in uppercase letters. Failure to do so may be subject to a hostban penalty if confusion arises when entering or leaving the room.
  4. If you are livestreaming your lounge matches, it is recommended to hide the Room ID in some way when it is visible on the screen to prevent random players from joining.
  5. If a random player joins the room and the room has to be restarted, it is recommended to switch to hosting the room through a friend code only. If a random player can be identified as a player in the Lounge, please make a report ticket in #reports.
2. If the room is being hosted with a friend code, the host must wait 2 minutes after posting their friend code to accept friend requests before opening the room. If the room is opened early, the late penalty (V. b.) comes into effect after 7 minutes of the friend code being posted. Should players request the room to be reopened if opened early, the host must do so or else receive 1 strike.
3. In the event of a room closure after the first race, hosts have to wait 5 minutes after they reopen; after 5 minutes, the host can start the mogi even if there aren't 12 players in the room.
4. If there is no host for a mogi 10 minutes after the poll ends, the entire lineup will receive -50 and a strike excluding hostbanned and chat restricted players.
5. In the event that a player disconnects before the first race of a mogi starts (by the end of Lakitu Countdown), the room must be restarted regardless of video proof submissions. This rule only applies once, if a player disconnects before the mogi a second time the room should continue without closing. A player should provide video proof (switch clip, stream, error history etc.) of their disconnection if requested; otherwise they will receive -50MMR and a strike. If the host does not restart, the first race will not count and an additional 13th race will need to be played at the end.
6. Hosts should start the room with the following settings:
  - Class: 150cc
  - Teams: No Teams
  - Items: Normal Items
  - COM: Hard COM
  - COM Vehicles: All Vehicles
  - Race Count: 12 Races
  Hosts who do not comply with the above race settings may have the corresponding races declared invalid and may be subject to a Hostban penalty.
7. Hosts that start the room with less than 12 players, close the room for no reason, or otherwise cause unnecessary disruptions will receive -50 and a strike, and may be prohibited from hosting in the future. If hosts disconnected in the middle of a mogi, hosts must take a 30-second clip to prove that it was unintentional (streaming archive is also allowed). Typing ^hostban in any channel will show the list of host-banned players.
  1. Host-banned players must wait at least 90 days before appealing their hostban.
8. Room hosts are responsible for taking screenshots of results. If the host failing to take screenshots prevents a table from being made, the host will receive -100MMR and a strike.
Match Rules
1. Once a room has been opened, players will have 5 minutes to join the room, unless the room is opened early (refer to rule IV. c.) or before the scheduled time in Lounge Queue events. For example, if the host posts their friend code at 9:00 and opens the room at 9:02, players are considered late at 9:08. If a room ID is posted in a Lounge Queue room at 8:57, the late penalty will be at 9:06.
2. Players that join the room late will receive a -50 MMR strike.
3. If a player still has not joined the room 5 minutes after the penalty time, they will receive -100 and a strike and must be replaced by a sub as soon as possible. The mogi should not be started with less than 12 players under any condition.
  1. If a lineup is struggling to find a sub, please tag Lounge Staff to tag @here for a sub.
4. Players who sub in a match that has already started:
  1. Do not lose MMR on a losing team.
  2. Only gain MMR on the winning team if they play 4 or more races in said event.
  3. A match has started once the first race has been completed, with the race results being shown. Players that sub in before the first race will be given normal MMR gains or losses.
5. Players who repick a course will receive a -50 MMR penalty. This does not include repicks from random track selection. Players who repick a course at least twice will receive a -50 MMR penalty for each instance and a strike (e.g. repicking twice results in -100 MMR + strike, repicking three times results in -150 MMR + strike). This penalty applies even if you sub, so be sure to ask the other players in your match which courses have been played, or pick Random on the track select screen.
  1. If the player who reported the repick files an objection and no video or other evidence can be confirmed, the penalty may be revoked. However, in that case we may check the facts with the reporter and other players who participated in the mogi.
  2. In Squad Queue 6v6 matches, repicking a course will also result in a -20 penalty to the team's score (subtracted from the offending player's score).
6. Players must use their Lounge Nickname (or a shortened, legible version if the shortened version is more than 10 characters) in FFA format events. Japanese characters are not allowed.
  1. Shortened names must be at least 3 characters long.
  2. Players must not add any characters that are not in their lounge name, including replacing characters with visually similar ones of a different language.
  3. FFA names must be distinguishable from players who may have similar names in the same mogi.
  4. Failure to abide by any of these naming guidelines after the first 2 races will result in -50 MMR.
7. In team matches, players must decide on a tag to use in their name with their teammates. Tags must adhere to the following guidelines:
  1. Tags must either all be placed at the beginning of players' names or all at the end of players' names. For example, the following is allowed:
    - A★Cynda, A★DUGO
    - Cynda★A, DUGO★A
    and the following is not allowed:
    - A★Cynda, DUGO★A
    - tmAn, mArio
    - A★Cynda, a★DUGO
    - CyndaXX, DUGOXX
  2. Two teams may not use tags which begin with the same character (uppercase and lowercase of the same letters counts as the same character) and two teams may not use hiragana and katakana tags of the same sound (e.g. あ★Cynda, ア★DUGO); the team which declares their tag first in the chat will have priority regarding this rule.
  3. Players must arrange uppercase/lowercase and hiragana/katakana tags with their teammates.
  4. Symbols that look similar to letters or numbers are classed as the same and cannot be used if another team has claimed it.
  5. Tags at the end of the name must be separated from the rest of the name with a separator such as a space or symbol.
  6. Player names must not begin with the first character of another team's tag.
  7. If not stated otherwise, the tag should start at the beginning of the name by default with regard to (i.)
  Failure to use same tags in the same team or abide by any of these naming guidelines after the first 2 races will result in a -50 MMR penalty.
8. Players that drop from an event before it starts will receive -100 MMR and a strike by default. If a player drops after the first race has been completed, they will receive a -50 MMR strike and receive an MMR penalty according to rule V. i. Players who drop from an event are ineligible for MMR gain from that mogi even if their team wins.
9. Teams missing a player (including because of disconnections) 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 6 races will receive 6/12 loss, or 0/12 loss if the teammate misses 12 races. The player who missed at least 4 races will receive a strike.
  1. If a player drops after the first race, their partner participating in the mogi can choose whether or not to find a sub for the dropped player.
10. If any player is disqualified from an event for any reason such as, but not limited to, throwing, teaming, or lap-trolling (on any track except Baby Park, in formats other than 6v6 SQ), they will receive a -100 MMR strike.
11. Players may not use an in-game name or Mii that is offensive, abusive towards others, contains inappropriate language, or violates any laws. Use of any offensive names or Miis will result in a warning or mute depending on the severity of the name, as well as possible punishment by MKCentral Staff.
Disconnections and Lag
1. If 3 or more players from at least 2 different teams disconnect or experience delayed items (only coins or shrooms) in at least two different item sets during a race, the race will not count and the room must be reopened regardless of video proof submissions. Players should provide video proof (switch clip, stream, error history etc.) of their disconnection if requested; otherwise they will receive -50 MMR and a strike.
2. If a race does not finish due to lag, the race will not be counted and the room will be reopened.
3. If no races can be finished for an extended amount of time due to lag, the event can be canceled with no players losing MMR.
4. If this happens to occur during an event, please attempt to capture video proof of the individual who may be causing the lag in the room. If the proof is convincing, and if the majority of the room agrees on who is causing the lag, staff have the right to punish the individual for a certain amount of time, or warn them to fix their connection before playing again.
5. If a player cannot rejoin the room due to an error (such as connection incompatibility with another player in the room), the player can call for the room to be reopened one time. All races which have started (when Lakitu's countdown has finished) prior to the player asking for a reopen will still count. Players should be able to provide proof of their issues if requested; failure to provide proof will result in -50 MMR and a strike.
Strike System
1. Players who receive MMR penalties for quitting matches, lap-trolling, joining the room late, targeting specific players or teaming will also receive a strike. Strikes expire after 30 days. Players have a limit of 3 strikes.
2. Players who reach 3 strikes will receive the following punishments:
  1. 1st offense: 7 day mute
  2. 2nd offense: 14 day mute
  3. 3rd offense: 28 day mute
3. Strike limits are reset each season.
Conduct
1. Players who consistently cause disruptions in the server such as trolling, flaming, spamming bot commands, etc. will either receive a chat restriction (only allowing them to send certain messages), a mute, or a temporary timeout via staff discretion.
2. Players who consistently cause disruptions in matches such as trolling, targeting specific players, inting etc. will receive a 3-day mute, and may receive increased punishment on repeated instances.
  1. Targeting is defined as disrupting the race of another player through excessive item use whereby their race is significantly/negatively impacted by score or placement; and/or the player targeting impacts their own race in a similar manner.
  2. Making a claim: If you believe someone is targeting, please take multiple videos as evidence and report them using the ticket system. Videos can be from switch clips, MKTV, streams with timestamps, etc.
  3. Some examples of targeting: slowing to red the same player, slowing to star the same player, spamming items at the same player excessively, and so on.
  4. Note: We encourage you to consider different play styles players may have, lag/genuine mistakes, and how close your mogi is in terms of points before submitting your claim.
3. Any NSFW content in the server will be promptly deleted and the user that posts it will receive an indefinite chat restriction.
4. Players who are banned from MKCentral may face similar consequences in Lounge depending on the severity of the ban. Detailed information about MKC bans and Lounge can be found here.
Results
1. An online war table generator can be found here:
  https://hlorenzi.github.io/mk8d_ocr/table.html
2. In order for a match to be counted, using a war table with all the correct player names (Server nicknames, not Mii Names) is required. Any penalties that occurred during the match must also be stated.
3. Only certain people will be given access to the results channels in order to prevent spam. If you want to become reporter, please check the #self-roles channel.
4. Tables must be submitted using the MK8DX bot in the Lounge server. For more info on how to use this bot, click here.
Squad Queue
1. Squad Queue is a different way of playing lounge that allows players to play with predetermined teammates. For more information about Squad Queue, click here.
2. If a player fails to show up for a match, misses at least half of an event, or trolls during an event (V. j.) they will receive the SQ Restricted role for 1 week. This role is essentially a ban from SQ for the duration that the player has the role.
  1. If a team can find a sub for a missing player before the late penalty time, the missing player will not receive the SQ restricted role.
3. Subs are allowed in Squad Queue events; however, the sub's MMR must follow at least one of these conditions:
  1. The team would still be in the same room with the sub's MMR taken into account.
  2. The sub's MMR is within 1000 MMR of the original player.
  3. In the case that a team violates either of the above conditions, any MMR they win from the event will be voided and also receive SQ Restricted.
4. If the host has been decided after opening time, the host has to wait 2 minutes to open the room. Players need to be in the room in 5 minutes. (except rule IV. b.). After 10 minutes, the host can start Mogi even if there are not 12 players in the room.
Other Notes
1. Please read the "Ticket Guidelines" section of the support/reports channels before creating a support/report ticket.
2. Chat Restricted, Mute, and Hostban roles are for punishments only and are not available upon request.
3. There is a possibility that penalties may be more severe at the discretion of Lounge Staff, based on severity and history of behavior.
4. Lounge Staff will make decisions in the event of unexpected circumstances not listed here.
5. Players who have received sanctions for an indefinite period of time must wait at least 90 days before appealing their punishment, excluding players who are indefinitely Chat Restricted or Muted because of an indefinite MKCentral ban.