This is not a real game, it's a prototype of a technical system!

Experience the look and feel of different approaches to a turn-based game loop with animations. Can you set it up to feel responsive but still look nice?

WASD to move/attack

Intended to help designers and developers explore these questions:

  • Should player input skip to the end of animations instantly so the game is responsive? Or should the player wait for animations so movement looks smooth and events are clear?
  • Should enemies move all together at once and obscure the order of events? Or should they move one at a time and create a slower, less snappy experience?
  • Should the enemies wait for the player to finish movement animations before starting their turn? Or act the instant you input your move?
  • What animation speed feels best?
  • How do projectiles look and feel? (Wizard)
  • How do enemy multi-move turns feel? (Bat)
  • How do things feel with few or many enemies on screen?

Try different combinations of settings to see what you think.

When you are exploring, don't only play slowly, make sure to test the limits by playing faster than the animations can draw! Hammer the game as fast as you can with a quick series of steps, and make sure to try some 3-button rolls. Does it drop inputs? Is that okay?

Really getting to feel the tradeoffs helped me to understand what works and what doesn't.

What approach do you think looks and feels the best? Share any thoughts in the comments below or on twitter, to @pkenneydev.

Art licensed from Oryx Design Labs.

More information

Published88 days ago
Player countSingleplayer


Log in with your account to leave a comment.

That's pretty cool little tool/proto. Have you tried making all moves complete in the same amount of time as the player movement?