Walk and Attack 4 directions. Some 8 directions. For some special chars also a special attack and Idle.
I will add "die" and get hit as soon as possible.
Good point, and you were right to ask: in v1.0 the contact point was not consistent. I measured it: the foot line sat anywhere between 72 % and 85 % of the frame height depending on character and direction.
Fixed today in v1.1 (free re-download): every frame of every character is now 192 x 192, the feet stand on row 165 (0.86 of the frame height) and the character is horizontally centred, in all 768 frames. One pivot, set once. The few pixels of bob inside a cycle are the step itself, not cropping. It is now stated on the page and in the README. Thanks for pushing on this.
Fixed, and thank you - that was a real bug, not you. Clicking away from the window started a second animation loop on every fallback tick, so a minute away left around 1800 of them running at once and the tab locked up. There is exactly one now, and the warning no longer claims you picked up your phone. Reload to get the new build.
Also, genuinely: over a thousand posts of feedback on other people's games is a lot of unpaid work, and it shows. Your report named the exact trigger, which is why it could be fixed the same hour. Thanks for doing that.
Thanks for flagging this — I looked into it, and it's a false positive.
The tool is built with PyInstaller in one-file mode. That kind of build unpacks itself into a temp folder at runtime, which is the same pattern some droppers use, so heuristic scanners get twitchy about it. Only 5 of 70+ engines flag it, and none of them name an actual malware family — Microsoft's "Wacatac" is a well-known catch-all label, SecureAge and SentinelOne just report generic ML verdicts, and the rest are generic too. BitDefender, Kaspersky, Avast, AVG, Avira, ClamAV and everyone else come back clean.
I'm rebuilding it as a folder-based release with proper version metadata, which should clear most of this up, and I've submitted it to Microsoft for false-positive review. I'll post the new SHA256 here when the update goes live so anyone can verify it.
Thanks again for taking the time to check and report it — genuinely appreciated.