The battle log was made possible by the "save & resume" feature, because it made it possible to save the state of a card as an in-memory class, so I could easily read it and render it again when hovering over any line in the battle log.
The battle log was suggested to me by multiple people pretty much from the beginning. It is needed to answer certain questions, such as why creatures died, why the player got damaged, or why a run ended. All of these should be possible to figure out now.
It also lets me see how the game operates. I already had a bunch of debug outputs, but the battle log makes things much clearer. So this will probably help with finding and fixing bugs as well.
I've also started working on a new music track, and I might just collaborate with a musician again for this one.
What's next? Something that I've wanted to do for a very long time: Adding a second deck.
You can play the current demo on Steam or in your browser on itch.io.
🧙♂️ To be continued...