Discussion The qb/unban threshold in ND and its effect on Deoxys-Speed

Blitz

Mightiest of Cleaves
is a Member of Senior Staffis a Top Community Contributoris a Top Smogon Discord Contributoris a Battle Simulator Admin Alumnusis a Top Social Media Contributor Alumnusis a Tiering Contributor Alumnusis a Top Contributor Alumnusis a Top Smogon Media Contributor Alumnus
Discord Leader
Alright, let’s officially codify this.

In National Dex, Deoxys-Speed was recently suspect tested down from NDUbers, where it was previously quickbanned in a large slate over 2 years ago. It failed to meet the required 60% threshold, with 58.14% of voters voting to unban it.

Now, if you don’t see what’s currently wrong with this, it’s the fact that the council can use this to quickban a Pokémon, and retest it in the tier with a 40% outcome for it to be Ubers, rather than the 60% requirement to change the status quo that is used for every other Pokémon that gets suspect tested out of the tier.

This discrepancy also existed during the Roaring Moon suspect, but its verdict wouldn’t have had an impact on its currently NDUbers status. While this should’ve been noticed then, this particularly impacts Deo-S because it should be unbanned if this was followed.

ND is, of course, not bound to official tiering guidelines, where the 50%+1 threshold was established last gen with Zamazenta-C. However, the format’s current status quo means that this is blatant council manipulation, unintentionally or not. Thus, National Dex should adopt this policy moving forward. Whether it should be retroactively applied to Deo-S or not is also a discussion point, but I have less of a stake there.
 
For some background, there wasn't any unawareness about 50 +1 for QBs at the time voting went up, however, I honestly don't think any of us (Runo, Kyo, myself) really knew about the policy's existence until the Palafin suspect came out in OU which is what prompted me to bring it up within our leaders chat on 12/21 which was a day before voting went up. Since NatDex isn't locked to being bound by official policy at all times, we internally discussed what we thought was best between 50% and 60% and we agreed that 60% was favorable, which can partially be attributed to wanting uniformity with the prior Roaring Moon suspect despite that also being in contrast with official policy, so definitely could be considered a mistake there.

