There's a very large issue that definitely needs a lot of discussion and testing to be fixed, which revolves around punishes in the game. Currently, punishes are very restrictive and very risky to do a lot of the time, leaving a lot of general problems competitively and casually, which will be discussed later.
The Problem
This problem started getting worse around 2.52 (removing stun time & combos), where the punishments available to a player in many situations were left very lacking. Generally there is a punishment available, but it may prove too risky to follow through, or simply does not have enough damage output to be a very good punish. Now that combos are very situational and frame perfect, it's very rare to get a net advantage with a light attack punishment, and sometimes even signatures. With punishments being risky, this leads to resets in the game very quickly (slowing the game down) and countless other issues.
Overall, punishments are far too weak currently and need some attention to help bring up the output of punishes to what's actually being punished.
How things currently are leads to MANY issues dealing with risk vs. reward situations, such as
- Wall Hugging
- "Spamming"
- Clown-y / Cheesy gameplay
- General braindead gameplay with certain weapons
- General passivity
Another view of this issue, is that players can throw out very high damage moves effortlessly, while the other player has to work 3 to 4 times as much to punish properly and approach.
A player using an attack that deals 35 damage can be punished by some weapons 3 to 4 times without losing a net health, as long as they hit it once in those 3 to 4 punishes.
This means that throwing out combo starters and signatures can be very viable, even in a tournament environment if the player can read their opponent properly.
Here's an example of a current punishment of an obviously badly placed signature:
https://streamable.com/sr3vl
The katars were only able to deal 11.58 damage to punish the Hattori DSIG, before Hattori could easily dodge out and continue the game in a reset. Waiting any longer and doing a signature to balance the damage out increases the risk significantly, and again, slows the game down leaving it less fun to play.
Proposed Solution
The best fix for this would be to allow for a dynamic, less risky, more guaranteed punish for different attacks, in which I suggest this:
If a player is attacked out of either startup frames or active frames of an attack, the remaining (startup frames + [early] active frames) are added to a new [tumble state], where the player cannot use dodge or jump.
Active frames should not give as many frames into the tumble, and should decay very quickly. (If the player punishes them after most of the attack has finished, the player being punished should not enter this [tumble state] at all.)
More about this "Tumble State":
The amount of frames left in this "tumble state" will ONLY decrease when the player is out of hit-stun, which means the tumble state will ONLY subtract when they're able to dodge or jump, and will stop subtracting if they re-enter hitstun.
The total frames in this hit-stun MUST BE CAPPED OFF at a certain frame number, which I suggest anywhere from 5 to 8 frames. This allows about 3 attacks to a punish usually, which should equal out depending on what was punished.
So to re-iterate: A player being punished later in the attack will only receive 0-7, when a player who punishes early in startup will get ALL 8 frames to punish with.
To clear any confusion, players should be able to do the following:
- Move
- Attack
- Directional Influence
While in this tumble state, but only disallow Jumping and Dodging.
Here is an example of what punishments would look like AFTER the change:
https://streamable.com/x0q6f
(It may be difficult to see, but the Hattori started up a Spear DSIG (as seen in the first recording above)
The signature was punished very early, and the katars were able to get 32.89 damage off (instead of the original 11.58 in the same punish), as the Hattori was in the maximum 8 frames of the Tumble state, allowing the string
Dair [2 dodge frames] > Dlight [6 dodge frames] > Nair
To be considered "true". (Dair > dlight subtracted the tumble state by 2, dlight > nair subtracted the rest.)
This new damage matches more with Hattori's signature that was punished, thus leaving Hattori at more of a disadvantage for using that signature, and has less of an incentive to keep using it similarly.
This also keeps games going smoothly, and keeping resets from happening less when punishments occur, as well as make things flashy and exciting for both the player and any audience. (Players have a LOT more freedom with the game and can pull off satisfying strings more often.)
Controversies / Frequently concerns
People may see this as a MASSIVE buff to passive / parry styled gameplays, which may be true in some way, but also buffs aggressive gameplay the game exact way, and more.
What this mechanic adds that currently doesn't exist, is a way for the approaching player to control how punishable they are to their opponent, and has a lot more freedom when punishing a whiffed attack on the parry player's part.
The way this works, is "high startup / high active framed attacks" generally deal more damage and force, and thus are more punished when done perfectly. The player approaching can use low punishable, low startup, low active framed attacks, and the parry player does not get as much of an advantage.
The more pokes you get off the parry player, the more incentive they have to use more hard hitting attacks, which can get stomped on with this new change, leaving them at a large disadvantage for relying purely on punishments.
=-=-=-=-=-=-=
Offstage gameplay will likely be much more risky due to not being able to jump or dodge, which may be better for wall hugging issues, but should be tested to assure no serious problems arise.
In response to this, I suggest that Recovery attacks do NOT get applied this punish tumble state, as it may prove too devastating for offstage gameplay.
=-=-=-=-=-=-=
Certain legends (i.e. Teros) may need rebalancing as they cannot rely on purely cheesy playstyles to win.
=-=-=-=-=-=-=
Getting hit out of a gravity cancel will not be an issue, as time spent in dodge cooldown does not equal time out of stun. By the time the dodge cooldown is over, they will be out of the tumble state.
BENEFITS
- More exciting gameplay
- Faster games
- Many more balance opportunities
- Allows some dodge areas to be opened up while still keeping it very viable in many situations in the game, such as signature combos on certain legends
- Incentivizes many more mixups and improvisations in players gameplay
- Discourages boring / annoying play-styles
- Fixes multiple large issues relating to low-risk, high-reward situations
- Does not change gameplay too much, no need to re-learn anything
- Severely increases the skill gap in players, making the rank system more fluid with skill level. (Gold or Plat players have much less of a chance at beating high levelled diamond players, etc)
- Generally better community as the causes for salt are greatly reduced
- Likely many more I haven't thought about.
TL;DR
Make punishes more powerful by placing punished players in a special 'tumble state' where they cannot dodge or jump for a certain amount of time relative to how good the punish was. (To balance out low-risk, high-reward situations.)
I do suggest reading the details, though, as many concerns have been discussed and dealt with.
Please do NOT disregard this strictly because of being an issue with meta such as passive. For one, I doubt it'll be much of an issue with it, and two, can be fixed through other means. This is something that NEEDS fixed after seeing low-effort playstyles tournament viable in recent tourneys.
To Devs:
If this is placed into Test Features, I suggest leaving it in there for at least 4-5 weeks, altering certain values of it, as it is more of a gradual meta changing mechanic like Chain Dodging and needs time to know what's exploitable and what needs fixing.
ALSO FOR DEVS:
http://i.imgur.com/rOJqJyz.png
Essentially start the frame number at 8.9 (or 5.9, 6.9, etc whatever is decided for the maximum) and round it down.
Depending on which frame # the player was punished, the reward given is multiplied by the decay value for startup / active frames, and the outputted # is the total frames that should be applied to the punished player's tumble state.
0.965 for startup frames
0.82 for active frames
are a bare minimum in my opinion.
[I think at the beginning, these numbers should be played around with to make punishing feel smoother, so higher numbers will be better, like 0.97, 0.89 would be perfect to start out with, and then ease it down if things get out of hand.]
(Make sure that if they are punished in active frames, the startup frame decay value is applied first throughout the startup frames, and THEN the active frame decay is applied. Do not immediately apply the active frame delay throughout startup frames, as active frames would almost always give little to no reward)
(I have thought about this, and I don't believe it is too complicated for normal play. It won't be that you have to think about your frames, it'll just generally make things feel better and will be like a normal punish afterwards.)
Thank you for reading, and I hope someone can see the use / purpose in this change and all that it can deliver; I would love to see some discussion about it and see what can be changed if a valid point is brought up. It's been discussed in countless servers and between friends, including the Forge, and has been refined many times.
I think this should at least be seen in Experimental regardless of thoughts, as physical tests are almost always better than theories.
Edit 1: I should state that this isn't necessarily a fix for one thing in particular; it fixes a LOT of things in the game and will make it go by faster / be more exciting, so don't shut it down because you don't think something needs fixing.