The only reason you guys are bringing up this "sac a weak Pokemon" crap is because you know how dangerous Salamence is and it's probably going to get a kill if you try to counter it the way you do with other OUs. That doesn't make it balanced in the slightest. The fact that you even have to resort to these ultra-specific scenarios and circular logic proves that there's obviously a problem with Salamence you can't boast for any other OU. If anything, you're just strengthening the argument that Salamence is overpowered and doesn't even belong in the tier....
Right, but the entire issue is getting them in without dying. You have to predict like a god the entire match to keep Salamence from killing anything, and even if it somehow doesn't, at team full of < 30% Pokemon is largely ineffective and prone to a sweep. I don't understand how that shit is not Uber....
Once again, it's not "predict what set it's using", it's "predict absolutely everything it does 100% to keep it from destroying your team because it's decently fast, very powerful, has perfect coverage, and is quite capable of beating all of its checks/counters.
You're like a broken record. This is all
absolute bullshit and has been addressed
several times. The only reason you're clinging to this nonsense is because you've so far proven incapable of coming up with anything else.
You don't have to resort to any "ultra-specific scenarios" to envisage a game where Salamence doesn't get a kill. You seem to like thinking that Salamence can use every one of his moves on a single turn and always kill (or 2HKO) the switch-in, but that's just nonsense you're making up to bolster your otherwise nonexistent argument. Whichever attack the Salamence chooses - and he can only choose one! - it's just as likely that the switch-in threatens Salamence as it is that Salamence threatens the switch-in.
Scarfers and Ice Sharders switching in on the Dragon Dance is not an "ultra-specific scenario". A bulky Flying type or Levitator switching in on Earthquake is not an "ultra-specific scenario". Scizor switching in on an Outrage is not an "ultra-specific scenario". Starmie switching in on Fire Blast/Flamethrower is not an "ultra-specific scenario". This stuff is
common. And if he stuffs it up the first time, getting back in is no waltz in the park; If Stealth Rock is up (protip: It probably is!), then you have to sacrifice something unless you're sure that your 40% Salamence (2 SR and one LO recoil, even less if Sandstorm is up) isn't going to just keel over and die from the attack it has to take on the switch-in.
I'm not going to argue that Salamence can't threaten all of his switch-ins, because quite obviously, he can. What you seem absolutely unable to accept, however, is that Salamence has to pick his attack before he knows what's switching in, and therefore won't always get it right. Sure, if he uses Draco Meteor, then a Mamoswine switch-in dies. But if he uses Earthquake, Dragon Dance, or even Outrage on a bulkier Swine, then he's either dead or crippled, either of which being good enough to strip him of his not-so-guaranteed kill per game.
It's easy to sit there theorymonning how Salamence can kill everything that might switch in. It's also devoid of any intellectual reasoning. It's much more difficult to think about how Salamence actually works in match conditions, the limitations placed on him by incomplete knowledge, and the very real situations where Salamence himself is the one who must "predict like a god" or die. Until you start
actually thinking, rather than just parroting damage calcs and other bits of Salamence trivia that lack any context, then your contributions to this thread are going to remain as empty and unconvincing as they have been for the past 33 pages.