Originated from this thread.
On battle platforms like Shoddy Battle and PBR, Sleep Clause is very simple: it is impossible to have more than one pokémon asleep on one team by anything other than Rest.
However, in Wifi matches the Clauses aren't implemented, and the new rule becomes: It is forbidden to break a clause, with the penalty of being disqualified.
This brings some complications with it thanks to the random factors in the game. Freeze Clause is hardly ever used on wifi, simply because there aren't any moves that specifically aim at freezing the opponent, it is merely a side-effect from moves like Ice Beam and Blizzard.
With Sleep Clause it becomes even more complicated as there are both moves that intentionally induce sleep and scenarios in which inducing sleep happens incidentially or is forced. A few examples are Effect Spore, Sleep Talking Psycho Shift or an Encored Sleep Move.
Therefore, the more precise Sleep Clause is:
After reading some of the odd scenario's in the "Sleep Clause: Clarification, or exception"-thread and the heavy discussions about if they break Sleep Clause or not, I think it's clear the current Sleep Clause isn't specific enough for Wifi battles.
So, in this thread:
1. We discuss if a new Sleep Clause is necesarry
2. We try to come up with a better Sleep Clause
3. I try to get the idea of a new Sleep Clause under the attention of some badged members who could actually make some work out of it. With my current postcount I won't get much off the ground myself.
One of my own ideas for a new Sleep Clause is to cap it at a specific percentage:
If choosing a specific move has a chance of 30% or more to induce a second sleep (other than Rest) on one of the opponent's pokémon, it violates Sleep Clause.
However this idea still is very flawed. Forced move scenarios would still get very complicated, and I'm sure a lot of people have better ideas.
EDIT: If a new SLeep Clause should be created, it should at least:
1. Be 100% clear about when it is violated and when not.
The current Sleep Clause has a lot of room for discussion; did the person who broke the rule do it intentionally or not? This should be prevented as much as possible. Ideally, violation of the rule should be mathemathically decidable, for example by putting a percentage-of-happening cap on it.
2. Prevent forced violation of the clause
If it is possible to force a win by letting the opponent disqualify himself, the clause doesn't work properly. That's not the game we're trying to play.
3. Have little to no exceptional cases.
If we have too many exceptions to the rule, it becomes too complicated. If we could keep Rest as the only exception of Sleep Clause, that would be ideal. A percentage-of-happening-cap could work here, too. This way Assist, Metronome and Effect Spore would fall under regular Sleep Clause and be permitted due to not having enough percentage of happening to break the clause, instead of being an exception.
So far we are putting together a list of moves that should or should not break Sleep Clause:
Moves that break Sleep Clause when inducing Sleep
-Dark Void
-Sing
-Hypnosis
-Sleep Powder
-Spore
-Grasswhistle
-Psycho Shift (selected with Sleep Talk)
-Secret Power
-Yawn
Moves that do not break Sleep Clause when inducing Sleep
-Rest
-Effect Spore
-Metronome
-Sleep moves used by a pokémon forced to use it (Encore, Imprison, Torment)
-Sleep moves by a Choiced Pokémon that is unable to switch out (Mean Look, Arena Trap, Shadow Tag)
-Magic Coat
On battle platforms like Shoddy Battle and PBR, Sleep Clause is very simple: it is impossible to have more than one pokémon asleep on one team by anything other than Rest.
However, in Wifi matches the Clauses aren't implemented, and the new rule becomes: It is forbidden to break a clause, with the penalty of being disqualified.
This brings some complications with it thanks to the random factors in the game. Freeze Clause is hardly ever used on wifi, simply because there aren't any moves that specifically aim at freezing the opponent, it is merely a side-effect from moves like Ice Beam and Blizzard.
With Sleep Clause it becomes even more complicated as there are both moves that intentionally induce sleep and scenarios in which inducing sleep happens incidentially or is forced. A few examples are Effect Spore, Sleep Talking Psycho Shift or an Encored Sleep Move.
Therefore, the more precise Sleep Clause is:
This indicates that putting someone to sleep by the effect of Effect Spore does not count as breaking Sleep Clause, but Sleep Talking Psycho Shift does. However, in some cases it's very hard to say if this "by you" rule still applies or not.only one pokemon on your opponent's team at a time can be put to sleep by you
After reading some of the odd scenario's in the "Sleep Clause: Clarification, or exception"-thread and the heavy discussions about if they break Sleep Clause or not, I think it's clear the current Sleep Clause isn't specific enough for Wifi battles.
So, in this thread:
1. We discuss if a new Sleep Clause is necesarry
2. We try to come up with a better Sleep Clause
3. I try to get the idea of a new Sleep Clause under the attention of some badged members who could actually make some work out of it. With my current postcount I won't get much off the ground myself.
One of my own ideas for a new Sleep Clause is to cap it at a specific percentage:
If choosing a specific move has a chance of 30% or more to induce a second sleep (other than Rest) on one of the opponent's pokémon, it violates Sleep Clause.
However this idea still is very flawed. Forced move scenarios would still get very complicated, and I'm sure a lot of people have better ideas.
EDIT: If a new SLeep Clause should be created, it should at least:
1. Be 100% clear about when it is violated and when not.
The current Sleep Clause has a lot of room for discussion; did the person who broke the rule do it intentionally or not? This should be prevented as much as possible. Ideally, violation of the rule should be mathemathically decidable, for example by putting a percentage-of-happening cap on it.
2. Prevent forced violation of the clause
If it is possible to force a win by letting the opponent disqualify himself, the clause doesn't work properly. That's not the game we're trying to play.
3. Have little to no exceptional cases.
If we have too many exceptions to the rule, it becomes too complicated. If we could keep Rest as the only exception of Sleep Clause, that would be ideal. A percentage-of-happening-cap could work here, too. This way Assist, Metronome and Effect Spore would fall under regular Sleep Clause and be permitted due to not having enough percentage of happening to break the clause, instead of being an exception.
So far we are putting together a list of moves that should or should not break Sleep Clause:
Moves that break Sleep Clause when inducing Sleep
-Dark Void
-Sing
-Hypnosis
-Sleep Powder
-Spore
-Grasswhistle
-Psycho Shift (selected with Sleep Talk)
-Secret Power
-Yawn
Moves that do not break Sleep Clause when inducing Sleep
-Rest
-Effect Spore
-Metronome
-Sleep moves used by a pokémon forced to use it (Encore, Imprison, Torment)
-Sleep moves by a Choiced Pokémon that is unable to switch out (Mean Look, Arena Trap, Shadow Tag)
-Magic Coat