The speakers suggest that people: 1. Choose a game design to build by copying an existing game loop in a game you like. 2. Build everything you need to make t

The speakers suggest that people: 1. Choose a game design to build by copying an existing game loop in a game you like. 2. Build everything you need to make that game. The "don't make your own game engine" advice applies to not falling into the trap of building a generic game engine before step 1 or 2 — just build the game itself and your "engine" is everything that's needed for that one game. Oogabooga seems to be their Windows-only set of C libs (including a replacement for the C standard library and a build system) to help people build Windows games, and seems focussed on top-down 2D games. https://github.com/alpinestudios/oogabooga https://github.com/alpinestudios/oogabooga. They intend you to fork the repo and use that as the starting point for your game. They also mentioned that it includes hot reloading but I don't see anything about that in the docs or repo. It looks like there's a free group that might have a more guided walkthrough here but it's gated behind a sign-up: https://www.skool.com/game-dev/about https://www.skool.com/game-dev/about