World Clan League Rules S6

1. Rosters

1.a. Teams are only permitted to use players who are present within their teams registration thread. Teams found guilty of using unregistered friendcodes will have those players points discounted from any previous wars and may be disqualified at staff discretion.

1.b. Registered players can transfer between teams once per season only, with the exception of players who were registered with teams that have died.

1.c. Players found guilty of representing any team that they are not registered with may be banned at staff discretion.

1.d. Teams found guilty of using banned players may be disqualified at staff discretion.

2. Player Registration

2.a. Players who attempt to register for more than one team may be banned at staff discretion.

2.b. Players found guilty of representing more than one team during a season (excluding authorised transfers) may have the points they accumulated for any such teams in previous wars cancelled and may be banned at staff discretion.

3. Mii Names

3.a. Players points will not be counted towards their teams score and/or individual totals should they play using a different name/alias to the one that they registered, unless the alias is declared within 24hrs after the wars completion.

3.b. Players are not permitted to play using names that are registered by any other member of their team or 2nd team or names that are offensive or insulting towards other players/members or teams.

4. Lineups

4.a. Teams can name a maximum 9 player line-up and any 5 may represent that team for any GP, with the exception of reopened rooms (see rule 8.b).

5. War Rules

5.a. All wars are 5v5, should a team have less than 5 players then they are to play with however many they have without their opponents being obligated to drop players/points.

5.b. War duration is 3 GP's (or 12 races).

5.c. Voting for courses is permitted but repeating courses is not allowed. Players responsible for causing a repeat course selection over the 3 GP’s (12 races) through voting (excluding random) will incur a 20 point war penalty for their team per repeat.

