I like the D
I like the D
What does 'more lax' in this instance mean? You mean more lax than the quickdrop system we have right now? Also does this system only apply for the tier-jumped mon; if so that sounds more complicated than it needs be to keep track of.b) Do nothing, wait for it to fall down naturally but impliment a more lax quickdrop system.
c) Drop it back to its original tier before the jump, regardless of external metagame considerations.
I'm not really sure what 'external metagame considerations' is supposed to imply, but looking at the context here I can only assume it means the metagame shifts that occur from the release of new games within the Generation. So you're saying that if a mon was in BW NU and jumps to BW OU, it gets to go straight back to BW NU if it does drop, but if the mon was BW NU and jumps to OU ~the instant BW2 begins, it needs to drop slowly? If that's the case, wouldn't the window for the mon to jump/drop between different parts of the same Generation be technically really small? Should the mon stays in its home tier for either: (a) a month or (b) until the official usage stats per 3 months comes around [I don't actually know which one you'd apply here] after the new part of the Gen is introduced, it's already become part of BW2 NU and no longer subject to slowly dropping once it jumps to BW2 OU. Not to mention that I don't particularly see a need to segregate parts of the same Generation like this when they're not too wildly different from each other; it's different from separating between entire Generations themselves, where new mons & mechanics are introduced and the lower tiers haven't even been established yet.d) Drop it back to its original tier before the jump, if the jump and drop occur in the same part of the generation (different parts being XY vs ORAS, BW vs BW2, DP vs DPP vs HGSS). If they aren't in the same part of the generation, let it drop naturally.
Wait a second; why would the mon getting a significant change or not suddenly become a factor to whether it gets to drop tiers or not? Pretty sure constant usage and banning sorts those kinds of Pokemon already, as they always have (Hidden Abilities, or tutor moves like ORAS Pangoro). Even if the mon does get "buffed" between its jump and time to drop, I don't see the need to deviate from the scheduled drop; if the mon ends up too strong for its home tier, at least it'll be given a fair chance to be banned. Isn't the suggestion of this newer system more to deal with fluctuating usage trends for Pokemon regardless of whether the mon has been "buffed" or not?Drop back to the original tier if nothing significant has changed with the Pokemon since it rose (i.e. no new legal move, ability or forme). And--what the hell--let it go across sub-generations (fine to drop in ORAS to tier it hasn't been in since XY.
@below yesAgree with Antar's above post, change my vote to C
No, obviously if a mon gets a really good ability (sheer force gatr) that is more likely to impact its usage than a shift between games, but if its a random move like moonblast on Celebi, then it definitely has less impact than a game release. Obviously it will be more rare that some random tutor move corresponding with a rise multiple tiers by a mon (like if Tangrowth randomly got Dazzling Gleam as it moved to OU, it was probably irrelevant), but if we are trusting councils to do it between game changes then we might as well for tutor moves / abilities as well. I meant original C.[
To be clear, people who are agreeing with me but voting C, is C now with my added caveat?
Clause 1 is pretty much how I expected it to go, but Clause 2 puzzles me since I don't really see the point to it. Like this sounds like it requires both the 'former home' tier to declare the mon broken without even touching it at all and for the upper tier to officially acknowledge the mon as part of their tier; why doesn't the 'former home' tier simply resort to quickbanning instead (like they always have), without having to wait for / needing the upper tier's input whatsoever?"A Pokemon that rises more than one tier in a given usage cycle, then drops out of that tier in a later cycle will be placed back in its original tier unless:
- The Pokemon gained a major addition in either movepool or ability that caused it to initially rise."
The second clause is intentionally subjective and should be left up to the tier leader(s) at the time, because it's a "I know it when I see it" type of scenario. Sheer Force Feraligatr is the best example, since it made the Pokemon _that_ much better to jump from NU to UU.
Since Clause 2 looks like it falls to the tier council's judgement, why use that to involve any more tiers than just the respective one to decide the mon's tier placement when quickbanning accomplishes pretty much the same thing with less hassle?