Welcome to the revival of RoguelikeDev’s FAQ Friday, now on the Fediverse!

The purpose for this event is for traditional roguelike developers to discuss design philosophy and share their technical insights and methods as well as field questions related to the topic.


Development Tools

Last week we already covered languages and libraries, but before we move into discussing details like programming and design there is another important "meta" element of roguelike development to cover: Tools.

Any type of game development will involve using multiple types of software. Beyond the compiler, at the very least you'll have a text editor, and possibly an IDE. On top of those you could have any number of other tools depending on your features, assets, workflow, etc.

Using the right tools is crucial to staying productive and efficiently creating something as complex as a game. Sometimes you even have to build your own custom tool for a specific task, because using what's available just isn't efficient enough.

What kind of publicly available tools do you use to develop your roguelike(s)? What for? Have you built any of your own tools? And if so, what do they do?

Don't forget to mention anything that you use in a particularly interesting or unusual way!


Original FAQ's on Reddit

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 1 week ago

I just use vim + cargo for development. However, for WildsRL, I've built two project-specific tools that have been essential for debugging.

The first is time-travel debugging. When debug is enabled, every entity dumps detailed debug for each turn they take. It includes their current field of view, their knowledge of tiles and entities nearby, any Dijkstra maps they computed, and (since I'm using behavior trees) the latest (Success, Failed, Running, Unused) state for each node in the tree. I have a web UI that can display this debug information, so if I see anything unusual in testing, I can review recent gameplay from any entity's perspective to see exactly why it did what it did.

The second is autoplay. There are enough interactions between NPC entities that a lot of my code is exercised by just running a small scene (100x100 map, 25 entities) for a few thousand turns. I have unit tests that check for crashes using this mode. However, there aren't that many crashes - one of the perks of writing in Rust. Arguably more important is that I can enable debug for the autoplay view and examine NPC behavior over many turns. I have another suite of tests that does that, and for all changes, I review any history diffs to check that the changes are what I intended.

  • source