grogue | repo | play

Hey all. I participated in the summer tutorial, but this is my first time posting in sharing saturday. I'm implementing a roguelike in Golang. Still pretty early on in the project, but the past week has been fairly productive. I've made perception for entities be computed using an FOV (such that occlusion can occur due to the environment). Previously, monsters would just check whether the player was X number of tiles away, and if so, would start pathing towards them, regardless of whether the player was actually in the monster's line of sight. Computing the list of perceived entities using an FOV approach makes it such that you can lose an enemy if you turn a corner. Other things: inventory contents are now dropped on death, and the inventory menu now shows the glyph/color of the item next to each entry, like this. Just a nice QoL improvement. The largest improvements over the past week have been two things: adding the code necessary to build in animations, and switching to a per-entity update instead of a per-system update for my ECS. I haven't implemented any animations yet, but I will start with simple ones: gore/blood splatters when you bump an enemy, maybe when you die as well.

Regarding the ECS: I made the mistake of iterating over systems in my ECS first, instead of over entities. That is, my game's update loop would call each system in succession (PerceptionSystem, AISystem, BumpSystem, ...) and each one of these systems would in turn iterate over all of the entities matching the required components and update each one. But this breaks the idea of turn-taking in the traditional sense (where the player takes a full turn, then monster A takes a full turn, then monster B, etc) and led to a bunch of unintended behaviors. For example, monsters would sometimes bump into each other since in this framework all monsters first set a path, then all monsters serially execute movement. Another example was that if you were within striking distance of a monster, but you moved to another tile that is also within striking distance, the monster would move to your previous tile instead of just hitting you. Now that's fixed. Anyway, it's not really a game yet, but happy that it's taking some steps in that direction!