Templates
Every Kaigen project starts from a template. A template is a whole project, with code, assets and a scene, and it's yours from the first build: change anything, delete what you don't need.
New project from a template
kaigen new my_game --template starting-template
kaigen templates # every template for your engine versionOr pick one in Kaigen Studio.
To build on
| Template | What it is |
|---|---|
starting-template | A third-person character on a grid floor, with a follow camera, a day and night sky, touch controls and the editor. The best place to start. |
multiplayer-starting-template | The same idea, with players joining a shared floor. Start here for anything online. |
xr-starting-template | The VR equivalent. |
To learn from
These are full games. They use a lot of the engine at once, so they're better for reading how something is done than for starting from.
| Template | What it is |
|---|---|
proving-grounds | First-person arena shooter against waves of drones |
wanderer | Third-person exploration on a procedural island |
vampire-survivors | Survive five minutes against an endless horde |
canyon-rally | A lap race through a procedural red-rock canyon |
scene-visualization | Product configurator with materials, hotspots and glTF import |
kestrel | Team deathmatch on a cargo ship: server-authoritative netcode, lag compensation and bots |
village-mmo | Online village RPG: quests, combat, vendors and chat with other players |
A good way to use them: ask your AI agent "how does canyon-rally do the car's suspension?" and let it read the code with you.
Worth knowing
- The starting template keeps the game's state (
game_sim_*) apart from its presentation (sky, avatar, HUD), so the same simulation can run with no window for tests and servers. Keep that split as your game grows. - Comments that start with
YOUR ... HEREmark where your code goes.