Responses to Aver, DRaGZ, and WastingPenguins below.
EDIT: Also, everyone should look at WastingPenguins posts again. Persons who want to find my last post can link relatively close to it through my quote of Aver.
Okay I'm understanding this a little better now.
"If the problem has a solution, there is no need to ban."
Unless the solution is to ban it, which makes this sentence illogical, but that against the point.
As, this is a misunderstanding of the meaning of that statement. It's understandable, as it was phrased. . . problematically. Allow me to correct it:
When it says solution, it means the options that are available to you
in the game, as a player at a controller port, trying to win a match. The options are forms of button input sequences on standard controllers, and even further restricted from there (for example, you must set the rules for items during the match to your tourney standard; you must not avoid the stage selection screen).
In your options you are trying to solve 'a problem', meaning anything you encounter that could prevent you from winning a match. We focus on 'options' this way because we have of course agreed that winning should be up to your choices "in the game" (as opposed to kicking your opponent in the groin, or unplugging his controller midmatch).
A ban is not something you can do in the game. A ban is of course one level removed from the game; it consists in an enforcement of certain restrictions on what players can do (to create problems for their opponents).
So the sentence is not paradoxical.
Now I don't believe this infinite was intentionally put into this game. Which by my standards makes it a glitch. I have been playing competitively in PC FPS for a long time now and was preparing for playing competitively in Brawl. Now I don't know how different the rules are but when there is ever a glitch in an FPS is it immediately removed.
This is one reason why I feel that this should be banned, that it was never intended to happen.
If you're saying that by your standards, if you believe something was not intentional, then you believe it is a glitch, that's your prerogative and I dare not try to mold your crazy mixed-up beliefs. Meanwhile if you're saying that your standards state that if something was not intentional, then it is a glitch, then bravo sir, you have just correctly stated the definition of glitch. Those are good standards.
If you were saying that your belief that something is not intentional means that it is a glitch, then you're insane. But I doubt the premise.
Now, there is some evidence coming up in the Smash Lab that the infinite may have been intentional. So that would throw this out the window. But I want to check you're still going with this post, since many pages have passed.
And of course, see down this post.
One other argument I have thought about is how it makes the game unbalanced. Now playing competitively in FPS has led me to see some games competitive form destroyed by ban happy people who want to ban each and every advantage. I don't want to see that happen to Brawl or any other game.
The difference is that this ban would allow six characters to have a better chance at winning, as well as not causing a shift from one character to the next. It would not have a negative effect on the metagame and if you kept the ban happy people in check nothing else would be banned.
Irrelevant. See my last post. "If the problem has a solution, there is no need to ban it." (not my words; I've forgotten the author, sorry!)
It does not matter if it would or would not give six characters a better chance at winning. I give you that point or not, just for the sake of this argument; it's still untouched that "there is no need to ban D3 infinites."
I should probably state here the principle, "If there is no need to ban something, there is no cause to ban something." Which is to say, a ban is necessary
just[/i] when it is preferable; this is a property of bans (or rather, of competitive mindsets).
It follows from the simple converse, "If there is cause to ban something, there is a need to ban it." If a ban is warranted, it is necessary to enact it, by the nature of bans and how they are warranted just by dire situations.
Since there is no cause to ban D3 infinites, it doesn't matter whether you were or were not going to try to argue that it ought to be banned from your "it wouldn't make the metagame worse" claim - which, recall, I'm not saying is true, but am saying I don't care about giving it to you for the sake of making this argument stronger. With no cause to ban D3 infinites, that means precisely that no one should do it.
Another example of people just twitch-posting without even understanding what is being said.
I just give up. No one here obviously actually gives a **** about the DeDeDe infinite or not, they just want to prove everyone else wrong at something, anything but the DeDeDe infinite. Because heaven forbid if we actually read the statement we are going to respond to.
I hope I give a ****. I think I'm here because I'm trying to find the Truth, and also because I do in fact care if D3's infinites got banned without it being established there was cause. If they don't break my game, I want them to stay, because I don't want anything messing with the competition.
I hadn't given this much thought, but I suddenly find it incredibly interesting. What's going on with the patch-the-problem-away online gaming communities? Have they totally abandoned the Sirlin approach to competitive gaming that is so highly championed in fighting game circles? Consider an RTS game like Starcraft. Starcraft has been HEAVILY patched all throughout it's life cycle. A very high percentage of patches are implemented specifically to make the game better balanced. When players discover a matchup-breaking exploit that Zerg has over Terran, how does the community react?
They don't say, "Leave it in! But you better stop picking Terran when you're up against a Zerg player."
Instead they say, "Patch that **** up! Restore balance!"
Yes, I realize that Starcraft has three "characters," so a matchup-breaking exploit is a way bigger deal. But that example is just for illustration. A tiny exploit doesn't have to be matchup- or game-breaking to be "balanced" or simply patched away entirely.
That's crucial, though. Do you know for sure that the overwhelming majority of players of FPSs, say, all say "patch that **** up!" ?
I do respect the philosophical move, though. This is the first new direction the argument has taken in. . . well, a hundred pages.
What have they gained from this process? A sublimely balanced, intensely competitive game that has enjoyed a decade of hardcore success. The analogy starts to break down when you consider that Nintendo ain't exactly patching jack ****, and we don't have the power to patch the game in the same manner ourselves without mandating cheat devices that many players simply won't have access too. For any number of reasons, most unbalancing elements and techniques cannot be "fixed" or removed from the game.
But in the case of the infinite in question... removing it from the game ENTIRELY would be ALL TOO EASY. If you don't think a ban could be enforced in tourney play, you're wrong. And it would not be hard. At all.
Sure, you can't fix everything... but every little thing that you truly CAN fix would help toward a balanced, competitive game with a vibrant, sustainable community.
Right now your problem is you haven't shown that "D3 infinites" are something to fix. They can be likeable. I like them.
Back to Kirio's (I think?) point: If you try to talk about making it 'better', you will always get arguments, because it will almost always be subjective. Only when the game is broken is there one clear direction for the game to do. And it has been defended that the game is not broken right now. Players cannot omnipick D3 and win all their games with dthrow. Their opponents can pick. . . I dunno, Pikachu was it?
So why the disconnect? What's going on with these patching maniacs? Is their philosophy less competitive than Sirlin's? I'm not arguing either way but I'm genuinely curious to see what you guys think.
Discuss this, people. Even though I don't think it will get back to answering our issue.
The end answer is probably just that online / producer-managed competitive communities are just. . . different.
Reading comprehension: learn it.
This has nothing to do with how broken something is. It is up to the community to decide whether or not something is broken. We all agree that D3's standing infinite breaks his matchup with DK, which is a subjective opinion that we all happen to agree on. Let's imagine that we all agreed that Pika's chaingrab breaks his matchup with Fox (we don't, but let's pretend.) And please note the difference between a heavily one-sided matchup and a truly broken matchup.
So in our scenario, both those techniques/sequences break matchups. Why don't I support banning both?
Because banning Pika's chaingrab, just to help Fox, or Wolf, or whoever, takes something valuable away from the metagame: a legitimate, non-broken tactic vs. many, many characters. In order to remove the the bad (brokenness) you will also have to remove plenty of good (a legit, non-broken technique vs. most characters). This technique HAS non-broken applications. In fact, it has many non-broken applications, but the number is irrelevant. All that matters is that it has non-broken applications at all, which would be removed if the sequence were banned.
But what happens when you ban D3's infinite? You lose nothing but brokenness, because the sequence exists ONLY to break matchups. It has ZERO non-broken applications. Banning it means you are removing plenty of "bad" and losing nothing "good".
Question: Can someone even think of single other technique/exploit with ZERO non-broken applications that is allowed in tourney play?
Good question. I can't answer it. Anyone?
Also, interesting distinction. But again, I'm doubting it's going to lead to actually backing the ban position.
TL;DR version: D3's infinite should not be compared directly to most other broken strategies because it is fundamentally different, as described above.
Hmm. . .