I do agree about the potential dangers of this precedent being set which can lead to actual council manipulation (also I'd stop throwing this phrase around haphazardly when the council didn't make this decision, you're slandering people for no reason), and I as I said in NatDex cord at some point the other day, I'm open to adopting 50% for the future if the player base doesn't support 60% for the sake of QBs retests (indifferent on if it should be applied retroactively to DeoS), but we were just trying to make an educated decision with the info we had on short notice.

However, I would also like to provide some context regarding Deoxys-S itself and why I felt that 60% made more sense for it than 50% in this case personally:

Deoxys-S was quickbanned a little over 2 years ago in a large slate including some objectively ridiculous mons like Flutter Mane, Mega Blaziken, and Kyurem-B, and the reasoning was due to its propensity to enable these insane brokens by just doing lead DeoS things (deoS gets Magic Coat in ND as well). Now, in the present day after the dust settled from the Tera suspect, Deoxys-S was the #1 survey scorer and also scored #1 in the council vote for the first suspect down from Ubers, and a lot of the theorycrafting concerning Deoxys-S was about the strength of NP sets in conjunction with Z-moves off an absurd speed tier, however, there was no way to know for sure how DeoS would interact because its first tenure where it was quickbanned just did not represent its capabilities fully, mainly being banned as an accomplice to quickly curb the hard HO meta that dominated early SV NDOU. The suspect came and went, with the main problematic aspect of DeoS being determined to be NP + Z sets

To summarize, I didn't think that a mon whose initial QB had been in such a drastically different metagame climate 2y ago while performing a different role that was determined to be broken in both iterations should have its unban % reduced by 10 in the current metagame, as DeoS is much more similar to an Uber who was never allowed being suspected down (eg SV ND Darkrai) than a standard council QB being resuspected (eg SS ND Ash-Greninja).
 
Heavily agree with this especially given weve had some pretty dodgy quickbans in the past. See: Ursaluna and Sneasler Slate. which ended up with ursaluna quickbanned and sneasler left in the tier. A few months down the line Ursaluna was unbanned and even fell to NDUU while sneasler was later banned by suspect with an over 90% Ban Majority (40-4).

I also think this should definitely apply retroactively to the recent deoxys speed suspect test as A council slate from over two years ago in an entirely different meta that had terastalization which we now do not is effectively overturning the majority community opinion on this matter. Likewise if the council had decided to unban deoxys speed with the large unban slate that came immediately after terastalization was banned, the exact same suspect result that has now resulted in a ban would have instead resulted in a do not ban verdict.

Quickban decisions like this can have a huge impact on future community driven tiering and the 50% +1 should be adopted as standardized across all tiers official or unofficial for anything quick banned/unbanned by slate.
 
I’m neutral on the 50 vs 60 percent argument, and have already made my feelings clear in #insidescoop, but this threshold should not be retroactively applied to Deoxys-Speed. Everyone involved with the suspect knew the threshold was 60% going in, and whether this threshold is the correct one or not, it was the agreed upon one for the suspect, and should not be overridden after the fact.
 
Whether or not National Dex adopts the 50+1 threshold for future suspect tests is neither here nor there, but I do not believe that a change to 50+1 should be applied retroactively. NatDex has followed this format previously without issue and, as said in the OP, it is not technically bound by the official tiering guidelines. I do not believe that the council was trying to manipulate this at all and they were just following the numbers that it was set at previously.

I think retroactively changing this threshold after it had been made clear to everyone that the unban threshold was at 60% as well as the fact that it has been previously sets a bad precedent. I do think that we should probably change it to 50+1 in the future to stay consistent with the rest of Smogon, but the idea of applying it now that its already been announced after everyone knew what the deal was going in is not the play in my opinion.
 
Few things:
  • Don’t apply this retroactively. What’s done is done. Voting would be compromised and communications to voters were already made. Maybe have another Deo-S test whenever the tiering calendar opens up in the future.
  • I don’t fully blame tier leadership. It’s not easy with so many moving pieces and nuances to the rules. You live and you learn. I appreciate communication and open mindedness.
  • This should be put into effect immediately for all future cases. Just the most clean and effective way of doing tiering while eliminating perceived manipulation of thresholds.
  • Council members should not double down by blaming people for not getting reqs/voting in situations like this. Change is ok. It’s not a matter of right/wrong. It’s just a matter of what is best for the community.
Happy holidays.
 
To summarize, I didn't think that a mon whose initial QB had been in such a drastically different metagame climate 2y ago while performing a different role that was determined to be broken in both iterations should have its unban % reduced by 10 in the current metagame
I don't see why this doesn't justify having its unban percentage decreased by 10%, frankly. As you yourself stated, it performed a wildly different role in a wildly different metagame - at that point, it might as well be a different version of itself currently. I don't see why modernized tiering policy should not apply to a near-completely different 'mon. There should have been an earlier suspect of it once the first broken things were gone, yes, but this level of difference between what Deo-S was and what it is today warrants a 10% decrease to follow modern tiering policy.

Of course, this can't really be applied retroactively, but I would support a retest of both Roaring Moon and Deo-S in the near future adhering to the 50%+1 rule so that we can bury the hatchet.
 
Personally I absolutely support adjusting to the 50%+1 format for any future suspects that much is practically unanimous. As for retroactive application, I dont see why you can't just fix it. A mistake; or atleast a misguided decision was made to handle it there's no real reason to double down on it here. I checked the suspect thread when i was curious about it being 60% required to unban in IS chat, and didn't see any actual indicator of the suspect requirement on the thread, so I don't think its particularly arbitrary to adjust it to what it should be. It might seem like its forced but honestly with how SV NDOU's tiering has been handled I think its completely fine to fix this by applying the results as it not only hasn't been 24 hours, but I don't believe its even applied to the SIM yet.

Just let Deoxys-Speed down now because that'll potentially impact future suspects coming down the line as well.
 
Personally I absolutely support adjusting to the 50%+1 format for any future suspects that much is practically unanimous. As for retroactive application, I dont see why you can't just fix it. A mistake; or atleast a misguided decision was made to handle it there's no real reason to double down on it here. I checked the suspect thread when i was curious about it being 60% required to unban in IS chat, and didn't see any actual indicator of the suspect requirement on the thread, so I don't think its particularly arbitrary to adjust it to what it should be. It might seem like its forced but honestly with how SV NDOU's tiering has been handled I think its completely fine to fix this by applying the results as it not only hasn't been 24 hours, but I don't believe its even applied to the SIM yet.

Just let Deoxys-Speed down now because that'll potentially impact future suspects coming down the line as well.
This isn't a mistake, we chose to apply it to Deoxys-S because NatDex had policy inconsistency and wasn't obligated to follow what official tiers do. Resulting in us just copying what we did last time for the Roaring Moon suspect. Where is the mistake there? To retroactively free Deo-S is just asking council / leaders to ignore the result of a legitimate suspect test.

A case can be made for future suspect tests to apply 50% +1 but retroactively applying it seems really questionable.

I don't see why this doesn't justify having its unban percentage decreased by 10%, frankly. As you yourself stated, it performed a wildly different role in a wildly different metagame - at that point, it might as well be a different version of itself currently. I don't see why modernized tiering policy should not apply to a near-completely different 'mon. There should have been an earlier suspect of it once the first broken things were gone, yes, but this level of difference between what Deo-S was and what it is today warrants a 10% decrease to follow modern tiering policy.
Sealoo's interpretation of Deoxys-S can create two camps of thought: Whereby one believes that because it's essentially a "new" mon that means that it should be treated with a level of unconfidence in its capabilities, thus requiring a stronger threshold to avoid regret / having to test it again later if it becomes more optimized and problematic. The other side, your side, uses this same statement of unconfidence and says that it should be given more lenience not less.

My personal take on the matter is that Deoxys-S itself is irrelevant to the discussion, it could've been Roaring Moon again or Palafin over Deoxys-S and this thread would've probably been made regardless. The mons that get banned from a format were and banned for a reason, they were unhealthy at best and gamebreaking at worst. You can't always say "but that ban was 2 years ago [X] is essentially a completely different mon now since [Y] and [Z] is in the meta and [A], [B], and [C] are gone", I don't think threats like Naganadel or Genesect are gonna care too much about a statement like that. Considering how potentially absurd the threats in the banlist can get, I don't think it's insane to ask the community to have a strong sense of concenus on a controversial mon instead of just only half of the community being needed to unban a potentially warping threat and potentially include something that is a net negative to the health of the meta. To me 50% +1 for OU suspect tests only show a lack on concensus if it can't naturally get a supermajority, which for normal suspect tests means the status quo wins. Why should it be different for unbans like this? The status quo should be especially favored in situations like this since you are adding new threats to account for instead of taking away.

@Retest Unban Percentage Threshold for OU Tests:
The logic used by Finchinator and by z0m0g in the official ruling is fine, but we have the opportunity to not follow it which can be a benefit for stability. To tackle z0m0g's point real quick: While it is true that anything that is unbanned can just be banned again (NatDex has even done this before with Darkrai and stuff), it prolongs the time you have a potentially busted mon in the tier because the community failed to have a sturdy concensus on it while also filling up time that could've been used for other pressing matters. I would rather have additional assurances with the 60% at that point. I don't really understand how it could be construed as council manipulation when at that point every ND OU suspect test would have the 60% threshold instead of potential for something like say...a mon being quickbanned and then suspect tested down in order to bypass the standard 60% requirement. (I might be misunderstanding that paragraph regarding power's point, not exactly sure if that is in support or against of 50% +1 for unbans)
 
