IRDC US 2015 - Brian Bucklew, Data-Driven Engines of Qud and Sproggiwood

If you're interested in how Brian thinks take a look at this video: ▶ this video I've learned a lot from this back in the day!

in “Brian Bucklew Porting Caves of Qud from Unity to Godot” · View on HN

I come back to it from time to time and play for a week. It looks like it's been getting more accessible over time, with a new UI update having been rolled out recently. There's definitely a certain mindset that helps make it more enjoyable. Imagination being key! From the technical side, the developers have peeled back the curtain on how they've created parts of the game: ▶ this video [link]

in “Mapping all 13.8 gigapixels of the Caves of Qud world map” · View on HN

I'm pretty far into a project to create a Typescript framework for turn and tile-based (think roguelikes) client/server games: [link] . Mix of entity-component and event-driven design (inspired by Brian Bucklew ▶ this video and Thomas Biksup [link] , though looking now I'm surprised I landed on a similar but imo more robust event system as I was only looking at EC pattern at the time). Typescript means entity factories and their components can be fully written in the language rather than XML per the videos above, and people can for example distribute a package that is basically DnD5e or Pathfinder rulesets, custom world generators, or anything else to be plugged into a published game. Typical Minecraft "infinite" world data structure, handles binding up event system to component listeners automatically, (will soon) handles serialization, listeners are async generators ala Redux Saga for neat inversion of control and advanced patterns as needed. It doesn't have any specific frontends or clients (APIs and react hooks+utils exist but not super advanced yet, and a small WebGL renderer + react component), it's more a collection of objects that recursively process state updates in response to a user input until it finishes (like a classic console roguelike), and produce a serialized stream of events clients of any kind can listen to, completely agnostic to how any client may choose to represent it, so you could easily make a DM interface vs an interface for players connected to the same

in “OpenMW becomes a general-purpose engine for isometric RPGs” · View on HN