1. Are you a supporter that wants to change your forum name? Just ask an administrator or moderator with a sparkly name!
    Dismiss Notice
  2. 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
  3. 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 CT WL Ruleset Changelog

Discussion in 'Help, Information, & News' started by Fruitz, Jun 21, 2015.

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

    adagify 私はキルアアが大好き

    • MKBoards Supporter
    Joined:
    Nov 5, 2014
    Messages:
    1,000
    Location:
    Australia
    Team:
    Yn, Qnτ, ωZ
    Update

    Change:
    Modification of Rule VI. b.ii. & Addition of Rule VI. b.ix.

    b.ii. 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.ii. If a host is caught with 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.ix. Unless a different setting is mutually agreed upon by both teams, If a host is caught with Thundercloud Autofire set to "OFF" 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.

    Due to discussion upon CT Council for Mutual Agreements regarding TC Auto-fire settings, we have decided to implement this change, however this is only for TC Auto-Fire (not to be confused with TC to MEGA).

     
    Last edited: Jan 14, 2017
  2. adagify

    adagify 私はキルアアが大好き

    • MKBoards Supporter
    Joined:
    Nov 5, 2014
    Messages:
    1,000
    Location:
    Australia
    Team:
    Yn, Qnτ, ωZ
    Update

    2 tracks have been banned:

    - Alpine Skyway: Various of out of bounds errors have been found within the track, such as going through the clouds when small, and being counted out of bounds on the spiral turn after the ramp.

    - GCN Rainbow Road: If you get bumped before the spiral turn at the end of the track, you'll be falling for a really long time as there is no fall boundary, therefore giving an instant last place to the player who witnesses it.
     
    Yax, tylerr and DatRaptor like this.
  3. adagify

    adagify 私はキルアアが大好き

    • MKBoards Supporter
    Joined:
    Nov 5, 2014
    Messages:
    1,000
    Location:
    Australia
    Team:
    Yn, Qnτ, ωZ
    Update

    This update is a direct mirror of the changes stated here.
     
  4. adagify

    adagify 私はキルアアが大好き

    • MKBoards Supporter
    Joined:
    Nov 5, 2014
    Messages:
    1,000
    Location:
    Australia
    Team:
    Yn, Qnτ, ωZ
    Important Update

    Change: Removal of Rules IX. e.-e.viii. Section name also changed to Suicide Bagging & Trolling.

    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: The majority of the players participating in the CT Division(s) have voted to remove Overlapping from the rule-set, due to many issues regarding this type of rule. This had already been removed in RT Divisions, and now it's safe to say it's been eliminated from the Wiimmfi League entirely.
     
    lina, tylerr, K1NG and 2 others like this.
  5. adagify

    adagify 私はキルアアが大好き

    • MKBoards Supporter
    Joined:
    Nov 5, 2014
    Messages:
    1,000
    Location:
    Australia
    Team:
    Yn, Qnτ, ωZ
    Update

    Change
    : Modification of Rule VIII. e.

    e. Players may not use the following glitches/shortcuts:
    - Alpine Skyway
    - BassBasher City
    - Blue Loop
    - Disco Fever
    - Haunted Woods
    - Iceway (1)
    - Iceway (2)
    - Kinoko Cave
    - SNES Donut Plains 3
    - Subspace Factory
    - Volcano Beach 2
    - Water Island (1)
    - Water Island (2)
    - Yellow Loop
    e. Players may not use the following glitches/shortcuts:
    - Alpine Skyway
    - BassBasher City
    - Blue Loop
    - Castle of Darkness (Bagging Shortcut)
    - Disco Fever
    - Haunted Woods
    - Iceway (1)
    - Iceway (2)
    - Kinoko Cave
    - SNES Donut Plains 3
    - Subspace Factory
    - Volcano Beach 2
    - Water Island (1)
    - Water Island (2)
    - Yellow Loop

    Reason: A new shortcut/glitch has been found in the following track:

    - Castle of Darkness

    This shortcut/glitch is only viable with bagging/going backwards. It is banned because it triggers a position glitch for the whole race, showing the bagger in 1st place for the other racers, therefore players who are actually first will not be getting blue shelled, while also getting items which they shouldn't be getting. Link of video of the shortcut/glitch is attached to the name of the track to show what it is and why it is banned.
     
    Last edited: Mar 24, 2017
    Killua likes this.
  6. Jazz

    Jazz WL Staff

    • Founding Member
    • WL Staff
    Joined:
    Feb 6, 2015
    Messages:
    1,721
    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
  7. adagify

    adagify 私はキルアアが大好き

    • MKBoards Supporter
    Joined:
    Nov 5, 2014
    Messages:
    1,000
    Location:
    Australia
    Team:
    Yn, Qnτ, ωZ
    Update

    1 track has been banned:

    - Disco Fever: Position glitches have been found evident in this track, therefore interfering with results of matches as some people won't receive the items they should be and could avoid getting hit by items they should be getting hit by (red shells & blue shells). This has occurred in two previous WL matches, one where we have video evidence of here (1:40:55). This occurs because the game judges a said player of doing the ultra glitch in disco fever due to lag, but is actually not, therefore showing them as last on other peoples screens.
     
    eZiire, BlueShadow, c and 4 others like this.
  8. adagify

    adagify 私はキルアアが大好き

    • MKBoards Supporter
    Joined:
    Nov 5, 2014
    Messages:
    1,000
    Location:
    Australia
    Team:
    Yn, Qnτ, ωZ
    Update

    2 tracks have been banned:

    - Comet Starway: A glitch has been found where If you happen to fall off the track near a zapper, it is possible that you will respawn onto the zapper continuously, pushing you off of the track over and over, therefore giving you an instant bottom position because of it. This has occurred in a few past WL matches, proving that it is a common bug, hence why it is being banned. Video can be found here.

    - Helado Mountain:
    A glitch has been found where if you fall off in the alternative route of this track, your lap will not count, therefore giving you an instant bottom position. This has also occurred in past WL matches. Gif can be found here.
     
    Killua likes this.
  9. adagify

    adagify 私はキルアアが大好き

    • MKBoards Supporter
    Joined:
    Nov 5, 2014
    Messages:
    1,000
    Location:
    Australia
    Team:
    Yn, Qnτ, ωZ
    Update

    Change
    : Modification of Rule VIII. e.

    e. Players may not use the following glitches/shortcuts:
    - Alpine Skyway
    - BassBasher City
    - Blue Loop
    - Castle of Darkness (Bagging Shortcut)
    - Disco Fever
    - Haunted Woods
    - Iceway (1)
    - Iceway (2)
    - Kinoko Cave
    - SNES Donut Plains 3
    - Subspace Factory
    - Volcano Beach 2
    - Water Island (1)
    - Water Island (2)
    - Yellow Loop
    e. Players may not use the following glitches/shortcuts:
    - Alpine Skyway
    - BassBasher City
    - Blue Loop
    - Castle of Darkness (Bagging Shortcut)
    - Crossingville
    - Disco Fever
    - Haunted Woods
    - Iceway (1)
    - Iceway (2)
    - Kinoko Cave
    - SNES Donut Plains 3
    - Subspace Factory
    - Volcano Beach 2
    - Water Island (1)
    - Water Island (2)
    - Yellow Loop

    Reason: A new shortcut/glitch has been found in the following track:

    - Crossingville (37:00)

    As shown in the video attached to the name of the track, see Jose's point of view as he takes the shortcut, this shortcut does not count his lap, however, it causes a position glitch on all of the other players screens, showing whoever is actually 1st in 2nd place, whoever is 2nd in 3rd place, etc. This will cause items to not hit the player, such like blue shells, while players will also be receiving items they potentially shouldn't be receiving.
     
    Last edited: Mar 24, 2017
    xNight likes this.
  10. adagify

    adagify 私はキルアアが大好き

    • MKBoards Supporter
    Joined:
    Nov 5, 2014
    Messages:
    1,000
    Location:
    Australia
    Team:
    Yn, Qnτ, ωZ
    Update

    4 tracks have been unbanned:

    - Alpine Skyway
    - Faraway Land
    - Kirio Raceway
    - Super Sky Courtyard


    Reason: Due to majority council vote, we have agreed to unban these tracks as the reason they were banned for originally don't cause a huge impact on the race(s) and are avoidable.

    ______________________________________________________________


    1 track has been banned under special occasion:

    - Undiscovered Offlimit: As witnessed in the previous CT FFA, there were a lot of spots lagged at the end of the race in this track. This has been evident to be a permanent issue with the track and will occur in 12 player rooms. This track is only banned in 6vs6 matches.
     
    ~Maidvelia❤~, Tyler and Killua like this.
  11. adagify

    adagify 私はキルアアが大好き

    • MKBoards Supporter
    Joined:
    Nov 5, 2014
    Messages:
    1,000
    Location:
    Australia
    Team:
    Yn, Qnτ, ωZ
    Update

    This update is a direct mirror of the changes stated here.
     
    s likes this.
  12. adagify

    adagify 私はキルアアが大好き

    • MKBoards Supporter
    Joined:
    Nov 5, 2014
    Messages:
    1,000
    Location:
    Australia
    Team:
    Yn, Qnτ, ωZ
    Update

    1 track has been unbanned:

    - Castle of Time

    Reason: The recent CTGP-R update has resolved the glitch(es) which was/were the reason(s) this track was banned.


     
  13. CJ

    CJ

    Joined:
    Jun 14, 2015
    Messages:
    1,125
    Gender:
    Male
    Location:
    CA, USA
    Team:
    Flow
    Update

    Change: Modification of Rule VIII. e.

    e. Players may not use the following glitches/shortcuts:
    - BassBasher City
    - Blue Loop
    - Castle of Darkness (Bagging)
    - Crossingville
    - Disco Fever
    - Haunted Woods
    - Kinoko Cave
    - SNES Donut Plains 3
    - Subspace Factory
    - Volcano Beach 2

    Reason: A new shortcut/glitch has been found in the following track:

    - Star Slope

    As shown, the player is able to skip a large part of the track with a mushroom, and then going back to hit the checkpoint to then continue on, counting the lap. As seen in the gif, Myth hops fairly far over the invisible wall, and onto the other side of the track. The player, skipping a portion of the track has a major advantage over the other racers, giving an unfair advantage. Also, if done incorrectly, the shortcut could potentially cause a position glitch.
     
    DatRaptor likes this.
  14. CJ

    CJ

    Joined:
    Jun 14, 2015
    Messages:
    1,125
    Gender:
    Male
    Location:
    CA, USA
    Team:
    Flow
    Update

    1 track has been banned:

    - Star Slope: Major out of bounds respawn glitches have been discovered, along with the fact of a major shortcut being already banned, which could potentially cause position glitches in the room. You can find the shortcut here, along with major invisible wall respawn problems here and here.
     
    rubified, Typhoon, laki and 4 others like this.
  15. Kneekoe

    Kneekoe WL Staff

    • Founding Member
    • WL Staff
    Joined:
    Jun 13, 2013
    Messages:
    1,066
    Team:
    the bad guys
    Update

    Change: Removal of previous rule VI b.i


    VI b.i.
    If any player is caught using Remove Game Music?, they will receive a penalty of 10 points per race (120 points total if left on for the entire match) until it is turned off.



    Reason: Bypassing this can be done by having multiple silent brstms turned on via MyStuff which, according to the current CT ruleset, will not get penalised.
    In addition, every CT player has access to turning on/off "Remove Game Music" as well as MyStuff.
    Therefore, the usual argument that having no ingame music causes players to hear items (such as blue shells coming for first) better becomes negligible.
     
    MZ, Eon, xSpade24 and 7 others like this.
  16. Stunky

    Stunky Tom | Stunky Staff Member WL Staff

    • Administrator
    • MKBoards Supporter
    • Founding Member
    • WL Staff
    Joined:
    Jul 12, 2013
    Messages:
    1,553
    Gender:
    Male
    Team:
    νι | Valiant
    Wiimmfi FC:
    2237-2605-0050
    As of 2nd November 2017, the following track glitch/shortcut has been banned from competitive play.

    Seaside Resort
    - Any form of attempt to hit the checkpoint a distance away in the off-road of the water section that may advance you to the end of that area of the track (thus cutting off a vast amount of time).

    If the description of the glitch as shown above is unclear to anyone, a video of the Seaside Resort glitch being performed can be seen in the spoiler below, just to clarify what the glitch roughly looks like.
     
  17. Stunky

    Stunky Tom | Stunky Staff Member WL Staff

    • Administrator
    • MKBoards Supporter
    • Founding Member
    • WL Staff
    Joined:
    Jul 12, 2013
    Messages:
    1,553
    Gender:
    Male
    Team:
    νι | Valiant
    Wiimmfi FC:
    2237-2605-0050
    Update

    Re-update of the CTWL ruleset so as rules are officially in... Any past cases with rules where we have claimed "the rules were intended to be changed" will stand with their current verdicts, this is just simply a "some things in this ruleset aren't up to date when they should be" situation.



    Major rewrite of Section IV. (Registration)
    a. Players must register with their own IP address and friend code(s) and not any other participant’s.
    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.
    b. Players may only register for one team, and a thread for that team must exist on MKBoards.
    c. Players may register up to two consoles (or two save-files). If a player is registering more than one save-file, there must be proof that they are both linked to that person.
    d. Players are only allowed to play for the team that they have signed up for.
    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.

    e.i. When a player registers or transfers to a team there must be significant proof of permission from a representative of the destination team (unless they are a representative of said 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 regular tracks (ex: FL + M7), they do not need permission. All other registration update threads may only be made by the player.
    e.iii. Newly registered/transferred players may not participate in wars originally scheduled before their request was made.
    e.iv. The CT 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.
    f. 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.
    f.i. Players may only transfer once during the season.
    f.ii. A player transferring from free agents is the only exception to f., provided they hadn't been registered for a team at any point during the season.
    f.iii. Players may only play one match per WL week, meaning that they cannot play in a W1 match, transfer to a different team, and then play in their new team’s W1 match.
    f.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.
    g. 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).
    h. Teams must have at least 8 correctly registered players by the registration deadline in order to be seeded.

    h.i. Teams who have not signed up by the registration deadline or who have not fulfilled rule III. i. are not allowed to play in WL.

    a. Players must register with their own IP address and friend code(s), not those of any other participant. This means that players must register themselves, as opposed to having team representatives post their player registration for them.
    a.i. Exceptions can be made for players living in the same household, however they must be approved by the council in advance.
    a.ii. Guests are allowed to play during a match, so long as the opposing team is able to confirm that the guest in question is a player registered on MKBoards, and signed up for the correct team.
    a.iii. The council and/or registration admins have the right to decline registrations on the grounds of alt suspicion, and can also delay the processing of a registration if required.
    b. Players may only register for one team per track type, and a thread for the team must exist as a Team Registration within the Wiimmfi League.
    c. Players may register up to two consoles (or two save files).

    c.i. If a player is registering more than one console/save, there must be proof that both are linked to that person.
    d. Players are only allowed to play for the team that they have signed up for.
    e. Players may update their Friend Codes at any time prior to the match.

    e.i. If there is sufficient proof that an update has not been performed in time, the player will be considered ineligible to play and may be punished according to IV. g.
    f. The Wiimmfi League has a mid-season registration and transfer period that takes place between 11:59pm Eastern Time of the Sunday in Week 5, and 11:59pm Eastern Time of the Friday prior to Week 6.
    f.i. Within this window, players may submit one transfer/registration, of which the council have the right to decline.
    f.ii. Transfers within the transfer window cannot be to a team that the player was in during the Preliminary Seedings stage.
    f.iii. Players who perform a transfer and/or registration may not play in matches where the default time is prior to their transfer. This means that, by transferring within the mid-season window, players would not be able to play matches for weeks 1-5.
    f.iv. Players may only play one match per WL week, so if for whatever reason a match is played during the window in advance, the player is not allowed to play for their new team up to that week.
    f.v. Sufficient permission must be provided within any transfer or registration. This includes:
    f.v.i. Valid printscreens of the leader/representative of a team permitting it.
    f.v.ii. A post within the thread by a leader/representative confirming the registration and/or transfer.
    f.v.iii. In the instance of a move between branches of a team (e.g. KG1 to KG2, or Bc RTs to Bc CTs where the person was not prior registered for a team on CTs), the leader may request the transfer themselves.
    f.vi. The council reserve the right to punish players and/or prevent them from being considered suitable to permit transfers for themselves or other players, if they believe that any insufficient permission, or deliberately faked permission, has been given.
    f.vii. The council reserve the right to decline any transfers or registrations. Reasons for this may be (but are not limited to) suspected alts (in which checks must be made) or potential unfair moves (e.g. stacking).
    g. 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).
    h. Teams must have at least 8 correctly registered players by the registration deadline in order to be seeded.

    h.i. Teams who have not signed up by the registration deadline or who have not fulfilled rule III. i. are not allowed to play in WL.

    Reason: Updating the CT Ruleset to include the Season 11 rules for Registration including that of the transfer deadline and other restrictions. This update also changed back the rule in regards to FC Updates, so as they can be done any time prior to the beginning of a match.



    Modification of Rule VI. a.
    a. For players, the following must always be set to "OFF" or "NO" - Remove Game Music?; for hosts of the room, they must have the following settings - Track Availability = Custom Tracks or All Tracks, Specific Engine Class = Normal, Race Count = 4, Thundercloud Autofire = Normal, Thundercloud Effect = Normal, Room Encryption = ON, Available Vehicles = All Vehicles, Host Always Wins Vote = OFF.

    a. Anybody who hosts a room in a Wiimmfi League match on Custom Tracks must have the following settings - Track Availability = Custom Tracks or All Tracks, Specific Engine Class = Normal, Race Count = 4, Thundercloud Autofire = Normal, Thundercloud Effect = Normal, Room Encryption = ON, Available Vehicles = All Vehicles, Host Always Wins Vote = OFF.

    Reason: Removal of any mention of "Remove Game Music?", therefore removing any duties for typical players in this section.



    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: Due to the stalling last season, the council lowered the required amount of waiting time prior to being able to start a room.



    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 will be given to the entire roster of the team. If a second offence occurs, in the same match or a different one, then a host ban will ensue for the entire roster and any remaining home matches will be hosted by the opposing team(s). The host-banned team will still be allowed to determine ruleset and engine class.

    Reason: Due to the stalling last season, the council lowered the required amount of time that a reset could be, and therefore did this with an additional rule.



    Addition of Section XIX. (Playoffs)
    a. Before the start of the season, Team Representatives will be voting for their teams in order to choose between having playoffs or no playoffs. There are 3 choices to pick from this:
    a.i. Best of 3 - Participating in 3 wars where the first team to win 2 wars win the division. The first seed will have a bagging advantage of choosing for the First and Third war.
    a.ii. 7 GP War - Participating in a 7 GP War where the team with the most amount of points at the end of the war wins. The first seed will have have host advantage and engine class choosing for the whole war The first seed will have bagging advantage for four GPs: GP1, GP3, GP5, GP7 while the second seed will have bagging advantage for three GPs: GP2, GP4, GP6.
    a.iii. No playoffs - There will be no playoffs after the ending of the last week which means whoever finishes first wins the division.

    Reason: Added to comply with the new Playoffs formats as of Season 11.
     
    suipthegoat likes this.
Thread Status:
Not open for further replies.

Share This Page