And tell me which pokemon game we would be attempting to accurately simulate with this solution?
How is removing a mechanic not altering it?We're not altering a game mechanic by not implementing the glitch. We're simply ignoring it.
Because we know how it's s'posed to work, and have concrete evidence (D/P) that this is not how the game is intended to be. It's not altering a mechanic, like increasing a moves Accuracy or Damage, but just ignoring it because we have a basis of how it works.
By the way, is there evidence that the U-Turn/Pursuit mechanics that were changed in Plat weren't glitches in DP?
"Deal with it" is a very effective way of correcting issues in the metagame.
I don't think programming a glitch into shoddy is maintaining game mechanics, and by extension I don't think ignoring the glitch is altering game mechanics. Who said "game mechanics" include errors in the programming?
Does Fire Fang hit through Wonder Guard? Yes.I'll admit I probably should have said that about the moves. But you're looking at it a little too literally. Yes, maybe they do say something along the lines of this: "Hypnosis was way too accurate in DP, let's lower it back to where it was." They don't say this: "Pursuit has been working fine since we added it, but don't you think we could spice it up and make it activate glitchy weather?"
By the way, is there evidence that the U-Turn/Pursuit mechanics that were changed in Plat weren't glitches in DP?
"Deal with it" is a very effective way of correcting issues in the metagame.
I don't think programming a glitch into shoddy is maintaining game mechanics, and by extension I don't think ignoring the glitch is altering game mechanics. Who said "game mechanics" include errors in the programming?
if we are going to do that we should just forget the glitch entirelyuh, why can't both people be able to cause this magnificent play of field control?
seriously...i know it's not 100% true to the game, but I'd argue that this makes the glitch both more usable and more preventable, and even better NOT random.
Is there any scenario that evolves that destroys any hint of a playable game if we let this wonderful move work on both ends?
is that more altering than it is to remove the wonderfulness of acid rain? I believe not because it's still true to the game effect, it's just that it's also easier to start
So now people want to allow this glitch because it is in the game yet still want Double Team banned? Where's the consistency?
We already ban things that are "bad" for the metagame (Double Team, Garchomp, etc...) so what's stopping us from doing the same thing here?
Again, we don't change game mechanics. That's where we draw the line.So now people want to allow this glitch because it is in the game yet still want Double Team banned? Where's the consistency?
We already ban things that are "bad" for the metagame (Double Team, Garchomp, etc...) so what's stopping us from doing the same thing here?
We can control what you bring into battle. We can't change what happens when we get there.
It really is not Smogon's place to decide what is meant to be in the game and what isn't. Going back to my earlier example, if Smogon decides "the special/physical split was not meant to be in the game," should we reverse it? Simply put, no.
@RB-Golbat: Yes we can. What about sleep clause? Shoddy makes it so that when you use a move that can sleep when something's already asleep it fails, correct?
Which is why people (obi and I) believe that sleep clause is implimented wrong, just as with evasion and OHKO clauses. if you break those clauses, than instead of the move failing, the game should end right there and whoever broke the clause loses.
Freeze clause is something i have a problem with though. Currently, the only place it exists is in Pokemon Battle Revolution. I would have no problem with removing Freeze clause from the ladder since it is impossible to regulate that like the other clauses.
In the Platinum Battle Tower, my Flygon still got hit with Pursuit even though it used U-turn first.Well, Hypnosis accuracy dropped, U-turn no longer locks a pokemon into the move with a choice item, and Pursuit no longer hits U-turners (oh snap, one related to Pursuit).
I'd like to ask to what end do these glitch implementations go? At what point do those in charge stop and say "maybe we should not add this?" Where does the line get drawn? It's obvious that these "Acid Weather" conditions were not meant to be triggered by Pursuit and that a Pokemon's ability was not supposed to deal damage during these conditions.
No, I was using a Scarf Flygon. I don't remember what I faced exactly, but it was nothing that could possibly outspeed me.Was the Pursuit user faster? Pursuit still has a 0 priority against anything normal.
...and another person brought up just banning Pursuit when it would cause the glitch.Why is there all this talk about banning Pursuit? Why don't we just do what any person in any game would do when given this situation. "Ban" the glitch. In SSBM there were game altering glitches like the Ice Climber's freeze glitch. It was in the game, but they banned it because it was unfair. Why not "ban" this glitch?
Would it be too unconventional to only ban pursuit in the situation that would cause the weather glitch? If it is found to be broken. I believe the glitch would only be banned on "brokeness" ground though.
No, I was using a Scarf Flygon. I don't remember what I faced exactly, but it was nothing that could possibly outspeed me.
You're missing the point, not implementing this would make the cartridge metagame so drastically different from the shoddy metagame that none of the sets in the strategy dex or even the banlists we create would be relevant.How many people play Shoddy to enjoy a 100%-accurate Pokémon DPP battle simulation, truthful to the cartridge in every way?
How many people play Shoddy to enjoy a balanced, strategic, competetively-viable Pokémon metagame?
With the glitch in the equation, the two have become mutually exclusive.
Implementation of the glitch will turn the metagame on its head, not to mention slashing competetive viability by giving one player a distinct advantage from the get-go. Of course we could ban Pursuit, or (since move bans are practically unprecedented) ban all Pursuit users, or revert back to D/P - any of which would still result in a massive metagame stir-up.
Not implementing the glitch will mean we aren't playing Pokémon, but rather a strange look-alike that's almost the same, except it happens to be competetively viable as well.
Give the masses the choice between two ladders. One is a Pokémon simulator, pure and complete to the letter, faithful to the cartridges. The other is a fake, modded, glitchless copy - a competetively-viable, made-up game that's fun to play. Let the people who are using the simulator decide which simulation they better enjoy. Majority really should rule on this one.
Of course, no purist will ever agree to such a test - after all, the Smogon community will want what Smogon's philosophy tells them they want, right?
I've had a back and forth with Veedrock on this since he's not into the "do this and you lose" method of clause enforcement. Instead of enforcing the clause this way, what if we just had Pursuit fail when it would trigger the glitch? Yes, it conflicts with my desire to change Sleep Clause's enforcement, but at least it's another option.Okay, earlier itt, one person made a reference to the Ice Climbers freeze glitch from SSBM...
...and another person brought up just banning Pursuit when it would cause the glitch.Why is there all this talk about banning Pursuit? Why don't we just do what any person in any game would do when given this situation. "Ban" the glitch. In SSBM there were game altering glitches like the Ice Climber's freeze glitch. It was in the game, but they banned it because it was unfair. Why not "ban" this glitch?
This got me thinking. Why can't we just clause the glitch?Would it be too unconventional to only ban pursuit in the situation that would cause the weather glitch? If it is found to be broken. I believe the glitch would only be banned on "brokeness" ground though.
Let's add a clause that makes anyone that triggers the glitch automatically lose. We won't need to simulate what happens during the glitch; all we have to do is establish the conditions for triggering the glitch, and if those conditions are satisfied, the Pursuit user loses. That way we can save some work in implementing the glitch, avoid banning moves/Pokemon, not have to deal with the harmful side-effects, and still stay true to the mechanics.
Of course, there's still the issue of selecting the "host," or the battler to impose those conditions on. Whomever is selected as the host for the battle could be at a disadvantage. Is there a fair way of selecting the host? Should it be random? Should it be based on who clicks the "Find Match" button first? Should it be based on something else?