5.d. Players found guilty of using any known course glitch (Mushroom Gorge, Grumble Volcano, Wario's Goldmine) or any unknown course glitch considered to be unfair will incur a 50 point war penalty for their team.

6. War Times

6.a. Wars are to take place at the WCL scheduled time unless both teams are in agreement to play at a different time.

6.b. Should a scheduled war coincide with a countries national or religious holiday which would effect the availability of a teams players, then both teams are to play at a mutually agreed time or a time set by the division administrator should both teams be unable to agree on a mutual time.

7. Hosting

7.a. Hosting teams must provide the opposition with a host code atleast 10 minutes before the room is due to be opened or the host and/or team may be banned from hosting at staff discretion.

7.b. Should a hosting team fail to open the room within 10 minutes from the scheduled time, they may lose that war by forfeit and the host and/or team may be banned from hosting at staff discretion.

7.c. Should a hosting team open the room earlier than 10 minutes before the scheduled time without consent from the opposing team, then the host and/or team may be banned from hosting at staff discretion.

7.d. The hosting team is to allow a minimum of 10 minutes joining time for missing players after the room has been opened, or 10 minutes after the scheduled time if the room was opened earlier than the scheduled time, unless consent from the team who are missing players is given to start. Hosts and/or teams who start without waiting 10 minutes for missing players without consent, may lose that war by forfeit and/or be banned from hosting at staff discretion.

7.e. The host must start the GP promptly after 10 minutes has passed from the time of opening the room, or 10 minutes after the scheduled time should the room be opened earlier than the scheduled time, unless consent from the opposing team has been given to wait longer. Hosts and/or teams who do not start the room promptly may be banned from hosting at staff discretion.

7.f. The host should wait a minimum of 1 minute and a maximum of 5 minutes between GP's, unless consent from the opposition has been given to resume earlier or wait longer. Hosts and/or teams who start the room before 1 minute or after 5 minutes without consent may be banned from hosting at staff discretion.

7.g. Should hosts disconnect the room intentionally without consent from the opposition then the host and/or team may be banned at staff discretion.

7.h. Should disconnections be frequent with a particular host then the host player may be banned from hosting at staff discretion.

7.i. Should teams report a considerable amount of room lag with a particular host then the host may be banned from hosting at staff discretion.

8. Disconnections

8.a. Should a player disconnect before the commencement of the countdown of the 1st race then the GP must be restarted, unless consent from the team whos player disconnected is given to resume. Should the host fail to restart without consent, then the GP is to be replayed if it is requested by the team who didn't consent and the host team may be banned from hosting at staff discretion.

8.b. In the event of a GP being restarted, both teams must restart with the same lineup that they had at the start of the GP, unless teams consent to lineup alterations/substitutions. Should a team fail to revert back to their original lineup without consent, then any players who were not in the original lineup will have their points cancelled and their team may face further punishment at staff discretion.

8.c. Should a player be disconnected during the 1st or 2nd races with less than 15 points, or between the 1st and 2nd races with less than 15 points, then that player will score 15 points for that GP. If the player has 15 or more points, then the players points prior to their disconnection will be counted providing proof can be presented or both teams are in agreement.

8.d. Should a player be disconnected between the 2nd and 3rd races, or during the 3rd or 4th races, then the players points prior to their disconnection will be counted providing proof can be presented or both teams are in agreement.

8.e. Should the host be disconnected, all players points prior to and including the race in which the disconnection occured in will be counted, provided proof is presented from a player who completed the race or both teams are in agreement.

8.f. Should a host be disconnected and no proof of scores prior to the disconnection can be provided, then that GP is to be replayed.

9. Player Shortage

9.a. Teams will be given 10 points per missing player at the commencement of any GP.

9.b. Teams who frequently fail to gather 5 players for WCL wars may be disqualified at staff discretion.

10. Substitutions

10.a. A maximum of 5 minutes is allowed for clans to make substitutions, after which time the GP must be started prompty unless consent to wait longer is given from the opposing team.

10.b. The host must not start the game before the allowed 5 minutes waiting time should a player from the opposing team be missing, unless consent from the opposing team is given to start. Teams who resume the game with an opposing player missing before the allowed 5 minutes waiting time without consent may lose that war by forfeit and/or be banned from hosting at staff discretion.

11. Tags

11.a. Players are to use similar tags to those on the same team as them at either the beginning or end of their names, failure to display tags correctly will incur a 10 point war penalty for their team.

12. Forfeiting

12.a. Forfeits are scored as 200-0.

12.b. Teams who forfeit during a season without good reason may be disqualified at staff discretion.

13. Results

13.a. The host team must post the war result within 24hrs of completion if the result has not already been posted by the opposition, failure to do so without good reason may result in that team being disqualified at staff discretion.

13.b. If neither team can provide proof of a full result then proof of any completed races may be counted as the final result at staff discretion.

13.c. If there is no picture proof of a result yet evidence is presented supporting the outcome of a war then that war may be scored as a forfeit win at staff discretion.

13.d. If evidence is presented supporting a claim that a team is witholding pictures to prevent the opposition from reporting the result then the team witholding pictures may lose that war by forfeit at staff discretion.

14. Inconclusive Wars

14.a. Should a team have an acceptable reason for not completing a war then any races remaining will be played at a mutually agreed time before the next scheduled WCL war. If a time can not be agreed, then they are to play at a time set by staff.

14.b. The scores for any completed races may be counted as the final war result if a team is unwilling to complete a war without good reason at staff discretion, providing the result does not favour the team unwilling to complete the war.

14.c. Teams unwilling to complete a war without good reason may lose that war by forfeit at staff discretion.

15. Replays/Reschedules

15.a. Any replays/reschedules are to be played at a mutually agreed time before the next scheduled WCL war. If a time can not be agreed, then they are to be played at a time set by staff.

16. Cheating

16.a. Persons found guilty of cheating in the WCL or any other official war or tournament will be banned and all points accumulated from any previous wars will be cancelled.

16.b. Persons found guilty of cheating in the WCL or any other official war or tournament may cause the disqualification of their team and/or banning of other members of that team at staff discretion.

16.c. Cheating accusations are to be presented to the council by the accusing teams council member for investigation. Accusations made by other means may result in the person(s) being banned from the WCL site and/or competition at staff discretion.

17. Conduct

17.a. Players who personally insult others within the WCL forum may be banned from the WCL site and/or competition at staff discretion.

17.b. Players who are racist, prejudice, threatening or bullying towards others within the WCL forum or by any other means may be banned from the WCL site and/or competion at staff discretion.

17.c. Participating teams found guilty of hacking other participating teams websites, forum accounts, or any other sensitive information may result in the individuals concerned being banned and/or team disqualification at staff discretion.

18. Lagging

18.a. Players found to be severely lagging resulting in an unfair disadvantage to their opponents may have their points for that war cancelled at staff discretion, if video proof is presented by atleast 2 different persons within 24hrs after the wars completion.

18.b. If it is proven that a player has lagged intentionally, then that players points from any previous wars may be cancelled and the player may be banned at staff discretion.

19. Exploitation

19.a. If it is proven that a player or team has exploited any of the WCL rules, forums or mechanics of the game then they may be banned or disqualified at staff discretion.

yay first reply...

didn't ask this before...

@ Rule 7a, when I'm hosting, I believe I start every GP in first, so how am I supposed to know whether someone behind me has d/c ed before or after the countdown?
In fact, in my recent room race, when someone d/c from the room sometimes I never knew until the race finishes unless I fell to last place and notice no one is behind...
any advice on this?

without the use of voice coms it is harder to know if somebody has dc'd, witch is why I believe division chat boxes are necessary. As not all clans use voice comms, and it is impractical for every member of the squad to have the hoster on an Instant messenger.

1- during the loading of the race, there is a "turing" view of the start grid. here you can see all the racers... that's first tip

2- just after the start you look behin yourself... not 100% efficient but can help

3- voice com as Thorny said is the best way to know

4- being in a multi-IM conversation with all your opponents or at least someone in contact with them but not playing

And if it starts to lag loads that could be a sign you lost some 1

yeah
if voice chat is possible - the best way to alert a host would be through use of it / msn or something.

alternatively the team that suffered the DC may know about it and to alert the other team could drop out from the race. Surely they will notice that there are only 5 people racing!

However, this method would need to be carried out with caution because if this is used to force a restart on a gp, then the team will be punished.

That rule won't work since you can be lapped on GV2 easily. Just get hit twice, maybe even by the last racers who are a little behind, and fall off the track, go wide to get an item.
It happened to one of us once, so he'd be disqualified if he got a bullet bill and hit the 1st place?

I actually wanted to come up with this exact same rule a few weeks ago but it just doesn't work properly.

that rule you proposed has been discussed on mkwii.com. it won't be introduced.
i agree that it is a dodgy tactic but a highly risky one. and as such it will be reserved for those clans with questionable racing ability.

I just remember someone saying that staying behind or even going backwards to attack the top racers at spots like narrow bridges is "in the nature of the game" and therefore won't be punbished.
After reading that I dropped out of our main lineup to be a sub because I dislike it as much as you do, apparently.

trolling/sandbagging has never been proven to be gamebreaking nor easy to do.

I wont go into more details cuz I already discussed about this on mkw.com's WCL thread.

We just came to the conclusion that , as much as that technique goes against racing ,and effective when succeded , both are hard to perform , especially with smart frontrunners.