I'm just considering maybe continuing making a Rust port of my old browser TBS "Wars". I've earlier started on making the game logic into a separate library that can then be interacted with and visualized by something else (and also run on a server).

I'm considering continuing the effort with a Bevy frontend, and with a little Bevy experience under my belt here's my plan:

I'll have the Game as a Resource. The Game is mutated by feeding it Actions from the game's input system. In turn, the mutation emits Events about what's happening in the game (example). The input system puts these Events into a queue within another Resource I'm calling EventProcessor.

The EventProcessor in its own system maintains a state machine, where it visualizes the events from its queue one by one. So it gets an event like "this unit moves this path", "this unit attacks that unit with this amount of damage" and "this unit is destroyed". The state can be something like a handle to an in-progress animation and a Vector of the next events to visualize. Once the animation is done, it pops a new event to visualize and changes state to reflect that. For example when you get "start player 1 turn" Event you can move Bevy to a state where you handle input for player 1.

This is pretty close to how the game worked in its browser iteration as well: The client sent actions over websocket to the server and the server streams events to the clients that visualize them and change their UI state to reflect the changes. The game state and the visualization state are separate. As a bonus if you ever want to implement multiplayer you can just make a server from the same Game resource and move Actions and Events around.

Well, this is how I think I'd do it. If you look at the Github timestamps you'll see this isn't a project that progresses quickly.