enigmaX
1 days ago
ADDITIONAL: Normal attacks with Katara & Dagger do not work either.
#293
DualBlade's Triple Stab not working
IN PROGRESS
Dual Blade's triple stab does not seem to be registering. After pressing the skill, no damage is registered and mobs do not get hit. There is also a slight delay after the skill animation where character cannot move or jump.
Character & Map:
Hate. Perion Street Corner.
Character & Map:
Hate. Perion Street Corner.
🍅 ME TOO · 0
Log in to confirm this bug.
COMMENTS
4 replies
SnailHunter ADMIN
1 days ago
Found it, and the second half of your report was the key. A Dagger+Katara swing plays a different set of poses from any other weapon — the dual-wield row — and the combat code keeps a list of which poses count as an attack. Those three were never added to it. Everything downstream reads that list, so the swing was thrown away before it ever looked for a target: no hitbox, no damage.
That also explains Triple Stab. A skill waits for the swing to carry it, and the same check discards a waiting skill when it does not recognise the pose — so the skill was dropped before it could resolve. The brief moment where you cannot move or jump is the attack flag timing out with nothing to release it, which is the same root cause.
This is the third time this exact list has been missing an entry: Rush and Brandish had the identical zero-damage symptom a while back. There is now a test that walks every pose any weapon can swing and fails if one of them is missing, so it should not happen a fourth time.
While in there I also finished the rest of the katara attack, which had been built but never actually ran because every swing was being discarded: you should now get two damage numbers per swing rather than one, the second landing a moment after the first, and together they add up to the single hit you were getting before — it is the same damage, shown as the two blades. Double Stab now splits its numbers the same way.
On the dev branch now, so it will be in the next published build rather than immediately.
That also explains Triple Stab. A skill waits for the swing to carry it, and the same check discards a waiting skill when it does not recognise the pose — so the skill was dropped before it could resolve. The brief moment where you cannot move or jump is the attack flag timing out with nothing to release it, which is the same root cause.
This is the third time this exact list has been missing an entry: Rush and Brandish had the identical zero-damage symptom a while back. There is now a test that walks every pose any weapon can swing and fails if one of them is missing, so it should not happen a fourth time.
While in there I also finished the rest of the katara attack, which had been built but never actually ran because every swing was being discarded: you should now get two damage numbers per swing rather than one, the second landing a moment after the first, and together they add up to the single hit you were getting before — it is the same damage, shown as the two blades. Double Stab now splits its numbers the same way.
On the dev branch now, so it will be in the next published build rather than immediately.
SnailHunter ADMIN
1 days ago
Found it, and your follow-up was the key: "normal attacks with Katara & Dagger do not work either" is what pointed at the cause.
A Dagger+Katara swing plays a different set of poses from any other weapon, and the combat code keeps a list of which poses count as an attack. Those three were never on it. Everything downstream reads that list, so the swing was discarded before it ever looked for a target - no hitbox, no damage.
Same guard explains Triple Stab: a skill rides on the swing that carries it, and an unrecognised pose makes the code throw the waiting skill away. The brief moment you cannot move or jump is the attack flag timing out with nothing to release it.
Third time that list has been short an entry - Rush and Brandish had the identical zero-damage symptom before. There is now a test that walks every pose any weapon can swing and fails if one is missing.
Worth knowing before you re-test: the rest of the katara attack was already built but had never run, because every swing was being thrown away. It comes alive with this, so you should see TWO numbers per swing, the second landing slightly after the first. That is not double damage - the pair adds up to the single hit you were getting, split between the blades. Double Stab splits the same way.
On the dev branch, so it lands in the next published build.
A Dagger+Katara swing plays a different set of poses from any other weapon, and the combat code keeps a list of which poses count as an attack. Those three were never on it. Everything downstream reads that list, so the swing was discarded before it ever looked for a target - no hitbox, no damage.
Same guard explains Triple Stab: a skill rides on the swing that carries it, and an unrecognised pose makes the code throw the waiting skill away. The brief moment you cannot move or jump is the attack flag timing out with nothing to release it.
Third time that list has been short an entry - Rush and Brandish had the identical zero-damage symptom before. There is now a test that walks every pose any weapon can swing and fails if one is missing.
Worth knowing before you re-test: the rest of the katara attack was already built but had never run, because every swing was being thrown away. It comes alive with this, so you should see TWO numbers per swing, the second landing slightly after the first. That is not double damage - the pair adds up to the single hit you were getting, split between the blades. Double Stab splits the same way.
On the dev branch, so it lands in the next published build.
enigmaX
4 hr ago
Update: Dual Blade's Triple stab and normal attack are working now. Ty!