Hi everyone — I’ve been diving deep into MakeCode Arcade’s source because I want to learn how to build real engine systems (not just make games). I’m trying to understand how the team organized large files (200–500+ lines) like sprite.ts, controller.ts, and camera.ts and how the pieces connect inside the frame loop.
I’m not asking for shortcuts. I’ve already read the source files and tried re-implementing pieces myself (example below). I’m posting here in the Help section because I’d really appreciate pointers from anyone experienced with the engine — especially Richard, Joey, or other core contributors — on design patterns, structure, and practical tips for building maintainable engine code. See the rest of this explain in Trying to Learn How Richard Builds Engine-Level Code like controller.ts - Arcade / Help - Microsoft MakeCode