Software engineer building games, and the tools behind them.
A kids' math game shipped on Steam. Built in Unity, with custom editor tooling for its ScriptableObject data.
A small 2D framework in C++ and raylib, being extracted from Spooky Run: scene management first, then assets, saves, and UI. Spooky Run is the test case that has to keep working while the systems move over.
How Lantern v0.1 handles assets: one reference-counted store, a scope per scene, generated path constants, and what the raylib log showed when I compared loading before and after.
The decisions I made building Spooky Run for Solo Dev Jam 13, what the other option was, and what each one cost or bought me
Replication, and figuring out WAIT
WATCH, UNWATCH, and dirty flags
Why I am learning GAS before rebuilding my Unity roguelike in Unreal with multiplayer
