1. Moderator Applications are open! Find out about this, along with a number of other updates, here.
    Dismiss Notice
  2. Are you a supporter that wants to change your forum name? Just ask an administrator or moderator with a sparkly name!
    Dismiss Notice
  3. Beto's been working hard updating the homepage, and has also made a new app for league results! Please check the announcement for more information.
    Dismiss Notice
  4. You can click here to download a zip file conaining WCL and PL standings/schedules. We will update the file once we've managed to gather (if possible) all the data about IL and MKL.
    Dismiss Notice

Important WL Ruleset Changelog

Discussion in 'Help, Information, & News' started by Kneekoe, Mar 25, 2015.

Thread Status:
Not open for further replies.
  1. me

    me Certified CX Member

    • MKBoards Supporter
    Joined:
    May 21, 2015
    Messages:
    556
    Team:
    Relapse
    Update

    Change: Modification of Rule H.3.

    Original: 3. If a player on the conditional participation list fails to follow either of the above rules, their points will be removed or they will receive a penalty of 150 points (greater of the two) and they will receive a strike from the Strike System.
    New: 3. If a player on the conditional participation list fails to follow either of the above rules, one of the following will happen (with them receiving a strike from the Strike System):
    3a. They will receive a penalty of 30 points for each race they participated in with incorrect conditional participation (up to 4 races/1 GP, then the penalty in 3b. will be given regardless even if the player has correct conditionals by race 5).
    3b. They will receive a penalty of 150 points (or their points will be removed if greater than 150) if they participated in the entire match with an incorrect conditional participation.

    Reason: The council added in H.3b. in case a player forgets to do their conditional participation for a race(s) and not the entire thing, during a match. For example, what happened over the weekend in the Quintessence vs Insurgence match where Lifeboat forgot to do his conditional participation for 1 race and received the full -150 penalty for that--this rule will prevent that for any future cases. A clan shouldn't be punished as severe as that for a mistake, so this rule prevents that and will also prevent any possible abuse.

    This change will go into effect as of September 28th, 2015 at 12:00 EDT.
     
    Harm and Futile like this.
  2. ~Maidvelia❤~

    ~Maidvelia❤~ Sometimes Looking Into The Past Helps Your Future

    • MKBoards Supporter
    • Founding Member
    Joined:
    Jul 26, 2013
    Messages:
    5,993
    Gender:
    Male
    Location:
    Warren, MI, USA
    Team:
    U★, GE
    Wiimmfi FC:
    4297-4674-3102
    Important Update

    Change: Modification of the entirety of Section J. ~ Suicide Bagging, Overlapping, & Trolling, section name change to Overlapping, Trolling, & Suicide Bagging

    J. Overlapping, Trolling, & Suicide Bagging

    1. The "Overlapping" rules are in effect by default. However, the home clan has the choice of changing it to "Trolling" rules if the opponent is notified of it before the room is opened for the first time. "Suicide Bagging" rules are only in effect if both clans mutually agree to it before the room is opened for the first time.
    2. Passing the line and then reversing is not considered being on the same lap as when you passed. For example, if you pass the line to get on lap 2 and then go behind the line, you are on lap 1.
    3. Overlapping
    3a. Players are not allowed to be overlapped by the 1st place position. Should this happen, they are given 5 seconds to move out of the way--not in the line of item boxes--of the racers (without affecting racers in the process) and then completely stop and not use any items for the entire rest of therace.
    3b. If a racer takes a shortcut (for example, the Grumble Volcano respawn) and overlaps a player due to that, the overlapped player must immediately abide by what is stated in rule J.3a.
    3c. If a player is overlapped while under the effects of an item used prior to being overlapped, a penalty will not be given. However, they are not allowed to affect any racers with that item and must immediately abide by what is stated in rule J.3a.
    3d. Players are not allowed to affect any racers that have not overlapped them, but are in close range of it. For example, if you are close enough to 1st place that you can cause an item box to not respawn in time for them to get it, Bob-omb them, or Star them while almost being overlapped, that is not allowed.
    3e. If the “overlapping” rules are in effect and are broken, it will be penalized (-20 points) for every incident should solid proof be presented.
    4. Trolling
    4a. Neither “suicide bagging” or “overlapping” rules are in effect. Everything is allowed without being penalized.
    5. Suicide Bagging (a.k.a. NO Trolling)
    5a. A player is not allowed to be half a lap or greater behind the current 1st place position and interfere with an opponent. This includes hitting with an item (excluded items: Blooper, Lightning, and POW), hitting an in-game object, taking an item box, and all forms of bumping. A racer is not allowed to intentionally get him/herself trolled.
    5b. If the “suicide bagging” rules are in effect and are broken, it will be penalized (-20 points) for every incident.
    5c. All “suicide bagging” penalties are at council and division admin discretion. Choosing to play with this ruleset subjects you to the final rulings of the staff.

    Reason: Please refer to this thread for a detailed explanation on why we changed this section of the rules to what is shown above.
     
    xJownage likes this.
  3. me

    me Certified CX Member

    • MKBoards Supporter
    Joined:
    May 21, 2015
    Messages:
    556
    Team:
    Relapse
    Section D will most likely be edited slightly before 11:59pm tonight (EDT). General Rule #9 will not be in effect for this. If nothing happens by then, the section stays as is and this message is to be voided.
     
  4. me

    me Certified CX Member

    • MKBoards Supporter
    Joined:
    May 21, 2015
    Messages:
    556
    Team:
    Relapse
    Update

    Change: Modification of Section D.

    New:
    D. Game Modifications

    1. No game modifications are allowed (unless otherwise stated in D.1a. or D.1b.).
    1a. For disc users (CTGP-R), the following must always be set to “OFF” or “NO” - Remove Game Music?, ‘My Stuff’ Folder, Mii Heads on Minimap, Special Fonts, Draggable Blue Shells, Speedometer; for hosts of the room, they must have the following settings - Track Availability = Nintendo Tracks, Specific Engine Class = Normal, Race Count = 4, Thundercloud Autofire = Normal, Thundercloud Effect = Normal, Room Encryption = OFF, Available Vehicles = All Vehicles, Host Always Wins Vote = OFF.
    1b. For ISO users, the only modification that is allowed is for the sole purpose of connecting to Wiimmfi.
    2. If any of the above rules are broken, the player's clan will receive a penalty of 150 points or have their points removed for the match (the greater of the two).

    Original:
    D. Game Modifications

    1. No modifications are allowed except those that are for the sole purpose of connecting to Wiimmfi or performing Confirmed Conditional Participation.
    2. If the above rule is found to be broken, the player's team will receive a 150 point penalty or have their points not count for the match (whatever is greater).

    Reason: With the newest update to the CTGP Revolution Channel, this was a necessary update.
     
    ~Maidvelia❤~ likes this.
  5. ~Maidvelia❤~

    ~Maidvelia❤~ Sometimes Looking Into The Past Helps Your Future

    • MKBoards Supporter
    • Founding Member
    Joined:
    Jul 26, 2013
    Messages:
    5,993
    Gender:
    Male
    Location:
    Warren, MI, USA
    Team:
    U★, GE
    Wiimmfi FC:
    4297-4674-3102
    Update

    Change: Modification of General Rule 8.

    8. Players without an MKBoards account or a banned account will not be allowed to participate in the league. Exceptions can be made for rare circumstances.

    Reason:

    We've decided to make rare exceptions for this rule now. The MKBoards staff do not always make the right or timely enough decisions on bans and account activation (most of the time they do make the right decision however). Those banned unfairly in the CSL staff's eyes or have been ignored timely account activation should still be allowed to participate in the league.
     
    Last edited: Nov 4, 2015
  6. ~Maidvelia❤~

    ~Maidvelia❤~ Sometimes Looking Into The Past Helps Your Future

    • MKBoards Supporter
    • Founding Member
    Joined:
    Jul 26, 2013
    Messages:
    5,993
    Gender:
    Male
    Location:
    Warren, MI, USA
    Team:
    U★, GE
    Wiimmfi FC:
    4297-4674-3102
    Update

    Change: Reversion of General Rule 8.

    8. Players without an MKBoards account or a banned account will not be allowed to participate in the league.

    Reason: We do not want anyone to believe we are picking favorites (when in reality we really weren't but whatever). That is a horrible impression to give off and a shitstorm is more than likely if people continue to have that perception. In addition, even though the MKBoards staff can make some questionable decisions, they usually own up to their mistakes and a majority of the time their decisions are the right ones anyway. The council have taken a vote to whether this rule would be reverted or removed completely, and reverted won.
     
  7. ~Maidvelia❤~

    ~Maidvelia❤~ Sometimes Looking Into The Past Helps Your Future

    • MKBoards Supporter
    • Founding Member
    Joined:
    Jul 26, 2013
    Messages:
    5,993
    Gender:
    Male
    Location:
    Warren, MI, USA
    Team:
    U★, GE
    Wiimmfi FC:
    4297-4674-3102
    Update

    Change: Modification of Rule B.8.

    8. Picking a Custom Track in CTGP-R if the host has Track Availability set to "All Tracks" will result in a penalty of 30 points and require a restart of the room (the entire room will freeze for everyone who is not running CTGP-R's Custom Tracks). The clan whose player had their Custom Track pick selected will use one of their resets in this instance (see rule B.4. for more information).

    Reason: With the latest CTGP-R updates, picking a Custom Track is not as much of an accident since the removal of the random glitch, so now a penalty should be given for it.

    --------------------------------------------------------------------

    Change:
    Modification of the entirety of Section D. ~ Game Modifications.

    D. Game Modifications

    1. No game modifications are allowed (unless otherwise stated in D.1a. or D.1b.).
    1a. For disc users (CTGP-R), the following must always be set to “OFF” or “NO” - Remove Game Music?, ‘My Stuff’ Folder, Mii Heads on Minimap, Draggable Blue Shells, Speedometer; for hosts of the room, they must have the following settings - Track Availability = Nintendo Tracks, Specific Engine Class = Normal, Race Count = 4, Thundercloud Autofire = Normal, Thundercloud Effect = Normal, Room Encryption = OFF (if people not on CTGP-R are present, otherwise it is fine to have it set to ON), Available Vehicles = All Vehicles, Host Always Wins Vote = OFF.
    1b. For ISO users, the only modification that is allowed is one for the sole purpose of connecting to Wiimm-Fi.
    2. If any of the rules for disc users are broken, the player's clan will receive a penalty based on how severely the game modification may have affected the match.
    2a. If any player is caught using any type of game modification from the ‘My Stuff’ folder, dragging a Blue Shell, or having Remove Game Music? set to "ON", their clan will receive a penalty of 150 points or the points that player scored (whatever is greater).
    2b. If any player is caught using Mii Heads on Minimap or Speedometer, they will receive a penalty of 5 points per race (60 points total if left on for the entire match) until those are turned off.
    2c. If a host is caught with Thundercloud Autofire set to "OFF", Thundercloud Effect set to "Mega", or Host Always Wins Vote set to "ON", their clan will receive a penalty of 150 points.
    2d. If a host is caught with Track Availability set to "All Tracks" instead of "Nintendo Tracks", their clan will receive a penalty of 5 points per race (60 points total if left on for the entire match) until that is changed to Nintendo Tracks.
    2e. If a host is caught with Track Availability set to "Custom Tracks" instead of "Nintendo Tracks" or Vehicle Availability set to anything but "All Vehicles", they must close the room at the cost of one of their clan's resets (see rule B.4. for more information). If there is proof that the host refused to reset, their clan will receive a penalty of 150 points.
    2f. If a host is caught with Specific Engine Class set to anything but "Normal", they will receive a penalty of 50 points per GP (150 points total if left on for the entire match) until the setting is changed. If any race of that GP is played with those settings, the whole GP will be penalized.
    2g. If a host is caught with Race Count set to above 4, they must close the room at any point before race 5 at the cost of one of their clan's resets (see rule B.4. for more information). If there is proof that the host refused to reset before race 5, their clan will receive a penalty of 30 points for each additional race played (up to 240 points in total penalties if 8 additional races are played).
    2h. If a host is caught with Race Count set to below 4, their clan will lose a reset (see rule B.4. for more information) each time a GP ends without 4 races being completed.
    2i. If a host is caught with Room Encryption set to "ON" and the room freezes, the host's clan will lose one of their resets (see rule B.4. for more information). If the room does not freeze, the war may proceed without any penalty.
    3. If any of the rules for ISO users are broken, the player’s clan will receive a penalty of 150 points or the points that player scored (whatever is greater).

    Reason: It was the staff's mistake to look at all game modification advantages or disruptions in the same light as cheating and give them the same penalty as cheating. In reality, different advantages are more severe than others and that cannot be ignored. In addition, each team that has received a -150 penalty for Section D violations will have their penalty lowered to a value from this new ruleset based on what rule was broken. Any penalty value changes that cause the result of a match to completely change (a team who won would now lose) will be allowed to replay the match for that week. We thought this would be the most fair way to handle these situations.
     
  8. ~Maidvelia❤~

    ~Maidvelia❤~ Sometimes Looking Into The Past Helps Your Future

    • MKBoards Supporter
    • Founding Member
    Joined:
    Jul 26, 2013
    Messages:
    5,993
    Gender:
    Male
    Location:
    Warren, MI, USA
    Team:
    U★, GE
    Wiimmfi FC:
    4297-4674-3102
    Update

    Major overhaul for season 6. Be sure to read the new ruleset carefully!

    Good luck to all teams this season~
     
    Barney likes this.
  9. ~Maidvelia❤~

    ~Maidvelia❤~ Sometimes Looking Into The Past Helps Your Future

    • MKBoards Supporter
    • Founding Member
    Joined:
    Jul 26, 2013
    Messages:
    5,993
    Gender:
    Male
    Location:
    Warren, MI, USA
    Team:
    U★, GE
    Wiimmfi FC:
    4297-4674-3102
    Important Update

    First update since the rule structure overhaul and it's kind of a biggie...

    Change: Addition of Rule III. e.i. and e.ii.

    e.i. When a player registers for or transfers to a team they must have permission from a representative of said team (unless they are already a representative of that team).
    e.ii. When a team representative transfers a player to their team they must have permission from said player. If a team representative is transferring said player out of their team or to a different branch of their team (ex: ¢β1 to ¢β2), they do not need permission.

    Reason: Please read this thread to see why we made this change.
     
  10. Nio

    Nio

    • Founding Member
    Joined:
    Jun 20, 2013
    Messages:
    569
    Update

    Change: Addition of Rule IV. g.

    g. All players must have at least 5000 VR on the license they chose to use for a match. If the first race of the in-game GP is completed with a player's VR not meeting this requirement, their team will receive a penalty of 30 points (90 point cap).

    Reason: VR lower than 4800/4500 can force the engine class to 100cc. Abusing this system should not be allowed, therefore we've established 5000 VR as the minimum requirement (the VR a player first receives when making a new license).
     
  11. Viraith

    Viraith WL Staff

    • Founding Member
    • WL Staff
    Joined:
    Aug 31, 2013
    Messages:
    3,590
    Update

    Change: Addition of Rule I. h.

    h. The scores of any match are final after 48 hours of the match's result thread being posted with the exception of cheating cases and improper conditionals.

    In effect for today's matches.
     
  12. ~Maidvelia❤~

    ~Maidvelia❤~ Sometimes Looking Into The Past Helps Your Future

    • MKBoards Supporter
    • Founding Member
    Joined:
    Jul 26, 2013
    Messages:
    5,993
    Gender:
    Male
    Location:
    Warren, MI, USA
    Team:
    U★, GE
    Wiimmfi FC:
    4297-4674-3102
    MASSIVE UPDATE

    Change: Modification of Rules I. f.-h.

    f. All teams will have a minimum of 2 and a maximum of 3 player representatives. These player representatives will be the only ones organizing their team’s matches throughout the league, no one else.
    g. All player representatives for each team will be added to a Skype chat made by the league admin(s) for their division. The league admin(s) and the division admin will oversee the chat. All match organization is to be taken place in the Skype chat.
    g.i. Any team who does not organize a match in their respective Skype chat runs the risk of the staff ruling any proof of rule(s) being broken as invalid.
    h. The scores of any match are final after 48 hours of the match's result thread being posted with the exception of cheating cases and improper conditionals.
    f. All teams will have 2 player representatives. These player representatives will be the only ones organizing their team’s matches throughout the league, no one else.
    g. All player representatives for each team will be added to a Discord channel made by the league admin(s) for their division. The league admin(s) and the division admin will oversee the channel. All match organization is to be taken place in the channel.
    g.i. Any team who does not organize a match in their respective Discord channel runs the risk of the staff ruling any proof of rule(s) being broken as invalid.
    h. The scores of any match are protected from any penalties/score changes 48 hours after the match's result thread is posted with the exception of cheating cases and improper conditionals.

    Reason: For I. f.-g.i. it was to reflect the move to Discord. Also we thought 3 player representatives isn't necessary, but we kept the minimum of 2 (so now the maximum and minimum is 2). For h., it was changed so that it is less vague.

    --------------------------------------------------------------------

    Change: Addition of Rule III. e.iv.

    e.iv. The council has the power to deny any player transferring down divisions if they deem the transfer in question to be inappropriate.

    Reason: To cover for cases similar to Lost in Time and Lost in Darkness that happened during season 5.

    --------------------------------------------------------------------

    Change: Addition of Rule IV. c.ii.

    c.ii. Should the away team want to use a reset, they must directly tell the hosting team to reset the room between the results of a race and the selection of the next track.

    Reason: The staff have decided it would be more beneficial for continuation to be the default instead of a reset for disconnections. Opposing teams that have a player disconnect must make a request to reset now.

    --------------------------------------------------------------------

    Change: Modification of Rule IV. d.

    d. Players may not use the following glitches:
    - Coconut Mall (both the ultra glitch and the downward spiral skip are banned)
    - Grumble Volcano (the lava respawn and rock-hop glitches are allowed)
    - Maple Treeway (both position and ultra glitch are banned)
    - Mario Circuit
    - Mushroom Gorge
    - Rainbow Road (the moon-jump at the beginning is allowed)
    - Wario's Gold Mine
    - GCN Peach Beach
    - GCN Waluigi Stadium
    - N64 DK's Jungle Parkway (both the ultra glitch and the spiral skip are banned)
    - N64 Sherbet Land
    d. Players may not use the following glitches:
    - Coconut Mall (both the ultra glitch and the downward spiral skip are banned)
    - Grumble Volcano (the lava respawn and rock-hop glitches are allowed)
    - Maple Treeway (both position and ultra glitch are banned)
    - Mario Circuit
    - Mushroom Gorge
    - Rainbow Road (both methods of the ultra glitch are banned, however the moon-jump at the beginning is allowed)
    - Wario's Gold Mine
    - GCN Peach Beach
    - GCN Waluigi Stadium
    - N64 DK's Jungle Parkway (both the ultra glitch and the spiral skip are banned)
    - N64 Sherbet Land

    Reason: To cover for the recently discovered second glitch on Rainbow Road by Estaloy.

    --------------------------------------------------------------------

    Change: Modification of Rule IV. e. and Addition of Rule IV. e.i.

    e. Any team that is responsible for picking a track that has already been played will receive a 20 point penalty (with the exception of a track selected via the normal track randomizer, NOT the CTGP randomizer).
    e. Any team that is responsible for picking a track that has already been played will receive a 20 point penalty (with the exception of a track selected via random, not including the CTGP randomizer).
    e.i. If a player provides video evidence that the CTGP randomizer was responsible for selecting a track that has already been played (without having a cup pre-selected), then no penalty will be given for the repick.

    Reason: Better wording (e.), and so that proven CTGP randomizer accidents no longer get penalized (since there is no reason for them not to be). It's an inconsistency too: random on regular tracks should be penalized too if we penalize for proven CTGP randoms (e.i.).

    --------------------------------------------------------------------

    Change: Modification of Rules VII. a. and b.

    a. Host must reset the room after each race someone disconnects in unless the team requesting the reset has already used their allowed amount of resets (see rule IV. c. for more information) or if there is a consent to continue.*
    b. Hosts must reset the room if there are less than 8 players [4vs4], 10 players [5vs5], or 12 players [6vs6] on the voting screen unless the team has already used their allowed amount of resets (see rule IV. c. for more information) or if there is consent to continue.*
    a. Hosts must reset the room after each race someone disconnects if requested, unless the team requesting the reset has already used their allowed amount of resets (see rule IV. c. for more information).*
    b. Hosts must reset the room if there are less than 8 players [4vs4], 10 players [5vs5], or 12 players [6vs6] on the voting screen if requested, unless the team has already used their allowed amount of resets (see rule IV. c. for more information).*

    Reason: To reflect the change to continuation by default for resets instead of disconnection, mentioned earlier above.

    --------------------------------------------------------------------

    Change: Modification of the entirety of Section X. ~ Conditional Participation

    X. Conditional Participation

    a. All disc users will be enrolled in the Confirmed Conditionals program. The list of players in the program can be found here:http://tinyurl.com/cslconditionals. Disc users have to use an eligible friend code and load through the CTGP Revolution channel with Custom Tracks set to ON.
    a.i. If a disc user plays a match with Custom Tracks set to ON (AKA using a white colored region line) without being enrolled in the Confirmed Conditionals program, the latest they may enroll for the program without receiving a penalty for that match is 48 hours after the results thread has been posted (they must also enroll using the same friend code they used in that match).
    b. If a disc user is unable to load through the CTGP Revolution Channel for whatever reason, they may stream their conditionals via Skype call to either a council member or one of the opposing team's members and load through the Wiimmfi Patcher (Homebrew Application). For the entire process, they must screen-share their full desktop screen and have their television visible via webcam or capture card. Going offline will require steps b.i.-b.iii. to be redone. The procedure is as follows:
    b.i. Power the Wii or Wii U on and load the homebrew channel.
    b.ii. Select the Wiimmfi Patcher Application and then select load.
    b.iii. Continue screen-sharing until you appear in the room.
    c. All ISO users will load via USB Loader GX. They must stream their conditionals via Skype call to either a council member or one of the opposing team's members. For the entire process, they must screen-share their full desktop screen and have their television visible via webcam or capture card. Going offline will require steps c.i.-c.vii. to be redone. The procedure is as follows:
    c.i. Power the Wii or Wii U on and load the latest version of USB Loader GX.
    c.ii. Select the game Mario Kart Wii.
    c.iii. Select settings and then Game Load.
    c.iv. Set the Ocarina option to ON, and then save it.
    c.v. Go back to the game screen and select Start.
    c.vi. The following message should appear: "sd:/codes/RMC___.gct does not exist! Loading game without cheats." Select Continue.
    c.vii. Continue screen-sharing until you appear in the room.
    d. If a player fails to follow either of the two procedures, one of the following penalties will be given:
    d.i. They will receive a penalty of 30 points for each race they play (up to 4 races/1 GP, then the penalty in c.ii. will be given regardless).
    d.ii. They will receive a penalty of 150 points or have all of their points deducted (whichever is greater).
    X. Conditional Participation

    a. Council has the power to place any players on the <CSL Conditionals List Link> should they deem it appropriate. These players are expected to abide by Conditional Participation rules from the instant that they are placed on said list, and continue to do so until they are removed.
    b. Disc users abiding by Conditional Particpation rules must screen-share their startup to either a council member or one of the opposing team's members and load through either the CTGP Revolution channel or the Wiimmfi Patcher. For the entire process, they must screen-share their full desktop screen and have their television visible via webcam or capture card. Disconnection from the room will require steps b.i.-b.iv. or b.v.-b.vii. to be redone. The procedures are as follows:
    CTGP Revolution Channel
    b.i.
    Power the Wii or Wii U on and load the CTGP Revolution Channel.
    b.ii. Select Settings, and assure that all settings comply with rule VI. a.i.
    b.iii. Exit Settings, and select Launch Game.
    b.iv. Continue screen-sharing until you appear in the room.
    Wiimmfi Patcher
    b.v.
    Power the Wii or Wii U on and load the Homebrew Channel.
    b.vi. Select the Wiimmfi Patcher Application and then select load.
    b.vii. Continue screen-sharing until you appear in the room.
    c. All ISO users abiding by Conditional Participation rules will load via USB Loader GX (any previously caught cheaters abiding by Conditional Participation rules may only complete their conditionals using one of the disc procedures). They must stream their conditionals via Skype call to either a council member or one of the opposing team's members. For the entire process, they must screen-share their full desktop screen and have their television visible via webcam or capture card. Disconnection from the room will require steps c.i.-c.vii. to be redone. The procedure is as follows:
    c.i. Power the Wii or Wii U on and load the latest version of USB Loader GX.
    c.ii. Select the game Mario Kart Wii.
    c.iii. Select settings and then Game Load.
    c.iv. Set the Ocarina option to ON, and then save it.
    c.v. Go back to the game screen and select Start.
    c.vi. The following message should appear: "sd:/codes/RMC_.gct does not exist! Loading game without cheats." Select Continue.
    c.vii. Continue screen-sharing until you appear in the room.
    d. If a player fails to follow either of the three procedures, one of the following penalties will be given:
    d.i. They will receive a penalty of 30 points for each race they play (up to 4 races/1 GP, then the penalty in d.ii. will be given regardless).
    d.ii. They will receive a penalty of 150 points or have all of their points deducted (whichever is greater).

    Reason: The previous season's procedure is now irrelevant due to 3 discoveries coming to light in the staff: a way to change region line color without deleting your save file, a way to replicate the exact coordinates of the CTGP-R region, and a way to Inject Gecko Code files directly into an ISO.

    In short, we will be removing Global Conditionals (GCs) until @MrBean35000vr can provide a My Stuff folder indicator and something that can check the hash of an ISO on the Wii/Wii U, instead of on a PC (otherwise GCs cannot be practical to implement). We will also be completely retiring Confirmed Conditionals (CCs), so the CTGP-R Channel will no longer be mandatory (disc users can now choose between the Wiimmfi Patcher and the CTGP-R Channel again as their preferred loader). If Mr. Bean manages to provide the aforementioned things, the new term will be No Startup Conditionals (NSCs).

    --------------------------------------------------------------------

    Change: Modification of Rules XII. a. and e.-e.viii.

    a. “Suicide Bagging” rules are in effect by default. However, the home team has the choice of changing it to “Trolling” rules if the opponent is notified of it before the room is opened for the first time. "Overlapping" rules are only in effect if both teams mutually agree to it before the room is opened for the first time.

    e. Overlapping
    e.i. Players are not allowed to be overlapped. Should this happen, the player must, without affecting the other players, move out of the line of any player’s, item boxes and/or dropped mushrooms/stars. They may not affect the other players in any way, shape, or form for the remainder of the race and/or gain positions from which they were overlapped in.
    e.ii. An overlapped player must allow any non-overlapped players to hit him/her with items.
    e.iii. If a player overlaps another player due to re-spawning in front of them (As in Lakitu appears holding the player in front of the overlapped player and henceforth), the overlapped player must immediately abide by rule XII. e.i.
    e.iv. If a player is overlapped while under the effects of an item used prior to being overlapped, a penalty will not be given. However they must still abide by rule XII. e.i.
    e.v. Players are not allowed to affect any players that are in close range of overlapping them. Rule XII. e.vi. is the only possible exception.
    e.vi. Players close to being overlapped may only take item boxes that are out of the usual line of first place, and may only take said item boxes if there are others readily and easily available in the item set.
    e.vii. Close encounters between players close to being overlapped and the first place player will not be counted as an overlap unless sufficient proof is presented to prove that an overlap occurred. If the player close to being overlapped provides evidence from their perspective that they did not get overlapped, no penalty will be given.
    e.viii. If e.i.-e.vi. are broken while overlapping rules are in effect, a penalty of 10 or 20 points will be given depending on the severity of each incident (assuming sufficient proof is presented).
    a. “Suicide Bagging” rules are in effect by default. However, the home team has the choice of changing it to “Trolling” or “Overlapping” rules if the opponent is notified of it before the room is opened for the first time.

    e. Overlapping
    e.i. Should a player be overlapped, they must, without affecting the other players, move out of the line of any players, item boxes, and/or ground items within 5 seconds of being overlapped. When this is performed, the player is not allowed to move (minor movement is fine if the player is stopped on a sloped surface, but this is not an excuse to drive near or around any item boxes), use any items, make contact with any item boxes, collide with any ground items, hit any ingame hazards that can cause items to be lost (i.e. thwomps, cars, etc), fall off of the track, and/or gain positions from which they were overlapped in for the remainder of the race. Using the rearview mirror every few seconds will prevent disconnection while overlapped.
    e.ii. An overlapped player must allow any non-overlapped players to hit him/her with items.
    e.iii. If a player overlaps another player due to re-spawning in front of them (As in Lakitu appears holding the player in front of the overlapped player and henceforth), the overlapped player must immediately abide by rule XII. e.i.
    e.iv. If a player is overlapped while under the effects of an item used prior to being overlapped, a penalty will not be given. However they must still abide by rule XII. e.i. when given the opportunity.
    e.v. Players are not allowed to affect any players that are in close range of overlapping them. Rule XII. e.vi. is the only possible exception.
    e.vi. Players close to being overlapped may only take item boxes that are out of the usual line of first place, and may only take said item boxes if there are others readily and easily available in the item set.
    e.vii. Close encounters between players close to being overlapped and the first place player will not be counted as an overlap unless sufficient proof is presented to prove that an overlap occurred. If the player close to being overlapped provides evidence from their perspective that they did not get overlapped, no penalty will be given.
    e.viii. If e.i.-e.vi. are broken while overlapping rules are in effect, a penalty of 10 or 20 points will be given depending on the severity of each incident (assuming sufficient proof is presented). A penalty may not be given if the incident has no effect on the results of the race.

    Reason: Many flaws of the "Overlapping" ruleset were fixed so we could ultimately put it in as a host's bagging pick like the "Trolling" ruleset has been.

    --------------------------------------------------------------------

    Change: Modification of Rule XV. a.

    a. Matches are to take place at the scheduled date/time unless both teams are in agreement to play at a different date/time before the scheduled time, or no later than 9 days after the scheduled date/time.
    a. Matches are to take place at the scheduled date/time unless both teams are in agreement to play at a different date/time that precedes both of their next match's originally scheduled date/time.

    Reason: It was requested that league matches should stop piling up and causing standings to fall behind, and the staff agreed with these requests.

    --------------------------------------------------------------------

    Change: Addition of Rules XVII. d.i. and d.ii.

    d.i. Any players affiliated with the withdrawing team in question may have any transfer requests in the same season denied.
    d.ii. If a team from a regular track division withdraws during a season, the rules stated in d. will apply to their custom track team as well (if they have a similar roster as the team that has withdrawn), and vice-versa.

    Reason: It was requested that there should be more repercussions for teams that drop out of the league, and the staff agreed with these requests.

    --------------------------------------------------------------------

    Change: Modification of Rule XIX. and addition of Rule XIX. f. (with every rule below it moved down)

    c. Players can be punished for misconduct in any medium. This includes, but is not limited to: MKBoards posts, YouTube comments/videos, verbal/text Twitch statements, Twitter messages/tweets, Skype statuses, verbal/text Skype statements.
    c. Players can be punished for misconduct in any medium. This includes, but is not limited to: MKBoards posts, YouTube comments/videos, verbal/text Twitch statements, Twitter messages/tweets, Skype statuses, verbal/text Skype or Discord statements.

    f. Incidents of misconduct may receive a different punishment from the system in rule XIX. b. depending on the severity of said incident. For example, a minor incident may only result in 1 match ban, but a more severe incident may immediately result in 3 match bans.

    Reason: For c., it was to reflect the recent rise of Discord in the community. For NEW f., it was to cover for those people who just happen to be Mega-Dicks.

    Good luck to all teams in season 7!~
     
    Last edited: May 7, 2016
    adagify, SiKH and Quinten like this.
  13. ~Maidvelia❤~

    ~Maidvelia❤~ Sometimes Looking Into The Past Helps Your Future

    • MKBoards Supporter
    • Founding Member
    Joined:
    Jul 26, 2013
    Messages:
    5,993
    Gender:
    Male
    Location:
    Warren, MI, USA
    Team:
    U★, GE
    Wiimmfi FC:
    4297-4674-3102
    Update

    Change: Modification of Rules VII. a. and VII. b.

    a. Hosts must reset the room after each race someone disconnects if requested, unless the team requesting the reset has already used their allowed amount of resets (see rule IV. c. for more information).*

    b. Hosts must reset the room if there are less than 8 players [4vs4], 10 players [5vs5], or 12 players [6vs6] on the voting screen if requested, unless the team has already used their allowed amount of resets (see rule IV. c. for more information).*
    a. Hosts must reset the room after each race someone disconnects if requested.*

    b. Hosts must reset the room if there are less than 8 players [4vs4], 10 players [5vs5], or 12 players [6vs6] on the voting screen if requested.*

    Reason: Since teams have the option to take a -20 penalty for any subsequent resets after their allotted 2 resets, the rule has been changed so that the host team must reset if the non-hosting team requests it without an option to decline the non-hosting team a reset, should they want it.

    --------------------------------------------------------------------

    Change: Addition of Rule IV. c.iii.

    c.iii. If the hosting team does not reset the room, they will receive a 20 point penalty for each time the first race of a GP starts (60 point cap).

    Reason: To have a consequence for hosts when they do not reset the room when they are supposed to.

    --------------------------------------------------------------------

    Change: Modification of Rules X. b. and X. c.

    b. All disc users abiding by Conditional Particpation rules must screen-share their startup to either a council member or one of the opposing team's members and load through either the CTGP Revolution channel or the Wiimmfi Patcher. For the entire process, they must screen-share their full desktop screen and have their television visible via webcam or capture card. Going offline will require steps b.i.-b.iv. or b.v.-b.vii. to be redone. The procedures are as follows:

    c. All ISO users abiding by Conditional Participation rules will load via USB Loader GX (any previously caught cheaters abiding by Conditional Participation rules may only complete their conditionals using one of the disc procedures). They must stream their conditionals via Skype call to either a council member or one of the opposing team's members. For the entire process, they must screen-share their full desktop screen and have their television visible via webcam or capture card. Going offline will require steps c.i.-c.vii. to be redone. The procedure is as follows:
    b. All disc users abiding by Conditional Particpation rules must screen-share their startup to either a council member or one of the opposing team's members and load through either the CTGP Revolution channel or the Wiimmfi Patcher. For the entire process, they must screen-share their full desktop screen and have their television visible via webcam or capture card. Council members or opponents confirming said player's conditionals may request the recorder to perform actions outside of the conditionals procedure for the purposes of proving that the conditionals weren't pre-recorded. Going offline will require steps b.i.-b.iv. or b.v.-b.vii. to be redone. The procedures are as follows:

    c. All ISO users abiding by Conditional Participation rules will load via USB Loader GX (any previously caught cheaters abiding by Conditional Participation rules may only complete their conditionals using one of the disc procedures). They must stream their conditionals via Skype call to either a council member or one of the opposing team's members. For the entire process, they must screen-share their full desktop screen and have their television visible via webcam or capture card. Council members or opponents confirming said player's conditionals may request the recorder to perform actions outside of the conditionals procedure for the purposes of proving that the conditionals weren't pre-recorded. Going offline will require steps c.i.-c.vii. to be redone. The procedure is as follows:

    Reason: Any council member or opposing team member watching conditionals may ask the player doing the conditionals to perform some form of action to prove that the conditionals were not pre-recorded.
     
  14. ~Maidvelia❤~

    ~Maidvelia❤~ Sometimes Looking Into The Past Helps Your Future

    • MKBoards Supporter
    • Founding Member
    Joined:
    Jul 26, 2013
    Messages:
    5,993
    Gender:
    Male
    Location:
    Warren, MI, USA
    Team:
    U★, GE
    Wiimmfi FC:
    4297-4674-3102
    Update

    Change: Modification of Rule V. a.i. and Addition of Rule V. g.

    a.i. If a clan tag is in the middle of a player's Mii name, there must be acceptable separator characters on both sides of the clan tag.
    a.i. If a clan tag is placed somewhere in the middle of a player's Mii name, there must be acceptable separators on both sides of said clan tag and they must be symmetrical until another non-separator character is reached.

    Examples for Clarification:

    -[ut]Player- ✔
    -ut_Player- ✔
    -ut- ✔
    --ut-- ✔
    %-ut-% ✔

    #%ut_Plyr- ✘
    -ut% ✘
    %-ut- ✘
    %-ut*% ✘
    @*ut-% ✘
    g. Mii names only consisting of a team's tag do not require a separator.​

    Reason: Both of these changes were made to be a solution for the problem addressed in this post.​
     
  15. ~Maidvelia❤~

    ~Maidvelia❤~ Sometimes Looking Into The Past Helps Your Future

    • MKBoards Supporter
    • Founding Member
    Joined:
    Jul 26, 2013
    Messages:
    5,993
    Gender:
    Male
    Location:
    Warren, MI, USA
    Team:
    U★, GE
    Wiimmfi FC:
    4297-4674-3102
    Update

    Change: Modification of Rule IV. d.

    d. Players may not use the following glitches:
    - Coconut Mall (both the ultra glitch and the downward spiral skip are banned)
    - Grumble Volcano (the lava respawn and rock-hop glitches are allowed)
    - Maple Treeway (both position and ultra glitch are banned)
    - Mario Circuit
    - Mushroom Gorge
    - Rainbow Road (both methods of the ultra glitch are banned, however the moon-jump at the beginning is allowed)
    - Wario's Gold Mine
    - GCN Peach Beach
    - GCN Waluigi Stadium
    - N64 DK's Jungle Parkway (both the ultra glitch and the spiral skip are banned)
    - N64 Sherbet Land
    d. Players may not use the following glitches:
    - Coconut Mall (both the ultra glitch and the downward spiral skip are banned)
    - Grumble Volcano (the lava respawn and rock-hop glitches are allowed)
    - Maple Treeway (both the ultra glitch and any variations of the position glitch are banned, however the u-turn skip is allowed. For clarification: the position glitch involves using any alternate route that directly combines the area after the cannon with the area of track between the u-turn and the trickable net)
    - Mario Circuit
    - Mushroom Gorge
    - Rainbow Road (both methods of the ultra glitch are banned, however the moon-jump at the beginning is allowed)
    - Wario's Gold Mine
    - GCN Peach Beach
    - GCN Waluigi Stadium
    - N64 DK's Jungle Parkway (both the ultra glitch and the spiral skip are banned)
    - N64 Sherbet Land

    Reason: Clarification on what the position glitch for Maple Treeway is. Any offenses of this glitch before this update was made will not be penalized. All offenses of this glitch after this update WILL be penalized, starting from this point and onward.

    --------------------------------------------------------------------

    Change: Modification of Rule XII. d.

    *d. The player who posts the match result must include a screenshot from http://wiimmfi.de/mkw of all participants and their friend codes (example: http://i.imgur.com/77KNcNl.png). Any edits discovered on the screenshot will result in the team/player involved facing severe consequences at the staff's discretion.
    *d. Both teams who played in the match are equally responsible for including a screenshot from http://wiimmfi.de/mkw of all participants and their friend codes (example: http://i.imgur.com/77KNcNl.png). Any edits discovered on the screenshot will result in the team(s)/player(s) involved facing severe consequences at the staff's discretion.

    Reason: We had made it clear in a meeting that we wanted both teams responsible for getting the necessary room pictures. We stated this change in the Changes Between the Season 5 and Season 6 Rulesets thread, but we forgot to amend the official ruleset to reflect this change. This has now been corrected. All strikes given for this situation before this update was made, will be revoked. All offenses from this point and onward WILL get struck and the strike is to stay put.
     
  16. ~Maidvelia❤~

    ~Maidvelia❤~ Sometimes Looking Into The Past Helps Your Future

    • MKBoards Supporter
    • Founding Member
    Joined:
    Jul 26, 2013
    Messages:
    5,993
    Gender:
    Male
    Location:
    Warren, MI, USA
    Team:
    U★, GE
    Wiimmfi FC:
    4297-4674-3102
    Update

    Change: Modification of Rule III. g.ii.

    g.ii. If a player's team dies or drops out of the league, the player is allowed one free transfer. This free transfer, and only this free transfer, bypasses rules g.i. and g.ii.
    g.ii. If a player's team dies, the player is allowed one free transfer. This free transfer, and only this free transfer, bypasses rules g. and g.i.

    Reason: To remove the contradiction with XVII. d.i., and also to remove Matt's typo when he came up with it (which was g.i. and g.ii. --> g. and g.i.).
     
  17. ~Maidvelia❤~

    ~Maidvelia❤~ Sometimes Looking Into The Past Helps Your Future

    • MKBoards Supporter
    • Founding Member
    Joined:
    Jul 26, 2013
    Messages:
    5,993
    Gender:
    Male
    Location:
    Warren, MI, USA
    Team:
    U★, GE
    Wiimmfi FC:
    4297-4674-3102
    Update

    Change: Modification of Rule I. h.

    h. The scores of any match are protected from any penalties/score changes 48 hours after the match's result thread is posted, with the exception of cheating cases and improper conditionals.
    h. Any sort of evidence that may result in a score change must be posted on the thread and/or brought to a staff member's attention within 48 hours after the match's result thread is posted. If this requirement is not met, the evidence will not be acknowledged by council (this does not apply for cheating cases and improper conditionals).

    Reason: Discussion of a verdict that results in a score change was not meant to stop after 48 hours. The 48 hour period was supposed to only be the window for when evidence that results in score changes can be presented. This has now been clarified.
     
  18. ~Maidvelia❤~

    ~Maidvelia❤~ Sometimes Looking Into The Past Helps Your Future

    • MKBoards Supporter
    • Founding Member
    Joined:
    Jul 26, 2013
    Messages:
    5,993
    Gender:
    Male
    Location:
    Warren, MI, USA
    Team:
    U★, GE
    Wiimmfi FC:
    4297-4674-3102
    MASSIVE UPDATE

    Change: Modification of the entirety of Section I. ~ General (due to all rules being moved down).

    I. General Rules

    a. Any team or player that tries to manipulate rules may suffer consequences at the staff's discretion. This means gentlemen's agreements are not allowed.
    b. All rules and penalties are to be enforced by the staff. However, in some scenarios these rules and penalties may be overruled by a 2/3 majority vote within the current WL council.
    c. MKB account bans are to be treated the same as WL bans unless the sole reason for the account ban was a COPPA violation.
    d. All compensation and penalty values in the Match Rules are based on the 5vs5 point distribution. To get the compensation and penalties for other match sizes, go here: http://tinyurl.com/wlmultiplier.
    e. Rule changes made mid-season will apply for all matches played after the change has been made with the exception of reschedules (at the staff's discretion). An announcement thread or post will be made for any and all rule changes.
    f. All teams will have 2 player representatives (a third representative will be allowed on an emergency basis). These player representatives will be the only ones organizing their team’s matches throughout the league, no one else.
    g. All player representatives for each team will be added to a Discord channel made by the league admin(s) for their division. The league admin(s) and the division admin will oversee the channel. All match organization is to be taken place in the channel.
    g.i. Any team who does not organize a match in their respective Discord channel runs the risk of the staff ruling any proof of rule(s) being broken as invalid.​
    h. Any sort of evidence that may result in a score change must be posted on the thread and/or brought to a staff member's attention within 48 hours after the match's result thread is posted. If this requirement is not met, the evidence will not be acknowledged by council (this does not apply for cheating cases and improper conditionals).
    I. General Rules

    a. Participants of the Wiimmfi League are prohibited from "bending" or "manipulating" rules or loopholes in the rules in order to create a benefit to any participating team in the league. Players who are found to be performing such acts will be subject to punishment based upon the severity of the incident caused by such ruleset manipulation. All players in the Wiimmfi League are expected to use common sense in all actions that they take, and to not act foolish for the sake of trying to cause harm. The league, whereas being competitive, is also meant to be simple and easy to understand, so if you do have any questions as to what the rules do and do not allow, please ask a member of staff before reporting anything invalid or manipulating rules, or else again you risk being punished.
    b. If staff error leads to a potential punishment, the punishment is to not go through and the error will be rectified for the following week.
    c. All rules and penalties are to be enforced by the staff. However, in some scenarios these rules and penalties may be overruled by a 2/3 majority vote within the current WL council.
    d. MKB account bans are to be treated the same as WL bans unless the sole reason for the account ban was a COPPA violation.
    e. All compensation and penalty values in the Match Rules are based on the 5vs5 point distribution. To get the compensation and penalties for other match sizes, go here: http://tinyurl.com/wlmultiplier.
    f. Rule changes made mid-season will apply for all matches played after the change has been made with the exception of reschedules (at the staff's discretion). An announcement thread or post will be made for any and all rule changes.
    g. All teams will have 2 player representatives (a third representative will be allowed on an emergency basis). These player representatives will be the only ones organizing their team’s matches throughout the league, no one else.
    h. All player representatives for each team will be added to a Discord channel made by the league admin(s) for their division. The league admin(s) and the division admin will oversee the channel. All match organization is to be taken place in the channel.
    h.i. Any team that does not organize a match in their respective Discord channel runs the risk of receiving a strike and the staff ruling any proof of rule(s) being broken as invalid.​
    i. Any sort of evidence that may result in a score change must be posted on the thread and/or brought to a staff member's attention within 48 hours after the match's result thread is posted. If this requirement is not met, the evidence will not be acknowledged by council (this does not apply for cheating cases, improper conditionals, and/or improper registrations).
    j. All times listed in the rules are according to the Eastern Timezone (ET). Daylight Savings is taken into account as well.

    Reason: Throughout the last few seasons we have seen staff errors lead to punishments, and we have also seen people try to bend the rules or manipulate their meanings in a way to negatively impact the league in some way. We have decided to prevent these issues from happening by incorporating the new rules, I. a. and I. b. We have also placed in I. h.i. as we are pushing for Division Admins to be able to have clearer evidence on what has been agreed for matches, and edited rule I i. to add improper registrations to the 48 hour exception list. I. j. was added to be more clear on what timezone the times listed in the rules use.

    ______________________________________________________________


    Change: Modification of Rules II. b. and c., Addition of Rule II. d.

    b. If a player is clean of strikes 4 matches in a row after previously having a strike count, their strike count will be reset. A strike after this will resume the strike count as if the player had 2 strikes.
    c. Any section or individual rule with an asterisk (*) next to it will follow the strike system procedure.

    List of Rules Underneath the Strike System:

    IV. f.
    All of V.
    VII. a.
    VII. b.
    VII. d.
    VII. e.
    VII. f.
    XIII. a.
    XIII. b.
    XIII. c.
    XIII. d.
    b. Staff discretion will be used to determine if a strike will be given and how many strikes will be given for repeat offenses.
    c. If a player is clean of strikes 4 matches in a row after previously having a strike count, their strike count will be reset. A strike after this will resume the strike count as if the player had 2 strikes.
    d. Any section or individual rule with an asterisk (*) next to it will follow the strike system procedure.

    List of Rules Underneath the Strike System:

    I. h.i.
    All of V.
    VII. b.
    VII. c.
    VII. d.
    VII d.i.
    VII. e.
    VII. f.
    VII. g.
    VIII. g.
    XV. a.
    XV. b.
    XV. c.
    XV. d.

    Reason: Due to request, we are deciding to punish repeat offenses harsher. The other rules have remained, but have moved down, with the list of striking rules being changed to suit the update of the ruleset.

    ______________________________________________________________


    Change: Modification of Rules IV. a.i., e.i., e.ii., e.iv., g.-g.ii., h., and Addition of Rule g.iv. (formerly Section III).

    a.i. Exceptions can be made for players living in the same household and must be addressed to and approved by a registration admin.
    e.i. When a player registers for or transfers to a team they must have permission from a representative of said team (unless they are already a representative of that team).
    e.ii. When a team representative transfers a player to their team they must have permission from said player. If a team representative is transferring said player out of their team or to a different branch of their team (ex: ¢β1 to ¢β2), they do not need permission.
    e.iv. The council has the power to deny any player transferring down divisions if they deem the transfer in question to be inappropriate.​
    g. Transfers mid-season to other teams may only be done at least three weeks after their registration/previous transfer.
    g.i. Players may only transfer a maximum of 2 times during the season.
    g.ii. If a player's team dies, the player is allowed one free transfer. This free transfer, and only this free transfer, bypasses rules g. and g.i.​
    h. If a player is caught playing for a team with an unregistered FC, that player will lose all of their points or receive a penalty of 150 points (whichever is greater).
    a.i. Exceptions can be made for players living in the same household and must be addressed to and approved by a registration admin. Guests are also allowed, so long as they are registered on MKBoards and prove that they are the guest in question.
    e.i. When a player registers or transfers to a team there must be significant proof of permission from a representative of the team (unless they are a representative of the destination team).
    e.ii. If a team representative is transferring a player out of their team, to a different branch of their team (ex: ¢β1 to ¢β2), or to the same team for custom tracks (ex: LL + CL), they do not need permission. All other registration update threads may only be made by the player.
    e.iv. The council has the power to deny any player transferring down divisions if they deem the transfer in question to be inappropriate or in violation of the minimum division listing.​
    g. Transfers mid-season to other teams may only be done at least three weeks after their registration/previous transfer, and prior to the default time for week 6. Please note that rule IV. e. still applies.
    g.i. Players may only transfer one time during the season.
    g.ii. A player transferring from free agents is the only exception to g., provided they hadn't been registered for a team at any point during the season.
    g.iv. If a player's team dies or a player is transferred to free agents by their leader, the player is allowed one free transfer. This free transfer bypasses both rule IV. g.i. and the 3 week buffer time between previous transfers/initial registration.​
    h. If a player is caught playing for a team with an unregistered FC and/or invalid registration, that player will lose all of their points or receive a penalty of 150 points (whichever is greater).

    Reason: Due to the increased standards of Registration Admins, as well as some poorly phrased sentences in the past ruleset, we have decided to make what is and is not accepted by the Registration Admins clearer in the rules. We have also added the Minimum Division clause, and added a transfer deadline, again by strong request following Season 7's issues.

    ______________________________________________________________


    Change: Modification of Rule V. a., Removal of Rules V. a.i. and a.ii., Old Rules a.iii. and a.iv. moved to a.i. and a.ii.

    a. Team tags may be placed anywhere in Mii names, but must be separated in some fashion using an acceptable separator character.
    a.i. If a team tag is placed somewhere in the middle of a player's Mii name, there must be acceptable separators on both sides of said team tag and they must be symmetrical until another non-separator character is reached.

    Examples for Clarification:

    -[ut]Player- ✔
    -ut_Player- ✔
    -ut- ✔
    --ut-- ✔
    %-ut-% ✔

    #%ut_Plyr- ✘
    -ut% ✘
    %-ut- ✘
    %-ut*% ✘
    @*ut-% ✘​

    a.ii. Acceptable separator characters consist of either a space or any of the following characters:
    . , 、。 ' : ; " " ' " ( ) _ « » & [ ] 「 」『』【】 { } · < > + - × ÷ = ± ∞ % \ / | @ ^ ~ © ® ° ™ ♭ ♪ º * ← → ↑ ↓ # Φ ◎ ☆ △ □ ◇ ★ • ● ◆ ■ ▲ ▼ ¦ Δ ∴ ※ 〒 ()*[] ~, Digital Number :, Digital Number ., Digital Number /, Digital Number -, Digital Number +, DSi D-Pad, DSi Clock, DSi Smiley Face, DSi Mad Face, DSi Sad Face, DSi Serious Face, DSi Sun, DSi Cloud, DSi Umbrella, DSi Lock/Snowman, DSi [!], DSi [?], DSi Mail Envelope, DSi Cell Phone, DSi Dot-in-a-Box, DSi Spade, DSi Diamond, DSi Heart, DSi Clubs, DSi Left Arrow, DSi Right Arrow, DSi Up Arrow, DSi Down Arrow, DSi Cross
    a.iii. None of the symbols shown in this picture are allowed to be used anywhere in a player's Mii name: http://i.imgur.com/gloUccJ.png.
    a.iv. If a team's tag has a separator as the team tag itself, that is allowed to be used as the separator (ex: for the tag "#", the full Mii name with tag could be "#MONEY").​
    a. Team tags must be visibly separated from Mii names.

    Examples for Clarification:

    ut Player
    ut*Player
    [ut]Player
    -ut Plyr-
    -[ut]Plyr-
    Player ut
    Player*ut
    Player@ut
    -Plyr ut-
    -Plyr*ut-
    -Plyr@ut-
    c ut e
    -c ut e-
    -ut-
    ut
    a.i. None of the symbols shown in this picture are allowed to be used anywhere in a player's Mii name: http://i.imgur.com/gloUccJ.png.
    a.ii. If a team's tag has a separator as the team tag itself, that is allowed to be used as the separator (ex: for the tag "#", the full Mii name with tag could be "#MONEY").​

    Reason: We're trying to be more lenient this season with certain issues, and felt that certain parts of the ruleset such as this section about Mii Names were perhaps too harsh on players so have edited it to reflect our slightly less harsh opinion.

    ______________________________________________________________


    Change: Modification of Rules VI. b.ii., b.iii., b.viii. (formerly b.vii.). Current Rules VI. b.iii.-b.x. moved down due to Addition of Rule VI. b.xi.

    b.ii. If any player is caught using Remove Game Music?, Mii Heads on Minimap, or Speedometer, they will receive a penalty of 10 points per race (120 points total if left on for the entire match) until those are turned off.
    b.iii. If a host is caught with Thundercloud Autofire set to "OFF", Thundercloud Effect set to "Mega", or Host Always Wins Vote set to "ON", their team will be forced to reset the room at the cost of one of their resets (see rule IV. c. for more information). If the host refuses to reset, their team will receive a penalty of 150 points.
    b.iv. If a host is caught with Track Availability set to "All Tracks" instead of "Nintendo Tracks", their team will receive a penalty of 5 points per race (60 points total if left on for the entire match) until that is changed to Nintendo Tracks.
    b.v. If a host is caught with Track Availability set to "Custom Tracks" instead of "Nintendo Tracks", they must close the room at the cost of one of their team's resets (see rule IV. c. for more information). If there is proof that the host refused to reset, their team will forfeit the match.
    b.vi. If a host is caught with Vehicle Availability set to anything but "All Vehicles", the war may proceed without any penalty unless a reset is requested. If a reset is requested, the host must close the room at the cost of one of their team's resets (see rule IV. c. for more information). If the host refuses to close the room when a reset is requested, their team will receive a penalty of 150 points.
    b.vii. If a host is caught with Specific Engine Class set to anything but "Normal", they must close the room at the cost of one of their team's resets (see rule IV. c. for more information). If the first race of the in-game GP is completed with one of these settings enabled, their team will receive a penalty of 30 points (90 point cap).
    b.viii. If a host is caught with Race Count set to above 4, they must close the room at any point before race 5 at the cost of one of their team's resets (see rule IV. c. for more information). If there is proof that the host refused to reset before race 5, their team will receive a penalty of 30 points for each additional race played (up to 240 points in total penalties if 8 additional races are played).
    b.ix. If a host is caught with Race Count set to below 4, their team will lose a reset (see rule IV. c. for more information) each time a GP ends (showing the final results screen with the Engine Class) without 4 races being completed.
    b.x. If a host is caught with Room Encryption set to "ON" and the room freezes, the host's team will lose one of their resets (see rule IV. c. for more information) and will have to set the setting to "OFF". If the room does not freeze, the war may proceed without any penalty.​
    b.ii. If any player is caught using Remove Game Music? or Mii Heads on Minimap, they will receive a penalty of 10 points per race (120 points total if left on for the entire match) until those are turned off.
    b.iii. If any player is caught using Speedometer, they will receive a penalty of 5 points per race (60 points total if left on for the entire match) until it is turned off.
    b.iv. If a host is caught with Thundercloud Autofire set to "OFF", Thundercloud Effect set to "Mega", or Host Always Wins Vote set to "ON", their team will be forced to reset the room at the cost of one of their resets (see rule IV. c. for more information). If the host refuses to reset, their team will receive a penalty of 150 points.
    b.v. If a host is caught with Track Availability set to "All Tracks" instead of "Nintendo Tracks", their team will receive a penalty of 5 points per race (60 points total if left on for the entire match) until that is changed to Nintendo Tracks.
    b.vi. If a host is caught with Track Availability set to "Custom Tracks" instead of "Nintendo Tracks", they must close the room at the cost of one of their team's resets (see rule IV. c. for more information). If there is proof that the host refused to reset, their team will forfeit the match.
    b.vii. If a host is caught with Vehicle Availability set to anything but "All Vehicles", the war may proceed without any penalty unless a reset is requested. If a reset is requested, the host must close the room at the cost of one of their team's resets (see rule IV. c. for more information). If the host refuses to close the room when a reset is requested, their team will receive a penalty of 150 points.
    b.viii. Unless a different setting is mutually agreed upon by both teams, a host caught with Specific Engine Class set to anything but "Normal" must close the room at the cost of one of their team's resets (see rule IV. c. for more information). If the host refuses to reset, their team will receive a penalty of 8 points per race (96 point cap). The same penalty would also be given if the agreed upon settings are not set.
    b.ix. If a host is caught with Race Count set to above 4, they must close the room at any point before race 5 at the cost of one of their team's resets (see rule IV. c. for more information). If there is proof that the host refused to reset before race 5, their team will receive a penalty of 30 points for each additional race played (up to 240 points in total penalties if 8 additional races are played).
    b.x. If a host is caught with Race Count set to below 4, their team will lose a reset (see rule IV. c. for more information) each time a GP ends (showing the final results screen with the Engine Class) without 4 races being completed.
    b.xi. If a host is caught with Room Encryption set to "ON" and the room freezes, the host's team will lose one of their resets (see rule IV. c. for more information) and will have to set the setting to "OFF". If the room does not freeze, the war may proceed without any penalty.​

    Reason: Although the speedometer gives a player an advantage that not all players have access too, however small it is, we feel that it is such a small advantage that it is appropriate to reduce the punishment.

    We have decided to allow teams to select which engine class they would like the races to be in, assuming both teams agree.

    ______________________________________________________________


    Change: Modification of the entirety of Section VII. ~ Hosting (due to all rules being moved down).

    VII. Hosting

    *a. Hosts must reset the room after each race someone disconnects if requested.
    *b. Hosts must reset the room if there are less than 8 players [4vs4], 10 players [5vs5], or 12 players [6vs6] on the voting screen if requested.
    c. Before opening the room, the hosting team must provide the opposing team with a host friend code and wait for the opposing team to give permission to open the room. If no confirmation to open the room has been given 5 minutes after the scheduled match time, the room may be opened.
    c.i. If the room is opened before the opposing team gives permission or before waiting the 5 minutes, the host must close and reopen the room if the opposing team requests it.​
    *d. The host must allow a maximum of 20 minutes after the scheduled/agreed start time for players to join the room and start it after that time frame unless both teams are in agreement to start sooner or wait longer.
    *e. The host must wait a minimum of 10 seconds and a maximum of 5 minutes before starting the room between GPs (continuing the match) unless both teams are in agreement to start sooner or wait longer.
    *f. The host is not allowed to start without all participants in the room unless the allotted time for the room to be opened is exceeded or if the opposing team gives consent for the host to start earlier without all of their participants in the room. If this rule is broken, the host must reset at the cost of one of the hosting team's allowed resets.
    g. The host is not allowed to kick any players from the opposing team from the room at any point in the match unless they're given permission. If this rule is broken, the hosting team will receive a penalty of 100 points for every player kicked, the room will be reset (counting as a hosting team's reset if applicable), and the host will be permanently banned from hosting. If the kick happens during a race, the race will not count.
    g.i. To check if someone was kicked, go to http://wiimmfi.de/show-bans. If so, take a screenshot and contact a staff member immediately.​
    VII. Hosting

    a. The host is required to start to start a VS race at the start of each GP. If the host starts a Team VS, Balloon Battle, Coin Runners, or Countdown then they will be forced to use a reset. If the team refuses to reset, then they will forfeit the match.
    *b. Hosts must reset the room after each race someone disconnects if requested.
    *c. Hosts must reset the room if there are less than 8 players [4vs4], 10 players [5vs5], or 12 players [6vs6] on the voting screen if requested.
    d. Before opening the room, the hosting team must provide the opposing team with a host friend code and wait for the opposing team to give permission to open the room. If no confirmation to open the room has been given 5 minutes after the scheduled match time, the room may be opened.
    d.i. If the room is opened before the opposing team gives permission or before waiting the 5 minutes, the host must close and reopen the room if the opposing team requests it.​
    *e. The host must allow a maximum of 20 minutes after the scheduled/agreed start time for players to join the room and start it after that time frame unless both teams are in agreement to start sooner or wait longer.
    *f. The host must wait a minimum of 10 seconds and a maximum of 5 minutes before starting the room between GPs (continuing the match) unless both teams are in agreement to start sooner or wait longer.
    *g. The host is not allowed to start without all participants in the room unless the allotted time for the room to be opened is exceeded or if the opposing team gives consent for the host to start earlier without all of their participants in the room. If this rule is broken, the host must reset at the cost of one of the hosting team's allowed resets.
    h. The host is not allowed to kick any players from the opposing team from the room at any point after the room opens without consent. To check if someone was kicked, go to http://wiimmfi.de/show-bans. If a kick was performed, take a screenshot and contact a staff member immediately.
    h.i. If this rule is broken while waiting for the room to start (kicking players to get any potential advantage), the hosting team will lose a reset for each player kicked and the host of the room will receive punishments as mentioned in rule VII. h.iii.
    h.ii. If this rule is broken during a race, the hosting team will receive a penalty of 100 points for every player kicked and the room will be reset if requested (counting as a hosting team's reset if applicable [see rule VIII. c. for more information]).
    h.iii. If a player violates either rule VII. h.i. or h.ii., they will receive a season ban from hosting if the match in question was outside of the league, or a permanent ban from hosting if the match in question was a league match.
    h.iv. If a player on the opposing team is kicked from the room during a kickstart or when kicking a player not participating in the war, rule h.i. is nullified. If this happens after the room starts, however, the host must immediately reset the room at the cost of one of the hosting team's resets (see rule VIII. c. for more information).
    h.v. If a team uses a host-banned player as the match host, they will receive a penalty of either 30 points per race with a maximum of 150 points or the points the host-banned player had (whichever is greater).​

    Reason: The main modification is to the rules regarding the host kicking players from the room. The punishment for kicking an opposing player during a race has not changed. However, it is also possible for the host to kick players from the room during the room-joining phase in order to get their team better spots in the room. We have decided that this should be punished. It is also possible for a host to accidentally kickstart the wrong person, and we have decided that this should also be punished, although not as harshly as if the host kicked an opposing player during a race.

    ______________________________________________________________


    Change: Modification of Rule VIII. c.iii., Addition of Rules d.-d.iii., all rules below moved down (this was formerly Section IV.).

    c.iii. If the hosting team does not reset the room, they will receive a 20 point penalty for each time the first race of a GP starts (60 point cap).​
    d. Players may not use the following glitches:
    - Coconut Mall (both the ultra glitch and the downward spiral skip are banned)
    - Grumble Volcano (the lava respawn and rock-hop glitches are allowed)
    - Maple Treeway (both the ultra glitch and any variations of the position glitch are banned, however the u-turn skip is allowed. For clarification: the position glitch involves using any alternate route that directly combines the area after the cannon with the area of track between the u-turn and the trickable net)
    - Mario Circuit
    - Mushroom Gorge
    - Rainbow Road (both methods of the ultra glitch are banned, however the moon-jump at the beginning is allowed)
    - Wario's Gold Mine
    - GCN Peach Beach
    - GCN Waluigi Stadium
    - N64 DK's Jungle Parkway (both the ultra glitch and the spiral skip are banned)
    - N64 Sherbet Land
    d.i. Any usage of these glitches on the tracks above will result in a penalty of 100 points towards the player's team and his/her individual score (for every person performing a glitch) per race.
    d.ii. All Players’ points will be corrected to their true values assuming sufficient proof of those true values is presented.​
    e. Any team that is responsible for picking a track that has already been played will receive a 20 point penalty (with the exception of a track selected via random, not including the CTGP randomizer).
    e.i. If a player provides video evidence that the CTGP randomizer was responsible for selecting a track that has already been played (without having a cup pre-selected), then no penalty will be given for the repick.​
    *f. Picking a Custom Track in CTGP-R due to the host having the track availability set to “All Tracks” will require a restart of the room. The team whose player had their Custom Track pick selected will use one of their resets in this instance (see rule IV. c. for more information).
    g. All players must have at least 5000 VR on the license they choose to use for a match. If the first race of the in-game GP is completed with a player's VR not meeting this requirement, their team will receive a penalty of 30 points (90 point cap).
    c.iii. If there is sufficient evidence that the hosting team did not reset the room when the away team wanted to use one of their resets, they will receive a 20 point penalty for each race that is played (240 points total for the entire match).​
    d. Players can freely choose to use any character, vehicle, drift type, and/or controller, unless rule VIII. d.i. applies.
    d.i. If player(s) of a team select the Magikruiser or Dolphin Dasher for the last race of a match (after the 11th race has been played), a 10 point penalty will be applies for every player using the Magikruiser or Dolphin Dasher (assuming sufficient evidence is provided). The only exception to this rule is if the player was in the Magikruiser or Dolphin Dasher during the previous race in the GP.
    e. Players may not use the following glitches:
    - Coconut Mall (1)
    - Coconut Mall (2)
    - Grumble Volano (the lava respawn and rock-hop glitches are allowed)
    - Maple Treeway (both the ultra glitch and any variations of the position glitch are banned, however the u-turn skip is allowed. For clarification: the position glitch involves using any alternate route that directly combines the area after the cannon with the area of track between the u-turn and the trickable net)
    - Mario Circuit
    - Mushroom Gorge
    - Rainbow Road (both methods of the ultra glitch are banned [method 1, method 2], however the moon-jump at the beginning is allowed)
    - Wario’s Gold Mine
    - GCN Peach Beach
    - GCN Waluigi Stadium (1)
    - GCN Waluigi Stadium (2)
    - N64 DK’s Jungle Parkway (1)
    - N64 DK’s Jungle Parkway (2)
    - N64 Sherbet Land
    e.i. Any usage of these glitches on the tracks above will result in a penalty of 100 points towards the player's team and his/her individual score (for every person performing a glitch) per race.
    e.ii. All Players’ points will be corrected to their true values assuming sufficient proof of those true values is presented.​
    f. Any team that is responsible for picking a track that has already been played will receive a 20 point penalty (with the exception of a track selected via random, not including the CTGP randomizer).
    f.i. If a player provides video evidence that the CTGP randomizer was responsible for selecting a track that has already been played (without having a cup pre-selected), then no penalty will be given for the repick.​
    *g. Picking a Custom Track in CTGP-R due to the host having the track availability set to “All Tracks” will require a restart of the room. The team whose player had their Custom Track pick selected will use one of their resets in this instance (see rule IV. c. for more information).
    h. All players must have at least 5000 VR on the license they choose to use for a match. If the first race of the in-game GP is completed with a player's VR not meeting this requirement, their team will receive a penalty of 30 points (90 point cap).

    Reason: Regarding rule c.iii, we decided the old rule did not give the host a sufficient punishment for failing to reset the room at the other team's request if there was a disconnection.

    Regarding rule d.i, which bans the "Magi strat," the Magikruiser and the Dolphin Dasher only serve one purpose in a competitive league format. Their only purpose is to do the Magi strat, which involves a team picking one of the aforementioned vehicles, both of which have excellent offroad stats, and picking a track with tons of offroad, in order to pull off a comeback victory. As these vehicles are significantly worse on the vast majority of tracks, that is their only use in a competitive league format which allows all vehicles (in particular, far superior ones such as the Flame Runner and Mach Bike).

    The Magi strat introduces a strong element of luck into the game. It essentially turns wars into a coin flip based on whether the heavy offroad track is chosen for the last race or not. While Mario Kart has a notable inherent element of luck due to the nature of items, it is still in the interest of the league to ensure matches are as competitive as possible. Leaving the result of the war up to a coin flip is uncompetitive. Though the council does not intend on banning every form of luck, the power of the Magi strat to decide the winner based on luck is deemed too uncompetitive to be allowed in league play. As the only use of the Magikruiser and the Dolphin Dasher is do the Magi strat, it is, for all practical purposes, equivalent to ban the vehicles in this way.

    We acknowledge that there are strategies associated with the Magi strat (for example, psychological ones, deciding how many players should use the Magikruiser, delaying your track pick to see what the opponent picks to see if they're doing the Magi strat or not, etc.) However, despite these strategies, we still feel the Magi strat adds an extreme element of luck to matches that is not conducive to a better competitive environment.

    However, if a player had already been using the Magikruiser or the Dolphin Dasher by the 11th or 12th race , then they should be allowed to continue to use the vehicle, as they put themselves at a disadvantage by choosing to use these suboptimal vehicles for an extended period of time.

    ______________________________________________________________


    Change: Addition of Rules XIII. b. and b.i., Old b.-b.ii. now c.-c.ii. (this was formerly Section IX.).

    b. Teams may not use banned players.
    b.i. If a team uses a banned player, they will be banned from the league.
    b.ii. The staff reserves the right to further a team's and/or individual player’s punishment.​
    b. Bans for cheating range from a season, 2 years, and permanent at the council’s discretion (other ban types and lengths are covered in the ruleset). Season bans are for minor incidents, while the default ban is 2 years. If a player is caught cheating while serving a ban, their ban duration will reset back to 2 years. Permanent bans will only be given if there is no other option for the Council regarding a player.
    b.i. If a player has served their 2 year ban, they will be moved to permanent conditionals unless the Council believe the player is too much of a threat to the league's integrity on conditionals. In which case, the player will remain banned.
    c. Teams may not use banned players.
    c.i. If a team uses a banned player, they will be banned from the league.
    c.ii. The staff reserves the right to further a team's and/or individual player’s punishment.​

    Reason: Elaboration on the punishments of banned players.

    ______________________________________________________________


    Change: Addition of Rule XII. a.i. (this was formerly Section X.).

    a.i. If it has been 2 years since a player was placed on conditionals due to a suspicious incident, they will be taken off the conditionals list unless the Council believe an appeal is needed. In which case if the appeal is not sufficient, the player will remain on conditionals until they provide an appeal that is acceptable.​

    Reason: Self-explanatory.

    *The council have also discussed limiting certain software to display gameplay while screensharing. This rule update (if implemented) will be posted separately.

    ______________________________________________________________


    Change: Addition of Appeals as Section XIV. (XIV. was formerly Incomplete Matches).

    XIV. Appeals

    a. Players on the conditionals list, ban list, or host ban list may appeal their placement on the list once every 6 months.
    b. The privilege to appeal may be revoked from certain players at the council's discretion.

    Reason: Self-explanatory.

    ______________________________________________________________


    Change: Modification of Rule XV. f. (formerly XIII. f.).

    f. Point System
    f.i. If a team wins a match, they score 3 points on the leaderboard.
    f.ii. If two teams draw a match, they will each score 2 points on the leaderboard with the exception of both teams forfeiting (100-100) where neither team will receive any points.
    f.iii. If a team loses a match by more than 20 points, they score 0 points on the leaderboard.
    f.iv. If a team loses a match by 20 points or less, they will receive 1 point on the leaderboard.​
    f. The team with the better Win-Draw-Loss Record on the leaderboard is the higher placing team.

    Reason: Under the old system, it was possible for a team with a worse win-draw-loss record to defeat a team with a better ranking in the final standings. We have decided that this is illogical and should not be a possibility.

    ______________________________________________________________


    Change: Modification of the entirety of the entirety of Section XVI. ~ Tiebreakers (formerly XVIII.).

    #1: The greater amount of matches won in total.
    #2: The higher overall difference between those individual matches (ex: Match 1 - A 388-344 B, Match 2 - A 315-417 B; Total - A 703-761 B. B wins).
    #3: The higher overall difference (+/-) in total.​
    #1: The higher number of points based on the Point System described below.​
    - If a team wins a match, they will receive 3 points.
    - If two teams draw a match, they will each receive 2 points (with the exception of both teams forfeiting, where neither team will receive any points).
    - If a team loses a match by more than 20 points, they will receive 0 points.
    - If a team loses a match by 20 points or less, they will receive 1 point.​
    #2: The higher overall difference (+/-) in total.
    #3: The higher overall difference between those individual matches (ex: Match 1 - A 388-344 B, Match 2 - A 315-417 B; Total - A 703-761 B. B wins).​

    Reason: Due to teams being awarded points for ties and close losses, points is a more consistent metric to use than match wins when determining a winner. We also feel that overall (+/-) should be used as a tiebreaker before the scores in only the matches between the two teams.

    ______________________________________________________________


    Change: Addition of Rule XVIII. a.i. (this was formerly Section XV.).

    a.i. The scheduled date/time may be changed if it interferes with a scheduled MKU match, or if timezone issues regarding a team justifies it. If all teams in the division are not in agreement with the changed date/time however, the team requesting the change will not have their request fulfilled.​

    Reason: Teams should be allowed to change their scheduled time in order to convenience their schedules, but only as long as it doesn't inconvenience other teams.

    ______________________________________________________________


    In addition to the above changes, we redid the ordering of the sections.

    I. General Rules
    II. Strike System
    III. Registration
    IV. Match Structure
    V. Mii Names
    VI. Game Modifications
    VII. Hosting
    VIII. Lagging
    IX. Cheating
    X. Conditional Participation
    XI. Disconnections
    XII. Suicide Bagging, Trolling, & Overlapping
    XIII. Results
    XIV. Incomplete Matches
    XV. Rescheduling & Replays
    XVI. Forfeits
    XVII. Disqualifications / Withdrawals
    XVIII. Tiebreakers
    XIX. Conduct
    I. General
    II. Strike System
    III. Conduct

    IV. Registration
    V. Mii Names
    VI. Game Modifications
    VII. Hosting

    VIII. Match Structure
    IX. Suicide Bagging, Trolling, & Overlapping
    X. Disconnections & Player Compensation
    XI. Lagging

    XII. Conditional Participation
    XIII. Cheating
    XIV. Appeals

    XV. Results
    XVI. Tiebreakers
    XVII. Incomplete Matches
    XVIII. Rescheduling & Replays
    XIX. Forfeits
    XX. Disqualifications / Withdrawals

    The reason we changed the order was because we thought it was all over the place. The new ordering goes in a sequential order and is grouped into categories (the ending of which is denoted by the horizontal rule images on the thread).


    That's everything, have a wonderful Season 8!!~
     
    Teeples likes this.
  19. ~Maidvelia❤~

    ~Maidvelia❤~ Sometimes Looking Into The Past Helps Your Future

    • MKBoards Supporter
    • Founding Member
    Joined:
    Jul 26, 2013
    Messages:
    5,993
    Gender:
    Male
    Location:
    Warren, MI, USA
    Team:
    U★, GE
    Wiimmfi FC:
    4297-4674-3102
    Update

    Change: Addition of Rule I. g.i.

    g.i. All team representatives must cooperate with the requests of their division administrators. Failure to cooperate will result in removal as a team representative and the team in question having to find a replacement.​

    Reason: Being a team representative is a privilege, and deliberately making life harder for the division admins should get that privilege revoked.

    ______________________________________________________________

    Change: Modification of Rule III. a.

    a. All players participating in WL must conduct themselves in a respectful manner to all participants and staff.
    a. All players participating in WL must conduct themselves in a respectful manner to all participants and staff. They are also required to follow the general site guidelines, along with any other guidelines and requests set out by the WL Staff.

    Reason: Insubordination / refusing to cooperating with requests by division admins and other sections of the staff makes it harder for the league to progress, so we've decided it needs to be punished when necessary.

    ______________________________________________________________

    Change: Modification of Rule XV. d.

    *d. Both teams who played in the match are equally responsible for including a screenshot from http://wiimmfi.de/mkw of all participants and their friend codes (example: http://i.imgur.com/77KNcNl.png). Any edits discovered on the screenshot will result in the team(s)/player(s) involved facing severe consequences at the staff's discretion.
    *d. Both teams who played in the match are equally responsible for including a screenshot from http://wiimmfi.de/mkw of all participants, their friend codes, and the room's group ID (example: http://i.imgur.com/77KNcNl.png--the group ID would be XB99). Any edits discovered on the screenshot will result in the team(s)/player(s) involved facing severe consequences at the staff's discretion.

    Reason: For the staff to be able to more easily check match history (which helps confirm whether a wiimmfi.de picture was faked or not), we want all participants to now show the room ID on their wiimmfi.de pictures.

    *There may be one more update (for conditionals); it will be announced in a separate post when/if it's ready.
     
  20. ~Maidvelia❤~

    ~Maidvelia❤~ Sometimes Looking Into The Past Helps Your Future

    • MKBoards Supporter
    • Founding Member
    Joined:
    Jul 26, 2013
    Messages:
    5,993
    Gender:
    Male
    Location:
    Warren, MI, USA
    Team:
    U★, GE
    Wiimmfi FC:
    4297-4674-3102
    Update

    Change: Modification of Rule IX. a. and d.i., and removal of Rules IX. e.-e.viii. Section name also changed to Suicide Bagging & Trolling.

    a. "Suicide Bagging" rules are in effect by default. However, the home team has the choice of changing it to "Trolling" or "Overlapping" rules if the opponent is notified of it before the room is opened for the first time.
    d.i. Neither "Suicide Bagging" or "Overlapping" rules are in effect.​
    a. "Suicide Bagging" rules are in effect by default. However, the home team has the choice of changing it to "Trolling" rules if the opponent is notified of it before the room is opened for the first time.
    d.i. "Suicide Bagging" rules are not in effect.​
    e. Overlapping
    e.i. Should a player be overlapped, they must, without affecting the other players, move out of the line of any players, item boxes, and/or ground items within 5 seconds of being overlapped. When this is performed, the player is not allowed to move (minor movement is fine if the player is stopped on a sloped surface, but this is not an excuse to drive near or around any item boxes), use any items, make contact with any item boxes, collide with any ground items, hit any ingame hazards that can cause items to be lost (i.e. thwomps, cars, etc), fall off of the track, and/or gain positions from which they were overlapped in for the remainder of the race. Using the rearview mirror every few seconds will prevent disconnection while overlapped.
    e.ii. An overlapped player must allow any non-overlapped players to hit him/her with items.
    e.iii. If a player overlaps another player due to re-spawning in front of them (as in Lakitu appears holding the player in front of the overlapped player and henceforth), the overlapped player must immediately abide by rule IX. e.i.
    e.iv. If a player is overlapped while under the effects of an item used prior to being overlapped, a penalty will not be given. However they must still abide by rule IX. e.i. when given the opportunity.
    e.v. Players are not allowed to affect any players that are in close range of overlapping them. Rule IX. e.vi. is the only possible exception.
    e.vi. Players close to being overlapped may only take item boxes that are out of the usual line of first place, and may only take said item boxes if there are others readily and easily available in the item set.
    e.vii. Close encounters between players close to being overlapped and the first place player will not be counted as an overlap unless sufficient proof is presented to prove that an overlap occurred. If the player close to being overlapped provides evidence from their perspective that they did not get overlapped, no penalty will be given.
    e.viii. If e.i.-e.vi. are broken while overlapping rules are in effect, a penalty of 10 or 20 points will be given depending on the severity of each incident (assuming sufficient proof is presented). A penalty may not be given if the incident has no effect on the results of the race.

    Reason: http://mkboards.com/forums/threads/...ng-ruleset-removed-from-regular-tracks.27657/
     
    Sane likes this.
  21. Jazz

    Jazz WL Staff

    • Founding Member
    • WL Staff
    Joined:
    Feb 6, 2015
    Messages:
    1,689
    Gender:
    Male
    Location:
    England
    Team:
    βλ
    Update

    Change: Modification of Rule IX c.ii.

    c.ii. If the “Suicide Bagging” rules are in effect and are broken, a penalty of 10 or 20 points will be given depending on the severity of each incident (assuming sufficient proof is presented).
    c.ii. If the “Suicide Bagging” rules are in effect and are broken, penalties of 5, 10, 20 or 30 points will be given depending on the severity of each incident (assuming sufficient proof is presented).

    Reason: There were a decent amount of trolling cases last season where it could have been a -5 or even a -30 so this lead us to change the amount we can give for a penalty case.
    ______________________________________________________________

    Change: Modification of Rule XVI

    2: The higher overall difference (+/-) in total.

    #3: The higher overall difference between those individual matches (ex: Match 1 - A 388-344 B, Match 2 - A 315-417 B; Total - A 703-761 B. B wins).
    #2: The higher overall difference between those individual matches (ex: Match 1 - A 388-344 B, Match 2 - A 315-417 B; Total - A 703-761 B. B wins).

    #3: The higher overall difference (+/-) in total.

    Reason: The council has decided that this change will benefit competition within the league, instead of teams managing to break ties simply by receiving a potentially lucky war in terms of penalties benefiting +/-, for example.
     
    Last edited by a moderator: Feb 9, 2017
  22. Jazz

    Jazz WL Staff

    • Founding Member
    • WL Staff
    Joined:
    Feb 6, 2015
    Messages:
    1,689
    Gender:
    Male
    Location:
    England
    Team:
    βλ
    Update

    Change: Modification of Rule IV. e., and removal of Rule IV. f. (Rule IV. g. will become Rule IV. f., Rule IV h. will become rule IV. g., and Rule IV i. will become Rule IV h.).

    e. Players who make their registration/transfer post after Friday @11:59 PM ET will be ineligible to play that week's match.
    e. Players who make their registration, transfer posts, or FC updates after Friday @11:59 PM ET will be ineligible to play with those updates for that week's match.
    f. Any FC updates must be completed before a match starts.

    Reason: Once an issue came up last season where someone posted their FC update very close to the match start time, we noticed that this rule was very vague so due to a vote happening, the council felt that FC updates should have the same deadline as registration and transfer posts as there won't be any more confusions with this new rule happening. This means that Rule IV. f. will no longer be needed.
    ______________________________________________________________

    Change: Addition of Rule X. f.

    f. If a player disconnects during any race where the sandbaggers are at least one lap behind by the end of the race (with proof), they will be given the equivalent spot of the lowest runner (for example, 8th place in a 5v5 with 2 sandbaggers).

    Reason: The council has decided that this change will benefit the competition since we feel that if someone DCs during a race, they do not deserve to get the last position when there are two designated baggers competing for the shock going backwards.
     
    Last edited by a moderator: Feb 9, 2017
  23. s

    s pavement

    • Founding Member
    Joined:
    Jul 13, 2013
    Messages:
    799
    Team:
    NY
    Update

    Change: Modification of Rule XV. f.

    f. The team with the better Win-Draw-Loss Record on the leaderboard is the higher placing team.
    f. The team with more points on the leaderboard is the higher placing team.

    Reason: Community poll presented a majority opinion in overturning the previous rule.

    Subsequently:

    Change: Modification of Rule XVI. #1

    Should two or more teams tie on points, the first check in determining a winner would be:

    #1: The higher number of points.
    #1: The higher overall Win-Tie-Loss record.

    These rule updates apply to both Regular Tracks and Custom Tracks.
     
    adagify, Aditya~, Skitty and 3 others like this.
  24. Doyy

    Doyy

    • Founding Member
    Joined:
    Jul 28, 2013
    Messages:
    60
    Update

    Change: Addition of rule XIII d. and XIII d.i.

    d. Players may not abuse Dolphin to gain any type of advantage over other players.
    d.i. If a player gets caught abusing Dolphin, rule a.i. will come into effect. Additionally, said player will receive a ban of 2 years and is forbidden from using Dolphin indefinitely. After the ban has been served, the player will be placed on the conditional participation list permanently.

    Reason: Since Dolphin is heavily prone to being abused, we want to give as little leeway as possible without banning Dolphin entirely. In addition, a new key has been added to the conditionals list, indicating that a player has been put on for the misuse of Dolphin.
     
    Last edited: Jun 15, 2017
    Ash, twingy and Delecto like this.
  25. Jazz

    Jazz WL Staff

    • Founding Member
    • WL Staff
    Joined:
    Feb 6, 2015
    Messages:
    1,689
    Gender:
    Male
    Location:
    England
    Team:
    βλ
    Update

    Change: Modification of Rule X. b.i

    b.i. They will be compensated with 15 points for the GP. Rule X. a. would not apply.
    b.i. They will be compensated with 15 points for the GP if their current GP score, with the additional compensation from rule X. a., does not exceed 15 points.

    Reason: The rule itself was hard to understand, contradicted another rule in the ruleset and it was shown due to the fact a lot of wars have been done where people give themselves 15 even if they got very close to 15 points before they dc'd. For example, I dc'd with 13 points race 2, I would not give myself 15 points, I would give myself 19 points due to it being 13+3+3 = 19. This rule was modified to be made clearer to people when reading this rule during wars.

    Change: Addition of Rule VII. i.

    i. After a reset, the host will wait a maximum of 8 minutes for players to join the room. If stalling is evident after all the players are in and room stability is good enough, a strike and then a host ban will ensue. This ban is independent on who the host was, it only matters if it's the same team both times.

    Reason: Throughout the past season there has been a lot of host teams making the other teams wait a very long time before starting, was shown during CTD2 as well as RTD3. This means that after resets, teams have only 8 minutes to join the room unless mutually agreed to wait for subs or other reasons. This would prevent teams to stop stalling which was manipulated most of last season.

    Change: Modification of Rule VII. e.

    *e. The host must allow a maximum of 20 minutes after the scheduled/agreed start time for players to join the room and start it after that time frame unless both teams are in agreement to start sooner or wait longer.
    *e. The host must allow a maximum of 15 minutes after the scheduled/agreed start time for players to join the room and start it after that time frame unless both teams are in agreement to start sooner or wait longer.

    Reason: Council mutually agreed that 20 minutes is too long for a default wait and could also benefit teams that would try to stall.
     
    Last edited: Aug 24, 2017
    Alessandro, laki, StarBoo and 3 others like this.
Thread Status:
Not open for further replies.

Share This Page