Starter kits, and why reading one teaches you the engine

What a kit actually is

A kit is a bundle: prefabs, scripts, a scene laid out to show them working, and whatever UI the loop needs. When you apply one, those pieces land in your map as ordinary objects and ordinary scripts. Nothing is locked and nothing is a black box you call into. You can open the script that makes a platform move and change how it moves.

That distinction is what makes kits useful. A tutorial tells you what to type. A kit hands you something that already works and lets you find out why.

The two families

Finished game loops. These are playable end to end: a scoring rule, a fail state, a HUD, a reason to keep going. Take one, replace the art and the numbers, and you have your own game with a loop that was already proved to work.

Rebuilt systems. These do something the engine can already do for you: drive a car, chase a player across a navmesh, move a character. The difference is that the built-in component is switched off, so one editable script does the entire job out of physics primitives. Raycast suspension per wheel. Capsule-versus-world collide-and-slide. Route requests that hop corners themselves.

Reach for the first family to ship something. Reach for the second when you want to understand what the engine is doing on your behalf, or when you need behaviour the built-in version will not give you.

Choosing by the loop you want

Pick the kit whose loop is closest to your idea, not the one whose art is closest. Art is a swap; a loop is the design.

• Obstacle course — checkpoints, kill bricks, moving platforms, spinners, jump pads, and a finish line with a live timer and best-time saving. The classic first project, and the one that teaches respawn logic.
• Driving — a car you walk up to and get into, ordered race checkpoints, a lap timer with a best-lap display, boost pads. Two variants beyond the basic one: a monster truck with a hilly course to bash around, and a time-trial rally over rolling terrain.
• Tower defence — creeps walking a fixed path in escalating waves, buildable towers that auto-target, coins per kill, lives lost per leak.
• Wave survival — three enemy types converging across an arena in escalating waves, click to shoot, coins per kill, upgrade pads between waves.
• Collectathon — an island to explore, gems that spin and pop when collected, a live counter, and a goal that unlocks once you have them all. There is a buggy to drive, too.
• Farm sim — plant on a plot, watch a crop ripen, harvest for coins, under a day-night cycle, with progress kept between sessions.
• Tycoon — tiered collectibles riding a conveyor, income multipliers, rebirth for a permanent boost. The most systems-heavy of the kits and a good read if you like economies.
• 2D platformer — a run-and-jump character on a pixel-perfect orthographic camera, collectible coins with a counter, a goal flag. Proof that 2D is a first-class use of a 3D engine.
• Endless runner — one-button auto-runner with wrapping obstacles, a climbing distance score and a saved best.
• Ragdoll sandbox — spawners, a cannon, blast and fire pads, a sweeper arm. No goal; pure physics play, and the fastest way to get a feel for the simulation.

The system kits sit alongside them. A custom character controller, a custom vehicle controller, a custom navmesh controller and a custom monster truck are each the “no built-in component” version described above. A mobile controls kit gives phone players a real touch HUD with a thumbstick, look area and buttons. A post effects kit collects ready-made camera effects with a gallery to flip between them, and a custom shaders kit does the same for surface shaders, with a walkable showcase.

How to read a kit

Apply it, play it, then work backwards.

1. Play the demo scene until you can describe the loop in one sentence. If you cannot, you are not ready to change it.
2. Open the hierarchy and find the objects that produce the thing you noticed. The checkpoint you touched is an object; so is the timer that reacted.
3. Read the script on one of them. Kit scripts are written to be read; they are the documentation for their own behaviour.
4. Change one number and play again. Jump height, wave size, income rate. Watch what it does to the feel.
5. Only then change the structure. By that point you are editing something you understand instead of something you inherited.

Where kits stop

A kit gets you a working loop, not a finished game. What it will not give you is the part that makes yours worth playing: the pacing, the level, the reason to come back. Two people can start from the same obstacle-course kit and produce a throwaway and a favourite, and the difference is entirely in the parts the kit left blank.

It is also fine to mix them. The kits are ordinary prefabs and scripts, so a driving kit and a collectathon can occupy the same map. The mobile controls kit in particular is meant to be added to whatever you already built.

Where to go next

When your map is ready to show someone, read publishing and what review means. Publishing on Galatrix is a submission with a review step, not a switch you flip.