Last edited:
This isn't a mistake, we chose to apply it to Deoxys-S because NatDex had policy inconsistency and wasn't obligated to follow what official tiers do. Resulting in us just copying what we did last time for the Roaring Moon suspect. Where is the mistake there? To retroactively free Deo-S is just asking council / leaders to ignore the result of a legitimate suspect test.

A case can be made for future suspect tests to apply 50% +1 but retroactively applying it seems really questionable.
To be clear, the fact of the matter is that you guys were simply unaware of the policy so the fact this suspect was 60% unban threshold was entirely from a mistake. The choice to double down is also a mistake in my eyes and I know I'm not alone on this; realistically all it did was make the situation worse and make you guys look bad. I don't think anybody would've actually complained that you fixed the reasonings before the voting slate to be more in accordance with tiering policy; especially considering the support it has to adopt 50%+1 at the moment is near unanimous and that the ban threshold wasn't actually in the OP to begin with.

Additionally, the reasoning that sealoo mentioned (seemingly only between the 3 ND heads, which is even worse that council was uninvolved in my eyes but that's another conversation), is questionable at best. The reasoning was almost purely on vibes that Deo-s didn't feel like a mon they had been freed before; despite the fact that it both was unbanned before and was only banned with reasoning of a quick fix to make HO less comically ridiculous in the same slate they banned Kyurem-Black.

I'm low on time for Christmas celebrations with in-laws so I'll finish it with this paragraph (and do forgive if this was too aggressive I can't proofread this more than the 4 times I've done already); I don't have any real issues with the mistake being made in the first place; people are human and oversights are going to happen every so often. But the resulting decision feels like everything surrounding it was (putting it kindly) really misguided, one that only really served to screw the people over whom succeeded in getting the majority that should have been in place from the get-go. You made an honest mistake and made the choice not to fix it.
 
Apologies for the delayed response:

To be clear, the fact of the matter is that you guys were simply unaware of the policy so the fact this suspect was 60% unban threshold was entirely from a mistake. The choice to double down is also a mistake in my eyes and I know I'm not alone on this; realistically all it did was make the situation worse and make you guys look bad. I don't think anybody would've actually complained that you fixed the reasoning before the voting slate to be more in accordance with tiering policy; especially considering the support it has to adopt 50%+1 at the moment is near unanimous and that the ban threshold wasn't actually in the OP to begin with.
The Roaring Moon suspect from awhile back could've been labeled as a mistake, but calling an intentional double down with Deo-S a mistake is untrue because it paints it as if we again forgot that this official SV OU policy existed and made the same mistake as Roaring Moon when ... we intentionally set it to this number knowing the SV OU policy. It was understood that with the minimal backlash from the Roaring Moon suspect and inconsistent handling of it and the prior Ash-Greninja suspect in Gen 8 (it appears that the Roaring Moon suspect this gen is where the divergence occurs), we could solve this inconsistency by making the Deo-S suspect the new precedent going forward. I said the term "double down" for Deo-S but it's more a clean slate in order to remove the inconsistency, and with it being a clean slate it meant that we could choose our pathway. Which of course led to the discussion among Natdex Leaders. I don't know where you're seeing this "near unanimous" support for 50% +1 but genuinely it would be helpful to us if you showed it because it seems neutral or split in my eyes. Regarding the fact that the ban threshold wasn't in the OP, this feels largely irrelevant when it's not something that has been done for unban suspects in NatDex to begin with.

Additionally, the reasoning that sealoo mentioned (seemingly only between the 3 ND heads, which is even worse that council was uninvolved in my eyes but that's another conversation), is questionable at best. The reasoning was almost purely on vibes that Deo-s didn't feel like a mon they had been freed before; despite the fact that it both was unbanned before and was only banned with reasoning of a quick fix to make HO less comically ridiculous in the same slate they banned Kyurem-Black.
Sealoo is using Deoxys-S as an example of possible circumstances for when a 60% threshold would be warranted. My own personal take on Deo-S in the post above can also justify this albiet with a different mindset but overall NatDex Leaders' consensus was that we preferred to solve the tiering inconsistency by favoring the status quo rather than mimicking SV OU stance. I'm not gonna pick apart sealoo's argument outside of this because again I feel the discussion of Deoxys-S in a vacuum misses the purpose of this thread and our justifications for making said test 60%, which was to solve a tiering inconsistency. Deoxys-S remaining banned was a side effect not the goal.

Given the information above, I think it would be best to put the discussion to Deo-S to bed because for it to be unbanned you have to call leaders actions throughout the suspect test either a mistake or malicious when it was neither. I understand that factors such as not including council in the discussion and all 3 leaders voting against Deo-S in the suspect looks bad in a vacuum, but the context provided should show that this wasn't a mistake or some malicious attempt by council to keep it banned because we hated it or something. We even helped a pro-Deoxys-S user fix an issue with his account so he could actually vote even when not doing so would've sealed the result even faster. This is ultimately a legitimate vote in my eyes.



Re: Some Discord callouts because they made me annoyed​

Bobsican said:
I'm aware that some are just like "NatDex is a Pet Mod/unofficial tier and can do whatever they want independently of tiering policy", but the truth is that deviating from such standard practices can obviously compromise the allowance such tiers have gotten for proper Tiering Contributor recognition and other stuff in other sections, and given this has been attempted to be kept as the status quo ideally to the best capability of the respective councils in two Pokemon generations by now, I would think it'd be best to at least have some change here than to try to act like ND can just do whatever and dismiss it, unless there's a desire to change what was officially decided for regular OU, but that's its own can of worms
bumboclaat said:
Just re: deoxys-s suspect stuff. It is in our best interest to have the same suspect requirements as official tiers even if we are not required to do so. ND in general already suffers from the undeserved stigmatization of being unserious or a petmod and things like this only serve to further or legitamize that viewpoint. It'd be great if ND could integrate with the rest of the site to some degree rather than be squirreled away in isolation. Should that be a possibility in the future deviating from official tiering practices just creates an unnecessary roadblock that people can legitimately point to as a reason against doing so.
There's no amount of policy that we can implement that removes the petmod/unserious label people put on NatDex. Two separate official tiers and an OM literally offered to sell a tiering action slot via the likeshop and yet they aren't brandished with the unserious label or at least it's not permanently attached. Meanwhile a lot of things that are done in NatDex get used as a black mark against the format for a long time regardless of the context, outcome, or execution. The isolation we receive from other sections is essentially by design because of the disconnect with the concept itself not the administration. The creation of Natdex wasn't simple and we've had to evolve our identity overtime in order to answer questions that official tiers never have to ask realistically. I don't think there is any gap that can be bridged regarding that matter because any choice NatDex makes there is arbitrary vs an official tier's iron clad cartridge legalities.

Official tiers have fine policies that can be emulated with support but conforming solely because it's what official tiers do has no realistic gain since the chances of being given additional opportunities to integrate seem absurdly low (idt NatDex would ever earn a spot in a tour like SPL or SCL, or get a trophy within Smogon's lifetime). The only other chances that I realistically foresee is additional communication and team tour inclusion from our respective counterparts, but this is achievable and has been achieved at times without the need of strict conformity (see Gen 8 AGPLs before Crown Tundra, an RUSD, UUbersPL).

As a section the awards we already receive (top level subforum, 2 CAs, banners, community leaders, tiering contributor badge, etc) are fine considering a lot of other opportunities are very out of reach. In general the opportunities we have to break away from official policy on things (such as Tera and Sleep) are not explicitly punishable given prior Upper Staff's behavior towards NatDex actions throughout the year was apathetic and distant instead of a direct denial. There are people, even in NatDex circles, that still don't understand this especially with the Tera suspect regarding people claiming that we supposedly ignored admins to start it. They didn't give a shit if it happened or not, they just didn't want their name attached to it, that was the real issue. This apathy from Upper Staff can be a benefit so long as there is transparency and support from the playerbase, so currently there is no drawback to deviating unless the community says otherwise.

If there were other pressing arguments made on Discord then I can try to address them if someone points them out.


I'm very conflicted right now:

I say all this in support of keeping Deo-S banned and 60% in place but at the same time I will still be fine if the community wants 50% +1. I do have a concern however about the general lack of motivation to actually support this cause and as a result I'm a bit hesitant to jump to a conclusion despite it delaying future suspects.

Just moving to 50% +1 because that's the SV OU standard is an easy way out yes but it's not a good justification. I also don't really agree with stuff about council corruption highlighted in the original SS OU thread because it feels like a realistically pointless safe guard. Transparency and community support is a norm leaders and councils try to follow already so any fear of corruption regarding issues like this would more point to a systemic lack of trust in respective councils, which isn't going to be erraticatated with a simple rule change. Worse so that the theoretical corruption again isn't removed, only lessened. A truely malicious council/leader can still create negative impacts to tiering with the 50% +1 rule and breach the community's trust.

Any reasoning for making it 50% +1 is irrelevant though, I only care about what the community wants. I urge people to consider the benefits each voting threshold provides and decide from that.

For Deo-S I will continue to fight any attempt to unban it.
 
Last edited:
Seems this thread has largely stagnated and its been holding up our next suspect (Roaring Moon, who will have its % to unban decided by the verdict of this thread due to being a QB at the start of the gen E: this is wrong, ignore) for about a month, so myself and other ND leaders talked it over during the past week and overall concluded that despite our personal reservations, it doesn't seem like there's much support for 60% amongst the community, so it's favorable to stick with official policy regarding the matter. It didn’t seem like there was much support for applying it retroactively to Deoxys-S in this case either, which we agreed on as well.

Therefore, we’ll use 50% +1 for QB retests going forward and it will not be applied retroactively to Deoxys-S, but this doesn’t eliminate the possibility for action pertaining to Deoxys-S in the future due to the awkward circumstances surrounding this suspect.

Thanks to all who chimed in on the topic whether here or Discord
 
Last edited:
Addendum:

A question came up regarding the status of a quickbanned Pokemon's voting threshold if they had previous retest. Tiering Admins Aberforth and Star have confirmed that quickbanned Pokemon who have obtained a "Do Not Unban" percentage of 60% and higher in previous suspect tests will require a 60% voting threshold in subsequent retests. Quickbanned Pokemon who have a "Do Not Unban" of <60% use 50% +1.
1738117867268.png

1738117882072.png

What does this mean in practical terms:
  • The current Roaring Moon retest will have a 60% threshold applied due to it scoring 48/67 (~72%) "Do Not Unban" in its previous retest.
  • A future Deoxys-Speed retest will have a 50% +1 threshold applied due to it scoring 18/43 (~42%) "Do Not Unban" in its previous retest.
  • Retests for quickbanned Pokemon who haven't yet been retested yet (Magearna, Palafin, etc) will have a 50% +1 threshold applied.
 
Last edited:
Back
Top