Actually a fast attack wind up with an Axe, Maul or Fist is arguably slower than strong attacks with knives and swords. The bottom line is there's a double standard that needs to be fixed. Bash wins vs fast attack AFTER the fast attack is already wound up and incoming. Flip the scenario. According to the rules I just mentioned with Bash v FA, if I start a Bash you should be able to start a Strong Attack and be immune to my bash but you get stunned regardless. Bash wins on both occasions when it should not. This is why spamming bash is the superior move. It's "Dynamite" in Rock, Paper, Bolter.
Which is why capitalising on heavy attacks as opening move can make you win fights before they even start, since most people will use DBash as their opener. As soon as something strong is encountered and overused, the natural counter to is should be hyped instead of the original move dispised. Yes, the DBash-stun that can hit you while you wind up the heavy attack definitely has to go, but you should celebrate that DBash-monopoly by steamrolling over your enemies whenever possible by outsmarting them. When they are pretty much guaranteed to do one move, that is not even hard.
Strong attacks usually stagger so you get one extra fast attack as a gift. Add DoT to the combo and redeploy. i would like to remove it from knife and chain weapons and leave it only on energy weapons.
If you see someone launch a dbash, and you haven't already queued a strong attack, side step or dodge. If you see them queueing a strong attack, queue a fast attack or gtfo of the way. Alternate your attacks, be precise with your timing and footwork, never spam. CQC basics.
Okay, fair enough. At least someone is comprehending the mechanics. Understand that the same criteria you just described doesn't apply to bash versus incoming fast attack. That's what I'm trying to point out. So when you start your Fast Attack PRIOR to me starting my Dbash, I can wind up the Dbash AFTER I see you winding up a fast attack and you still get bashed every time. So the whole "you waited until you saw he threw rock to throw paper" doesn't work the other way around with bash vs fast attack. Bash beats fast attack AFTER the fact(after FA has been thrown) and but Strong Attack doesn't beat bash(after the bash has been thrown). That's a double standard.
Dbash functions in the reverse of the strong attack. In a dbash you're invulnerable (to fast attacks) at the beginning, but more vulnerable during the second half. In an SA you're vulnerable during the wind up, but less so during the strike. What this means is that Strong attacks are best used predictively (start attacking before your opponent) while dbashes are more reactive.
That still doesn't change the fact that bash is working outside the RPS system because it beats fast attacks that are already incoming(prior to the bash being thrown) and it beats strong attacks by bashing the player that's winding up a strong attack. "But the bash was already being thrown prior to the Strong Attack winding up!" you say? So then how come that same mechanic doesn't work with Fast Attack vs Bash? If you have a slower swinging Fist, or mace, or axe it's much more obvious than with swords. You start your fast attack wind up, I see it coming and I roll a bash. Guess what, you get bashed every time(unless the Fist is bugging out) even though you were winding up the Fast Attack well prior to me starting the bash.
But the strong attack was winding up and i did it and it still clanged. Fast attack shoould always beat stong attack like strong attack while it winds up ignores dbash. Opposite attacks shouldnt clang.
