Forsburn’s cape issues#843

Cape is an interesting take on a strong attack. You can combo from it, you can kill with it, and it’s disjointed at the cost of it not being able to hit as low as other strongs, and you can’t use it in neutral most of the time. Cape has only one weakness in theory, crouch cancelling the hit and then punishing the Forsburn player. But, there tend to be multiple weaknesses that this move has.

Whiffing the strong hit

Both up cape and forward cape are inconsistent at putting the opponent right where the dagger is. It either pulls too much and sends the opponent behind Forsburn, or it doesn’t pull enough and the dagger is too short to hit them. Not only does the dagger whiff, but the opponent is then completely actionable to do anything while Forsburn is still in the abysmal endlag of the dagger strike.

Crouch Cancelling when falling

There are times where the opponent is not touching the ground, but because they were falling, they land on the ground after the cape hits them. This allows the opponent to get a punish on the Forsburn player when the Forsburn should have had a guaranteed f or up strong dagger hit.

Cc or whiffingat ledge

This is similar to the other one where an opponent is airborn and then becomes grounded after being hit with cape, but just when the opponent near the ledge. The opponent gets pulled onto stage and is then fully actionable to punish Forsburn. But if the opponent is falling past ledge and gets hit by Forsburn’s cape, then the dagger whiffs and the opponent keeps dropping down.

All these issues make the amount of use cases for cape much more limited, and it makes cape a much riskier move that any other strong on hit.

Pls make the move more consistent.

I think cape is interesting in its current form and doesnt really need buffs when dstrong already exists as your more traditional strong. The only things I would like to see is the removal of the sourspot on up strong 2 (the move is already very inconsistent even without it), and addressing people being able to shield before fstrong 2 after failing to cc/floorhug the cape.

I still feel like that at least the consistency issues with Up strong should be fixed, and F-strong should not be whiffing because the opponent wasn’t pulled close enough to be hit by the dagger.

I wouldn’t mind having up strong being more consistent, but having the knowledge and reactions to know when uStrong2 will link IS a skill expression that I’d miss.

Cape is absolutely fine the way it is now