"ECS and Engine-less GameDev in TypeScript"
summary
Concrete workflow and results: TypeScript code uses PixieJS rendering + tiled CSV maps to load sprite sheets and place tiles on a 64×64 grid, turning a CSV into frames automatically. Game logic uses an ECS implemented as parallel component arrays (example size ~5,000 slots) with an entity pool and reuse guarded by a GUID per slot to avoid stale references. Demo shows moving sprites, layered tiles, and reusable velocity/collision systems that actually run.
AI-written summary · about
chapters (13)
- 0:00Engineless game development
- 2:25Tools for game building
- 3:09PixieJS rendering basics
- 4:56Simple sprites to tile maps
- 7:26Tiled for level design
- 9:56CSV maps for game worlds
- 11:50Entity Component Systems explained
- 13:14Components and systems in ECS
- 16:26Systems interacting with components
- 18:33Understanding entities
- 20:40Entity lifecycle and GUID tracking
- 22:07Constructing entities
- 23:31Next steps and advice
related talks
44mGames Development with Typescript and Canvas
26mWhen Cross-Platform Is An Understatement: Making Weird Physical Games With TypeScript
30mType System Game Engines
34mComposing Classes with TypeScript
44mTurning Cocos Creator into a Tough Nut: Building a TypeScript Architecture Around a Game
38mMakeCode Arcade with Static TypeScript
48mCocos Creator: A Journey into TS Game Development for Beginners
26mFrom Takedown to TypeScript: A Retro Game Engine Story