Previous examples mostly showed simple attacks. However, an attack is still considered an attack even when it is compound—made up of feints or multiple movements. As long as the offensive action is continuous and threatening, it retains priority.
Priority remains with the attacker until one of three things happens:
- The defender successfully interrupts it (for example, with a parry or finding the opponents blade, or counter-attack that prevents the hit in time).
- The attacker themselves breaks the action (by hesitating, withdrawing, or cancelling the attack).
- The attack fails to succeed (by falling short, missing, or otherwise losing its threat).
Too many feints versus a late stop hit may be evaluated as a fault on both sides, therefore no score is awarded against either.
Q1: I don’t understand this one because it looks to me like left pulls his sword back. Like he’s almost chambering. Isn’t that losing the priority?
Q2: Also, flat hits?
Q1: I don’t understand this one because it looks to me like left pulls his sword back. Like he’s almost chambering. Isn’t that losing the priority?
A1/1: The correct way to execute a counterattack against compound attack is to stop the attacker during the feinting phase. Countering a compound attack in the final phase is the same as countering a simple attack. These video are slowed down and even a feint can seem as interruption. But in this case, attacker does one composed action and defender has not used proper time for a stop-hit.
A1/2: he starts moving with lifting back the weapon, and if the opponent was ready for this, and hit him during that lift, back, indeed that would be attack Right (left would not have prio) -- priority is tempo-related, and related to what you do with your tempo.
here, in the first episode of that attack from left, Right retreats, and left really starts a compound attack with a feint. Right only counterattacks too late, and in that situation Left already has the priority
Right could have scored an attack, when left started his forward move, if right anticipated this, was stable on his feet, didnt retreat but counterattack while left was stepping forward while liftinhh the weapon.
this would show the differece between reactive (looking to see what he does) and proactive (anticipation and preparation of situations).
and right could also have scored a counterattack if he didnt use the first episode, during the feint. it would probably jave looked like a step back, stop, and counterattack as he perceives that the attack is rather airy.
but since he retreated away and lifted his own weapn up like a reactive parry instead, he misssed these chances, when he actually counterattacked, he was already being attacked with a direct cut.
im watching the vid a couple more times to make sure im not saying something stupid.
left here makes an action that can be called a feint-attack (for his intent at least) but with an extremely wide movement that causes him to lift back his weapon even with the feint (the technique of feints will need more coaching for many fencers...)
however, right is still not counterattacking during the feint, he is retreating, and forfeiting his chance of taking priority even if the attacking technique is not great. when he ends up cutting, there is already a cut in his way from Left, and he is still reacting to lefts movement.
on a more general note, if we imagine that left performs a technically good feint-attack:
if Right managed to counterattack successfully during the feint (because he anticipates it, so he doesnt react with a parry), he would win this not because he has priority, but because the hit from the counterattack arrives before the attacker(with prio) starts the last phase of the attack, the cut that will actually hit.
even though compound attacks are committed, there is a change of line (or at least dynamics) between feints and cut, and if a counterattack arrives during the feint, we treat it as if that disrupted the next move, and invalidated the hit from the attack even if it eventually arrives -- late.
however, if the counterattack arrives when the final move has already started, we treat it as if the move already in motion could still arrive and be a valid threat, a bit like people think of the afterblow.
but here the distinction is tied to whether you need to start a new move to hit your opponent (like change from feint to the line of the cut), or not, because its already on the final trajectory.
we often talk about it in terms of timing, but in fencing timing is tied to movement, so in order to be on time (eg. with a counterattack hit), we can referee it in relation to movement, like indescribed above. the time is always relative to the given opponents rhythm.
Q2/1: Also, flat hits?
A2/1: Incorrect edge alignment of the blade is a serious technical mistake and should always be corrected in training. The wrong edge alignment makes parries, beats, and counter-cuts more vulnerable, as they don’t transfer enough energy into the opponent’s blade. And of course, the damaging effect in reality would be reduced. Receiving a hit with the flat, however, is an even more fundamental error.
In current competition practice, a strike delivered with enough trajectory and intensity is usually considered valid, even if it lands with the flat. The reason is simple: with the naked eye it is almost impossible to tell if the edge is off by 10 degrees or by 30 degrees. Both situations have very similar effect, not much different from a clean flat strike.
Allowing referees to judge these small angles would create too much uncertainty and random results. The modern approach makes the referee’s job easier, since they do not need to check the exact alignment of every cut. Historically, though, sabre rules treated flat strikes as invalid.
Q2/2: You say if it delivered with enough trajectory (I suppose that means intent to cut with edge) then that’s enough. Ok, clear. What about the case where the strike is delivered also from the flat. Like, thumb grip, comes down completely flat. Is that also ok?
A2/2: I think it means that it is delivered as an intentional cut that otherwise fufills the requirements to score, so being flat does not invalidate hits right now.