-
Check out the relaunch of our general collection, with classic designs and new ones by our very own Pissog!
-
Welcome to Smogon! Take a moment to read the Introduction to Smogon for a run-down on everything Smogon, and make sure you take some time to read the global rules.
Sally-mence? - An OU Warstory
- Thread starter Angel Diva
- Start date
The warstory really makes me think one thing: is it worth it to sacrifice Salamence to take out X? It was clear in both situations that Salamence was given the opportunity to attack and die, or switch out and risk dying to rocks/revenge.
Both players chose to sacrifice Salamence, which is only one way it could have gone. What would have happened later in the match if either player had saved their Salamence? Perhaps Jolteon would have revenged the one later on, but only if it didn't manage another DD, but still.
There were a lot more possibilities than what happened.
Both players chose to sacrifice Salamence, which is only one way it could have gone. What would have happened later in the match if either player had saved their Salamence? Perhaps Jolteon would have revenged the one later on, but only if it didn't manage another DD, but still.
There were a lot more possibilities than what happened.
pretty nice warstory, maybe next time include the thinking-process to make it meatier.
Its posts like this that show that Mence is strong OU, but not even close to Uber. I hope that the Smogon Council reads this warstory and unanimously votes Salamence OU. This story is almost good enough to be archived.
9/10
9/10
I don't get it, you can't really look at the performance of a pokemon in a single battle to justify a move to uber or a stay in OU. You really have to look how it preforms in the long run, 50 matches +, but by how varied mence can be this is simply impossible.
9.5/10 for the warstory though.
9.5/10 for the warstory though.
On the subject of mence: There are a few people on this thread who realize that one match does not in any circumstance decide the fate of a Pokemon. Just reading down the replies, so many people think that because mence died easy here, he must not be broken. This is false. I have actually never had a problem with mence sweeping me, but the Council can't say "Look at this random player who never had a problem with mence. We should keep him OU". This battle proves nothing by itself.
On the subject of the warstory: It was nice. The formatting was nice. There were some really nice moves, and some not-so-good moves. Double commentary was cool. 8.5/10
On the subject of the warstory: It was nice. The formatting was nice. There were some really nice moves, and some not-so-good moves. Double commentary was cool. 8.5/10
Good Warstory both played very smart a couple mishaps but still very good game to read
Ok, there is no way one match can say anything about anything. I think that is OBVIOUS to the point where it need not even be said. That is simple common sense.
What a warstory CAN do though, is illustrate an example of the case, and then alot of players can (and have been throughout this thread) chime in and say-- "Yeah, that's what always happens to mence in my matches!" Which is how a warstory can become persuasive-- by illustrating an argument better than simply writing the argument, and being backed by multiple players chiming in on a lot of cases indicating that the illustration is in fact representative of their own experiences.
Which it is. Mence is just "meh."
What a warstory CAN do though, is illustrate an example of the case, and then alot of players can (and have been throughout this thread) chime in and say-- "Yeah, that's what always happens to mence in my matches!" Which is how a warstory can become persuasive-- by illustrating an argument better than simply writing the argument, and being backed by multiple players chiming in on a lot of cases indicating that the illustration is in fact representative of their own experiences.
Which it is. Mence is just "meh."
So this battle illustrates that Salamence isn't broken because this one dude had a max Sp. Def Heatran with a Shuca Berry lying around just to suicide itself on Salamence? Or because the other dude had a dying Gyarados with Intimidate so he wouldn't OHKO his Machamp the second it got in? lol
If Salamence was "meh", as you put it, it wouldn't even be a suspect. Maybe everyone else is wrong and we should all play our games like this?
If Salamence was "meh", as you put it, it wouldn't even be a suspect. Maybe everyone else is wrong and we should all play our games like this?
It's kind of ridiculous how adamantly you defend your Mence opinion. Always ready to jump on an opposing opinion. Wasn't this type of thing for the Council Thread?
Anyway, excellent warstory.
The thing is, I don't think that the majority of players would have played Salamence the same in that situation, which is why there is discussion about how things went.
I personally would have switched if I were either Salamence in fear of Scarf in the first case and after I did the damage calc in the second case. I know a lot of others would have done the same.
That being said, that particular choice in the game by both players wasn't fatal enough to make the warstory bad. I rather enjoyed how it was organized and the double commentary helps see how the game went behind the scenes.
Would you leave DD Salamence at +0 in on a near full HP Machamp with Ice Punch? How about Mixmence at -2 on an unknown item Heatran?
No, the warstory illustrates salamence isn't broken if players say it illustrates their experiences and they agree he isn't broken. Salamence being "meh" is my personal opinion, which again is obvious by my use of "meh," a value judgement phrase.
You seem to have a lot of trouble with these cause and effect issues, as well as following argument in general-- It's annoying to have to spell out every detail that could simply be assumed via my word choices.
Nice one guys. Definitely better than most of the warstories out there.
