Configuration

Setup

Create your first game and find your way around the editor.

Creating a game

Open Horizon Editor and sign in. The first screen lists the games on your account, with a search box and a Create New Game button. A new game needs nothing but a title — there are no project templates and nothing is scaffolded on disk, because there is no disk: the game lives on the server from the moment you create it.

Opening a game takes you to the editor. Everything you change from there is saved as you work and versioned automatically; Ctrl + Z restores the previous version, and the History button in the toolbar lists them all.

The workspace

The editor opens on six panels. They are tabs in a resizable layout: drag a tab to move it, drag a divider to resize, and the arrangement is remembered per browser.

Hierarchy
left
Every object in the scene, as a tree. Select one here and the Inspector follows. Parent an object to another by dragging it.
Assets
left
The meshes, textures and sounds imported into this game. Drop a .glb in and the import runs server-side — conversion, thumbnail and all.
Scene
centre
The 3D viewport you build in. This is the engine itself, not a preview: Bevy compiled to WebAssembly, drawing through WebGPU.
Game
centre
The same world, running. Press Play in the toolbar and the game takes over this tab.
Scripting
centre
The node graph for the selected object's script, plus its Variables and Components panels.
Inspector
right
The components on the selected object, and every field on them. This is where you attach a script, a collider or a light.

Objects and components

A scene is a tree of objects, and an object is a bag of components. Nothing about an object is fixed: it does what its components say it does, and you add or remove them from the Inspector.

ComponentWhat it gives the object
TransformPosition, rotation and scale. Every object has one.
MeshThe geometry to draw, referenced by asset id.
MaterialTexture, colour, roughness, and whether to draw both faces.
PointLightA light that radiates from a point.
DirectionalLightA light with a direction but no position, like the sun.
CameraA viewpoint to render the game from.
PhysicsA collider, plus whether it reports collisions, whether gravity applies, and a layer tag.
CharacterControllerKinematic movement: speed, jump height, slope limit and the keys that drive it.
ScriptA node graph to run on this object. An object may carry several.

A script can also declare custom components of its own — named fields of type int, float or bool that it reads and writes with the Get Field and Set Field nodes. Attaching the script adds them to the object automatically. That is where per-object state belongs: health, speed, whether a door is open.

Toolbar

Select and pan

Two scene modes. Middle-click pans in either of them. The transform gizmo switches between translate, rotate, scale and all three at once, in world or local space.

Play

Builds and runs the game in the Game tab. Stop returns you to the scene, unchanged.

Game settings

Ambient light level, the loading image players see, and two overlays for yourself: the view gizmo and an FPS counter.

Publish

Title, description, price in coins, cover image and tags. Publishing pins the current version and lists the game in the launcher.

Working together

Several people can hold the same game open. Edits are merged by a CRDT rather than by locking, so no one waits for anyone else and there is nothing to reconcile by hand. Two editors that have received the same updates hold identical state. Go offline and your pending changes replay when you reconnect.