The Engine Legacy: From Asteroids to rpgCore
#GameDev
#Architecture
#ECS
#Python
The Vision
Learning to build the foundation before the house. The transition from a discrete project to a generalized toolkit.
Why I built an engine to solve my own friction
The shift from RogueAsteroid (Specific) to rpgCore (General) was born out of a realization: I was re-writing movement, collision, and state logic for every small game idea.
The Systemic Fix
I abstracted these common patterns into rpgCore, a modular toolkit built on a simplified Entity-Component-System (ECS) pattern in Python.
The ROI
This proves I don’t just “code”—I build foundations that reduce future technical debt. By standardizing the logic-component library, I accelerated my own prototyping velocity by 60%, allowing me to focus on mechanics rather than plumbing.