OK so before I get into my new post PLEASE read this one as it goes through tiering policy which is what we use to base bans off of and it shows serv is not ban worthy. I personally put a lot of merit into tiering policy because of how ive been told to properly determine whether to ban something through experience.
================================================================
now ill respond to a few things in other pro ban posts
Rose is consistently one of the better pokemon in the meta because of spikes, utility in sleep powder, and sets like specs that make up for its usage. rose is not a product of serv by any means and there are many teams that can afford to use specs rose in a serv meta.
Also, when looking at specific cases a lot of offensive teams can afford to not pack a servine counter on there, increasing team building diversity. ive personally had a 3 dragons team where the only servine counter-esq mon was alolan grimer that continues to work well in the meta.
if you are asking for rose to be lower on viability rankings pop off but there are incredible logical leaps you have to take to assume rose is only good because of servine.
im gonna respond to these specific points by simbo cause the replay's one is filled with holes and i encourage people to look at what the players do to allow a servine sweep as 90% of the time it is just because the servine user was better or luck (which is explicitly said in TP happens)
3) if servine is being used a defogger to these pokemon you would be able to play around it even easier in game. on paper ofc it looks overwhelming cause ur assuming the serv is carrying like 7 moves. sure birds and fires can be chipped but when they are chipped they are usually clearing a path to the OPPOSING PLAYERS wincon. people arent just sacking these pokemon and servine is not good enough to force people into playing poorly which is not shown in your replays either. other grass types are dogshit cause serv and rose are good yes, shocker. we have also developed into different hazard removers, these then check serv as well because of how meta has developed in a healthy way.
4) no, what antiban people say is that YOU are the ones assuming that serv can do all this stuff on paper when in practice it is balanced and does not fit TP policy of bannable. there are many pokemon that can sweep teams with relative bulk with proper support this isnt a new idea. nfe is a tier built around all these conflicting wincons which is why this specific wincon in serv that isnt as good in practice is not ban worthy.
next point is 1) if you look even before serv got its jump in usage these pokemon were still on the top of viability and 2) serv is NOT still busted with the way the meta is now which in part is due to healthy meta advancement. serv is not dictated usage on a team by any means.
also 3) machoke is another case of teams adapting to serv style teams. you site these steel mons that work well with serv and there is a reason why machoke is a great breaker when people themselves constrict themselves to using serv. a serv team is not perfect and gets overwhelmed by breakers like machoke BECAUSE of their inherent strength and weaknesses. there are more team styles than serv teams and anti-serv teams and you seem to neglect this in most of your posts on this mon. i personally enjoy a tier where prep can be made if people are spamming serv and if they arent to improve the quality of tour games.
===============
also brief responce to ktut
its not that easy to make a serv team if you have to include all these mons simbo is saying you need to which leaves you open to other breakers. serv teams are a specific style that is good in the meta right now, but you can get away with not using a serv and still being fine.
==============
once again i really URGE people to read the WHOLE tiering policy post. this is one of the things we should be basing bans off of. it highlights what we should be looking for in a ban and servine does not fit it.
also as a general add on, please refrain from using perceived metagame benefits when figuring out whether to ban a mon, look at the mon itself not the future as there are multiple rabbit holes you could go down w that
apologies if this post was a bit jumbled, am a tad sick and busy irl but i hope this covers a good bit of stuff and ill try to be open on discord to talk
also rip spelling mistakes cause im not reading over this gang
voting no ban if that isnt clear
voop out
Scapegoated Servine - A Metagame Post
Overview
In this first post, I will not be responding to any posts made by my favorite smoghorse Simbo or any others, I will merely be running down the tiering policy with a possible servine ban in mind. Tiering policy is what tiers use to determine whether a pokemon is ban worthy and will be linked here. Now let's jump right into it!
Uncompetitive
The tiering policy thread defines uncompetitive as "elements that reduce the effect of player choice / interaction on the end result to an extreme degree, such that "more skillful play" is almost always rendered irrelevant." To ban servine under this definition you have to prove that the more skillful player loses games as a direct result of servine while also balancing it with the assumption in tiering policy that "Probability management is a part of the game." Now that that is laid out we have to examine the specific bullet points within the uncompetitive framework.
1) Servine is no where near the same as baton pass and has numerous both defensive and offensive counters and checks, there is a lot of counterplay around servine and if the more skillful player wins on a set turn servine does not magically pull it back for the other persons team, assuming the more skilled player also has an equally good, if not better, team.
- This can be matchup related; think the determination that Baton Pass took the battling skill aspect out of the player's hands and made it overwhelmingly a team matchup issue, where even the best moves made each time by a standard team often were not enough.
- This can be external factors; think Endless Battle Clause, where the determining factor became internet connection over playing skill.
- This can be probability management issues; think OHKOs, evasion, or Moody, all of which turned the battle from emphasizing battling skill to emphasizing the result of the RNG more often than not.
2) There are no external factors that influence whether servine should or should not be banned
3) This is the only place in the uncompetitive section of the tiering policy where servine could be considered ban worthy. However, as previously stated, probability management is a part of the game, and servine's usage of the move Glare is no where near the other listed issues. Not only do many servines not have the ability to even fit glare onto their sets, paralysis has been a part of pokemon for years and servine's counters can still get around it in nearly all cases, goinig against the usage of the words "almost always" that would be needed to ban serv. Also, servines main move, has a fairly high chance of missing, so if you chose to argue down this street you have to look at how the luck is fair on both sides, does not give one player an edge with removing skillful play, and that probability is a part of the game
BrokenNext, the tiering policy thread defines broken as "elements that are too good relative to the rest of the metagame such that "more skillful play" is almost always rendered irrelevant. ". To ban servine under this definition you have to prove that a team without servine is worse than a team with servine or that servines counters are all niche. Now that that is laid out we have to examine the specific bullet points within the broken framework.
1) Many teams do not run a servine and are still fine, while of course an S rank pokemon is splashable in the metagame, it is nowhere near required to use. If anything it is the opposite, when you have the servine vs servine mirrors is where you see battling skill come to play, and in situations where people use to use both rose/serv together they leave themselves open to pokemon elsewhere. This actually causes the metagame to have many diverse cores and offensive pokemon that can stand out on different teams.
- These aren't necessarily completely uncompetitive because they don't take the determining factor out of the player's hands; both can use these elements and both probably have a fair chance to win. They are broken because they almost dictate / require usage, and a standard team without one of them facing a standard team with one of them would be at a drastic disadvantage.
- These also include elements whose only counters or checks are extraordinarily niche Pokemon that would put the team at a large disadvantage elsewhere.
- Uncompetitive and Broken defined like this tend to be mutually exclusive in practice, but they aren't necessarily entirely so.
- Baton Pass was deemed uncompetitive because of how drastically it removed battling skill's effects and brought the battle down to matchup, but it could also be deemed broken because of the unique ways in which you had to deal with it.
- While this isn't always the case, an uncompetitive thing probably isn't broken, but a broken thing is more likely to be uncompetitive simply due to the unique counter / check component. For example, Mega Kangaskhan was deemed broken because it was simply too good relative to the rest of the metagame and caused the tier to centralize around it, but it could also be labeled as uncompetitive because of the severe team matchup restriction it caused by punishing players if they did not pack one of the few obscure counters or checks for it.
2) There are both counters and checks to servine in the current meta. Fire types / haunter / coverage moves on frog are all popular, scarf staravia also exists on the offensive side. On the defensive side teams have grimer / rose / slig / toge. While with the right support and gameplay servine CAN break through these mons, it requires skillful play by the servine user to get to that point. Z moves and niche pokemon also exist to work around servine which is healthy for the meta. Servine does not fit into this category as there are checks and counters to servine that are not niche. If anything servine having some niche counters/checks and common counters/checks makes it healthier in the meta with more diversity and ideas to explore.
3) Servine is not comparable to baton pass or mega kanga because, while one could argue that servine is somewhat centeralizing, servine does not remove battling skill or have obscure checks and counters. I personally believe that there could be more room to explore with servines stats and calcs previously brought up, but servine cannot run all those sets and moves at the same time / its checks are already common in the meta / and S rank pokemon will have some degree of centralization to them inherently
UnhealthyFinally, the tiering policy thread defines unhealthy as "elements that are neither uncompetitive nor broken yet are deemed undesirable for the metagame such that they inhibit "skillful play" to a large extent." Before I go into how to apply this to servine, I will first acknowledge that I personally will avoid using this at all costs as I take the wording of the tiering policy on it very seriously. The tiering policy thread states the following -
I do not believe for a second that banning servine will cause the better player winning over the lesser player at any higher rate nor that there is enough outcry for the ban to come close to calling for that. Now, to ban servine under an unhealthy definition you have to prove that a servine inhibits skillful play and is undesirable for the metagame to a point where it calls for this drastic of a ban. I would also like to reiterate that something cannot be both unhealthy and broken/uncompetitive by definition and for me to ever consider this I would need to see much more community outcry. Now, lets jump into the remaining parts of the unhealthy framework.
- This is the most controversial and subjective one and will therefore be used the most sparingly. The Tiering Councils will only use this amidst drastic community outcry and a conviction that the move will noticeably result in the better player winning over the lesser player.
- When trying to argue a particular element's suspect status, please avoid this category unless absolutely necessary. This is a last-ditch, subjective catch-all, and tiering arguments should focus on uncompetitive or broken first. We are coming to a point in the generations where the number of threats is close to overwhelming, so we may touch upon this more often, but please try to focus on uncompetitive and broken first.
1) Going back to the previous things I have mentioned, probability management is part of the game and servine does require skill to pilot. Also, there are many offensive checks and defensive counters to servine, with Z moves and niche pokemon only increasing this list and the diversity in the meta. While in theory you could argue down this route, I will discourage anyone from doing this because unhealthy should be used sparingly if at all and a servine ban will not even have a provable positive impact on the meta later on. This specific section is vague for a reason, and while that could be used to justify a servine ban, the examples given in the older tiering policy for this section have been a ban on stealth rocks and scald, which cannot be compared to servine.
- These are elements that may not limit either team building or battling skill enough individually but combine to cause an effect that is undesirable for the metagame.
- This can also be a state of the metagame. If the metagame has too much diversity wherein team building ability is greatly hampered and battling skill is drastically reduced, we may seek to reduce the number of good-to-great threats. This can also work in reverse; if the metagame is too centralized around a particular set of Pokemon, none of which are broken on their own, we may seek to add Pokemon to increase diversity.
2) We are not and should not be adding Pokemon and servine ban does not fit inside the "too much diversity" framework. I doubt I need to say more here
tl;dr serv is really good in the meta but doesn't fit into the tiering policy definitions well enough for me to consider voting ban on it in the near future nor will I ever vote ban based on servine having a slim chance of fitting under unhealthy, which has been clearly stated to avoid using.
expect another post from me soonish responding specifically to simbo and others
viper, out o7
================================================================
now ill respond to a few things in other pro ban posts
View attachment 194829
got reqs last night, voting ban unless someone on no ban can actually give a convincing argument about this mon not being super constricting on teambuilding.
Also everybody says to just use rose and fires, yeah? lets look over rose's MU's w/ all the top mons of the meta and what it can do to them, if anything just to prove my point on this shitmon being a restraint on teambuilding. gonna assume standard spdef rather than my fast rose spread that gains a better MU vs 1 variant of serv and stuff that goes to creep it
Oh also i'd like to use this post for my own vr nom when servine innevitably gets banned,
Roselia to Unranked.
Because Imagine giving Seaking an S rank. fuck that. ban servine. the fact that rose got s rank bc of serv, and only serv, means serv's completely broken. and this trashmon rose having 40% usage despite losing to fucking everything good is just more proof that servine's effect on the metagame is a SEVERE detriment.
Rose is consistently one of the better pokemon in the meta because of spikes, utility in sleep powder, and sets like specs that make up for its usage. rose is not a product of serv by any means and there are many teams that can afford to use specs rose in a serv meta.
Also, when looking at specific cases a lot of offensive teams can afford to not pack a servine counter on there, increasing team building diversity. ive personally had a 3 dragons team where the only servine counter-esq mon was alolan grimer that continues to work well in the meta.
if you are asking for rose to be lower on viability rankings pop off but there are incredible logical leaps you have to take to assume rose is only good because of servine.
3) The offensive Bird and Fire Types Argument
All offensive bird and fire type teams still primarily rely on Serv and Roselia as defensive Serv checks, the fact that offensive birds and fire are checks is valid, but nearly all these teams still rely on Serv and Rose as the defensive backbone for their team, and that's primarily for other Serv. Yes, Serv and Rose check other Pokemon. However, every team needs a defensive Glare/Knock/Storm switchin on top of offensive checks and that's why Rose and Serv have 80% total usage in the tier and why every other Grass-type is dogshit. These birds and fires are also really easy to chip down during a game. They all take either 25% from rocks and/or have recoil-based STAB attacks. The odds of them surviving long enough to check serv late game is low and some of my replays showcase this. You also need good hazard removal for these teams and who pairs well with offensive bird and fire types as a good Stealth Rock fogger? Servine.
Total Rufflet Tour Usage in Serv/Rose meta: | 27 | Rufflet | 22 | 5.39% | 45.45% |
How many times was Rufflet paired with Rose/Serv
| 102 | Rufflet / Servine | 13 | 3.19% | 53.85% |
| 218 | Rufflet / Roselia | 6 | 1.47% | 33.33% |
19/22 Uses featured Serv or Rose as a partner.
Rufflet's the easiest one to quantify because its a fairly niche breaker. Pokemon such as Staravia, Monferno, Magmar and Combusken have different roles for teams and the first two are pretty splashable. I'll give you the usage stats though, to prove that even teams with heavy offensive counterplay for Serv still rely on the same defensive Serv or Rose as their defensive checks because you can't get away with just offensive checks.
Total Monferno Tour Usage in Serv/Rose meta: | 2 | Monferno | 149 | 36.52% | 50.34% |
| 3 | Monferno / Servine | 58 | 14.22% | 53.45% |
| 5 | Roselia / Monferno | 55 | 13.48% | 52.73% |
Not as high as Rufflet but about 65% of Monfs are paired with a serv or a rose.
Total Combusken Tour Usage in Serv/Rose meta: | 20 | Combusken | 33 | 8.09% | 45.45% |
| 102 | Servine / Combusken | 13 | 3.19% | 61.54% |
| 146 | Roselia / Combusken | 9 | 2.21% | 22.22% |
21/33, again about 64%
Total Staravia Tour Usage in Serv/Rose meta: | 10 | Staravia | 82 | 20.10% | 48.78% |
| 16 | Staravia / Roselia | 42 | 10.29% | 52.38% |
| 48 | Staravia / Servine | 25 | 6.13% | 48.00% |
67/82, its paired with Serv or Rose.
The point is, offensive checks alone cannot get you by against Serv. They cannot switch into Glare because they lose their entire purpose of being fast breakers if they do, they usually are frail and get chipped easily, and rarely do they survive til the lategame. A lot of the more common breakers such as Monf and Busk also typically sacrifice themselves to chip Pokemon like Marshtomp too. These Pokemon arent used just for serv so they cant survive long enough to consistently act as a check, and thats why nearly all teams with these kinds of offensive counterplay still pack a Serv or Rose.
4) Arguing against some of these antiban posts
I'm too lazy to argue against every specific point raised by people, but if you do have an antiban argument you want to lob my way, tag me on Discord.
A general point I want to make towards all antiban people is that they seem to heavily want to overestimate servs capabilities, then claim that because it doesn't do everything it wants to do, its flawed and healthy. If servines biggest flaw is that it cannot often act as an early game defensive check and wall softener then sweep late game, that supports proban, not antiban. If serv was genuinely capable of shrugging off hits like that early game, switching into a third of the tier, then still pick up three kills late game, there would be no debate. No other Pokemon, except maybe clef, even offers you the ability to play any role from defensive support, wall softener, or wallbreaker/wincon at team preview. Serv lets you pick which role you want it to play at preview and is so good, it can still do multiple roles in a game. No other Pokemon can invest fully into its defenses, while still being one of the most potent breakers in the tier, and it also has the option to luck through checks if all else fails. A lot of my replays showcase this, servine switches into attacks and clicks Knock and Glare early game, then survives long enough to break late game. If you expect it to do all this every game, again, you expect far too much. The fact that serv is capable of so much in a meta which heavily preps for it is proof that its incredibly centralising.
Another general point I want to make is to fully explain how Serv has warped the meta. Many of you cite the argument of 'I can slap a lot of the most viable mons on a team and naturally have multiple checks, both offensive and defensive to serv so it doesnt affect me in builder'. To those people, I'd ask you to look at our top used Pokemon and our VR. Number 1, 2 and 5 of the most used Pokemon in this meta is Serv, Rose and Grimer, 1, 2 and 3 for best defensive Serv checks. Number 3 is Monferno, one of Serv's better offensive checks, 10 is staravia, offensive sets are typically seen as reliable offensive checks, 11 is haunter, then you have two 'checks' in steel types Pawn and Metang at 13 and 14, and then vull, toge and combusken take 18, 19, and 20 respectively. 11 of our top 20 mons in terms of usage are either its best defensive counterplay, decent offensive checks or mons that are seen as checks but aren't. How is Serv still the best Pokemon in the tier despite this heavy level of warping and the fact that half of our top 20 mons in terms of usage check it defensively or offensively? People pack so much counterplay for it, either naturally or consciously, but it's still the best mon in the tier and still is capable of sweeping while performing defensive and wall softening roles.
More importantly, I see people complain a lot about Machoke recently. Why aren't you using Gloom or Quilladin or other defensive Machoke counters? Because you can't. Using any Grass-type that isn't serv or rose heavily weakens your serv matchup to the point where you would have to stack checks upon checks to not outright lose to it and 5 teammates. Servine has warped this meta to heavily favour spdef walls which defensively check it. Roselia and Vullaby are the big two. You need incredibly sturdy defensive serv counterplay because of how easy it is for serv to boost up. No other high ranking offensive Pokemon in the tier can boost and attack with ease like serv does, while weakening its own checks and counters with knock/glare to potentially break past them, or allow a teammate to beat them, later in the game. Plus it then can tank even SE STAB from our strongest special attackers; none of our fast frail special attackers come close to boasting that.
im gonna respond to these specific points by simbo cause the replay's one is filled with holes and i encourage people to look at what the players do to allow a servine sweep as 90% of the time it is just because the servine user was better or luck (which is explicitly said in TP happens)
3) if servine is being used a defogger to these pokemon you would be able to play around it even easier in game. on paper ofc it looks overwhelming cause ur assuming the serv is carrying like 7 moves. sure birds and fires can be chipped but when they are chipped they are usually clearing a path to the OPPOSING PLAYERS wincon. people arent just sacking these pokemon and servine is not good enough to force people into playing poorly which is not shown in your replays either. other grass types are dogshit cause serv and rose are good yes, shocker. we have also developed into different hazard removers, these then check serv as well because of how meta has developed in a healthy way.
4) no, what antiban people say is that YOU are the ones assuming that serv can do all this stuff on paper when in practice it is balanced and does not fit TP policy of bannable. there are many pokemon that can sweep teams with relative bulk with proper support this isnt a new idea. nfe is a tier built around all these conflicting wincons which is why this specific wincon in serv that isnt as good in practice is not ban worthy.
next point is 1) if you look even before serv got its jump in usage these pokemon were still on the top of viability and 2) serv is NOT still busted with the way the meta is now which in part is due to healthy meta advancement. serv is not dictated usage on a team by any means.
also 3) machoke is another case of teams adapting to serv style teams. you site these steel mons that work well with serv and there is a reason why machoke is a great breaker when people themselves constrict themselves to using serv. a serv team is not perfect and gets overwhelmed by breakers like machoke BECAUSE of their inherent strength and weaknesses. there are more team styles than serv teams and anti-serv teams and you seem to neglect this in most of your posts on this mon. i personally enjoy a tier where prep can be made if people are spamming serv and if they arent to improve the quality of tour games.
===============
also brief responce to ktut
its not that easy to make a serv team if you have to include all these mons simbo is saying you need to which leaves you open to other breakers. serv teams are a specific style that is good in the meta right now, but you can get away with not using a serv and still being fine.
==============
once again i really URGE people to read the WHOLE tiering policy post. this is one of the things we should be basing bans off of. it highlights what we should be looking for in a ban and servine does not fit it.
also as a general add on, please refrain from using perceived metagame benefits when figuring out whether to ban a mon, look at the mon itself not the future as there are multiple rabbit holes you could go down w that
apologies if this post was a bit jumbled, am a tad sick and busy irl but i hope this covers a good bit of stuff and ill try to be open on discord to talk
also rip spelling mistakes cause im not reading over this gang
voting no ban if that isnt clear
voop out