AdminBug reports 23Suggestions 4Exploits 0
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.