Hi! First of all: Please, NEVER dial back the feedback! Honestly, this is pure gold for me. Getting this kind of detailed, real-world testing feedback is exactly how Capsule is going to grow into something incredible. I am not overwhelmed at all; quite the opposite, it’s highly motivating!
Here is a breakdown of your points and how they connect to what's cooking for the engine:
1. The "Plays 3 Times" Bug
- Thank you for flagging this and providing the test file (Grickle's art style is awesome, by the way!). This is a known execution/reflow quirk in version 1.9's CSS handling. The good news is that the upcoming Version 2.0 completely overwrites the animation and event pipeline. It uses a strict frame-ended tracking method that guarantees a
play onceinstruction plays exactly once, then stops reliably.
2. The RenJS Approach (Multiple Animations per Sheet)
- You are reading my mind! The Animation State Machine I'm building for Version 2.0 is designed to do exactly this. Instead of having "one file = one animation", you will be able to define multiple named states (like
idle,talking,blinking) for a single character, mapping them to specific frame ranges, whether they are on the same spritesheet grid or separate ones.
3. Playing Animations Backwards
- This is a fantastic idea and so simple to implement with modern web tech! Since Capsule runs on a robust CSS architecture under the hood, adding a toggle to play animations in reverse (
animation-direction: reverse) is a very low-cost, high-value feature. I am officially adding a "Play Backwards" option to the v2.0 roadmap thanks to your suggestion.
Keep the feedback coming whenever you encounter something or have an idea. You are actively helping shape the future of the engine! 🚀