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.


Original FAQ's on Reddit

you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 2 days ago

My game loop is single-threaded. I figure with small 2D maps and optimized native code, I should never need multi-threading. Plus, I target wasm, so I can't depend on parallelism for performance.

Ignoring UI and menu modes, there are two cases in the game loop:

  1. An animation is running: tick it
  2. Else: do regular state updates

Animation frames are represented as a simple list of (point, glyph) deltas to apply to the map. We render the map as normal, and then render the deltas as an overlay. Even there, there are a few wrinkles. I test each of the deltas for visibility before rendering them. If all of an animation frame's deltas are skipped, then we skip to the next frame during that rendering. In fact, if none of an animation's frames are visible, it won't any time at all, and we'll fall through to case 2. This check is actually relevant to gameplay! It means that players have no way of telling when an animated event occurs unless they can see (at least a portion) of the animation.

Another wrinkle in the animation system is that there may be callbacks that update game state queued between two frames. Adding in these callbacks was essential. For instance, for a fire attack, a callback might light a tile on fire only when the flame moves through it. For all future frames, that cell will be lit in the underlying map.

Compared to animations, case 2 - regular state updates - are trivial! I run the following logic:

  • Find the actor with the smallest time-to-next-turn
  • Advance time to that turn
  • Run plan() to choose an action, and act() to apply it
  • If the actor is the player, plan() can return "blockedOnInput" - that's when we break!
  • Else, repeat

Easy!

  • source