Skip to content

Exporting a standalone build

Besides publishing to the Galatrix servers for multiplayer, you can export your map as a standalone build — a self-contained game you can host anywhere or open in a browser. Think of it as a Unity local build: it runs your scene with the same engine and the same scripts, just single-player and offline rather than networked.

Build it

From the editor's top menu choose Map → Build Standalone. A dialog collects the options:

OptionWhat it does
Game NameThe title shown on the start screen and used for the downloaded file.
FormatSingle HTML — one self-contained .html file with Three.js, Rapier, the engine, and your scene all embedded inline. No external dependencies; opens directly in any browser, even offline. ZIP Bundle — the same game split into separate files (index.html + standalone.js + scene.json). Also fully self-contained, but it needs a local static server to run (e.g. npx serve .), because a browser won't fetch the side files over file://.
Shadow QualityLow / Medium / High shadow map resolution.
Show player avatarRender the capsule character (turn off for first-person or fully scripted players).
Compress scene dataGzip the embedded scene; the build decompresses it in the browser at load.
Compress dependenciesGzip the embedded Three.js + Rapier bundle (~8 MB → ~1.5 MB), decompressed in the browser at load.
Engine modulesLeave optional engine subsystems out of the export to shrink it (see below).

Click Build and the file downloads.

Engine modules

The engine ships a few optional subsystems that a given game may not use. Under Engine modules in the Build dialog you can leave the ones you don't need out of the export:

  • Terrain renderer and Tilemap renderer are auto-detected. The editor scans your main map and every sub-map; if none of them contain a terrain (or tilemap) object, that renderer is pre-checked to be stripped, so a game that never uses it simply doesn't ship it. If a map does use it, it's marked "used by this game" and left in.
  • Particle system, Animator and math.geo / math.curve are marked advanced and left in by default. Each is reachable from scripts (particles.*, animation.*, math.geo.*) as well as (for particles/animator) a component, so a scan can't prove a game never uses them — stripping them is an explicit opt-in rather than something the editor decides for you. Only strip one if you're sure your game never uses it.

Stripping is safe by construction: if you strip a module a map actually needs, the game fails loudly at load with a clear message — "The … engine module was stripped from this build. Re-enable it in Build ▸ Engine modules and re-export the game." — never a silent broken scene. It's a per-export choice; your editable project always keeps everything, so you can re-export with the module back in at any time.

In practice this trims a small slice off the download (a renderer is tens of KB against a multi-MB engine), so treat it as a nice-to-have for size-sensitive hosting rather than a big win.

What you get

A standalone build is a Unity-style local build, not a multiplayer client. It runs the exact same runtime the editor's Play Mode uses, so behavior matches what you tested:

  • your scene, lighting, audio, particles, and weather;
  • every entity script, the input/camera/cursor/character-controller APIs, spawn/destroy, and player verbs;
  • render-to-texture cameras and multi-camera viewports;
  • a click-to-play start screen.

Because it isn't networked, the player-vs-player and server-authoritative pieces don't apply — it's one local player (or a fully scripted one).

Branding

Standalone builds carry a small GALATRIX.com mark: the start screen reads "GALATRIX.com Engine", and an in-game watermark sits in the top-left corner. The watermark is part of the game UI and stays above the scene, so it is not removed by the running game.

When to use which

  • Publish (multiplayer, hosted on Galatrix) — for a shared, server-authoritative game others join.
  • Standalone build — for a single-player game, an offline demo, a portfolio piece, or hosting the game yourself.