Munya

You're free to go about it, nobody had any objections and I don't see any issues. The test will begin with the end of the month tier changes. Which should go live end of the day today(29th)/early tomorrow

Sorry was waiting on confirming the want to test it again amongst TC. DM me the write up - I'll pass it by TC so they can suggest any potential revisions/review if need be(usually about a daylong process), if there are any I'll let you know if not I'll give the go-ahead to post it.

If and when Gallade gets a nerf it will be trialed again yes.

Late 29th/early 30th whenever I can get around to it and a tournament isn't happening. When is TT?

I'll outsource the writeup to you, I'm of the opinion its been banned long enough to warrant a test at the very least as well.

First, I'm not going to expect any of TC to make a thread before usage movements are actually finalized, things change even if it may seem unlikely. As for your next step, garner enough support from a member of TC to where they will draft a thread for review/posting. Only need to convince one.

The movement thread was just made this morning, nobody has had a chance to propose a discussion. EDIT: OP had been updated with Gallade ban. Still awaiting shaymin post.

They can initiate a vote for a quick ban if necessary, the bar is high for a quick ban though.

Currently still using old cutoff for this season, 4.36% to go either way. Banned to Ubers from OU: Gallade - Discussion thread/ban post. To OU from UU: Salamence - 5.26% OU Usage Banned to BL1 from UU: Shaymin - Discussion thread/ban post. To UU from OU: Seismitoad - 3.31% OU usage Toxicroak - 2.91% OU usage To UU from NU: Gastrodon - 8.09% UU usage Zoroark - 5.44% UU usage Clefable - 4.87% UU usage Tentacruel - 4.85% UU usage To NU from UU: Ditto - 3.91% UU usage Druddigon - 2.08% UU usage Gigalith - 1.65% UU usage Gligar - 4.16% UU usage Mismagius - 3.04% UU usage Venusaur - 4.02% UU usage Xatu - 3.83% UU usage NU Suspect Test: Venomoth - TC approved, discussion thread

We are discussing it.

Its just what was suggest, all I care about in the first 2 months is them being more difficult to have movements on than the last month. We should ideally be going into the seasonal tournament with as stable of a tier as we can so theres no last minute surprise showing up to blindside somebody that maybe had a handle on the season prior to something dropping or rising. Unfortunately updates have partially put a real damper on that but that is out of my hands.

This is within a close enough range to what I was thinking, .25% off(was thinking 5 and 4) but this may actually be better as it keeps something I used as an example for something that would still yo-yo if we just had a straight 5% cutoff in OU(torkoal). This month though we are probably retaining normal seasonal cutoff and going with it after asking the TC. Something that was suggested internally within TC is this in the future: 1st month 1.7 to drop, no rises 2nd month 2.5 to drop no rises 3rd month 5 to drop or rise. Which is where I brought up the yo-yoing thing and why a split would be better. The above is apparently similar to how smogon handles it now? I didn't look into the claim.

It would actually be to maintain the integrity of the next season with two "major?" pokemon in the tiers being banned it doesn't really sound right to ban based off that usage. That said its not guaranteed to happen, it is a question atm, one that I will poll the TC on later but I figured you all could give your input as well.

Then they should have voiced those objections when it was being discussed and the multiple people that were okay with it were talking about it, and they very specifically given time to say no to it when I asked.

Then the TC needs to express an interest in going back.

It was in the may thread

Woops, forgot to update it when I made the announcement that that is not how it works anymore. That said, I am stating, and have stated before that that isn't a thing anymore.

1.7 and 6.7 usage movements don't exist anymore so not sure why you are mentioning those, it would use normal cutoffs next month if it was frozen this month.

If they veto something at least in this particular case it won't be a ban, just a temporary stop since I assume Shaymins existence had at least a minimal effect on Venusaur since its another strong grass type in the tier? To maybe give it time to pick back up some of its momentum or give us time to discuss the eventuality where it might drop.

Raising the usage % is just going to change the bar, instead of stuff hovering around 4.36% changing every 3 months, stuff hovering around whatever % we change to will change every 3 months. Split cutoffs is how you deal with that but I haven't been given a good answer as to what they should be.

Re-opened temporarily, lets assume that both the current pending OU and UU bans go through, what are opinions on freezing the seasonal usage movements until next month? Other options being just doing the movement normally or giving TC the option to maybe veto some usage based movements during this change.

One is a change to fall in line with the official pokemon games, the other is a potentially completely custom nerf, big difference. Just to be clear, I am not saying the pp nerf could never be reverted, I may say its unlikely but I wouldn't say no. I would say its less likely in this particular case than it normally would be, you would need to seek that reversion elsewhere if you want to make a serious push for it.

Keep in mind if this topic is going to happen, devs are always going to prefer path of least effected, so for instance nerfing Sharpness at this point in time directly nerfs Gallade without effecting any other pokemon currently. Changing the PP of recovery moves is something that effects many pokemon, it would be a last resort if ever considered.

If the development team seeks player opinions on it then a thread will be made for it, until that time this isn't the place for it. There is nothing wrong with players suggesting solutions, but in the right time and right place, which this is not.