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.
The Game Loop
For those just starting out with game development, one of the earliest major roadblocks is writing the "game loop." With roguelikes this problem is compounded by the fact that there are a greater number of viable approaches compared to other games, approaches ranging from extremely simple "blocking input" to far more complex multithreaded systems. This cornerstone of a game's architecture is incredibly important, as its implementation method will determine your approach to many other technical issues later on.
The choice usually depends on what you want to achieve, but there are no doubt many options, each with their own benefits and drawbacks.
How do you structure your game loop? Why did you choose that method? Or maybe you're using an existing engine that already handles all this for you under the hood?
Don't forget to mention any tweaks or oddities about your game loop (hacks?) that make it interesting or unique.
For some background reading, check out one of the most popular
simple guides to game loops, a longer guide in the form of a roguelike tutorial, and a more recent in-depth article specific to one roguelike's engine.
all 2 comments