Ideas
Game loops, delta time, collision, cameras, state machines, units, pivots and UVs work the same everywhere. Learn them once and you have learned most of every engine.
Game Design & Development · Reference
Our lessons teach ideas, not brands. Every game engine has a game loop, a camera and a way to spawn things. Every 3D app can extrude, mirror and export. They just call them different names. Choose the tools you use, and the tables below translate. Your choice is remembered on every lesson page.
This course is the plain JavaScript you write in our lessons. Find the idea there, then read across to see the same idea in the engine you want to use next.
Mesh apps (Blender, Maya, 3ds Max) make game art. CAD apps (Fusion, Onshape) make exact, buildable parts. SketchUp and Tinkercad are fast for blocking out ideas. The .glb file column shows what actually reaches the game engine.
Textures, sprites and photo edits. Photopea runs in a browser tab, GIMP and Krita are free to install, Procreate is on iPad, and Aseprite is built for pixel art. The .png file column shows what survives when you export for a game. To check and polish a texture before it goes into an engine, use the Asset Bench.
Game loops, delta time, collision, cameras, state machines, units, pivots and UVs work the same everywhere. Learn them once and you have learned most of every engine.
Save in open formats and your work moves with you: .glb for 3D models, PNG sprite sheets, Tiled maps for levels, OGG or WAV for sound.
GDScript, C#, C++, GML, JavaScript and Python are different languages, so code is rewritten. The plan carries over: what runs at start, what runs every frame, and who announces what.
Listed so you can compare, not as recommendations. Every row of the tables has at least one free option.
Menus and shortcuts move between versions. If something here has moved, tell Mr. Scandrett and the table will be fixed for everyone.