Build a foothold on an unfamiliar world. Follow what it leaves behind.
Farlanding is a single-player 3D real-time strategy game about a survey expedition beyond familiar space. Build bases, command a growing force, and uncover a trail of discoveries that changes what your expedition can do. Made with Godot and Blender.
Play in your browser · Player guide · Development plan
Travel aboard the Meridian and choose where to land next. On the surface, establish a base, gather resources, produce units, and respond to an enemy with its own foothold. Each mission adds a different reason to explore.
- Build and command. Grow from a small landing crew into a working base and an army.
- Look beyond the battle. Scan unusual signals and gather intel to unlock new options.
- Adapt to the planet. Weather, terrain and local conditions change how you move and fight.
- Bring discoveries home. Invest in your expedition between missions and shape your next landing.
Some missions reward a strong assault. Others call for a quiet approach or a careful search. The screenshots show the first world; the rest is yours to discover.
The browser build needs a desktop browser with WebGL2, a keyboard and a mouse. Click Play Farlanding, then choose New campaign or Single missions. Press F1 for controls or Esc for the pause menu.
High graphics uses full 3D resolution, shadows, glow and 2× antialiasing. Choose Balanced or Performance in the launcher if your GPU needs a lighter preset. Saved graphics choices are remembered. Graphics details and measurements.
Browser saves stay at the same origin in the same browser. Wait for the saved confirmation before closing or reloading; clearing site data removes those saves. Use the stable play link above to keep the same origin between updates.
Open game/ in Godot 4.7.2 and press Play, or run:
godot --path gameTo build and serve the browser version, install the matching export templates, then run:
tools/install_godot_templates.sh
tools/export.sh Web
python3 tools/serve_web.py build/webOpen http://127.0.0.1:8060. Keep the server running; opening index.html
as a local file will not work. Browser build and deployment guide.
Game code lives in game/, the scripted Blender pipeline in art/, and sound
sources in audio_src/. Definitions are resources; gameplay runs on simulation
ticks, with presentation and audio responding to events.
Run tools/check.sh before pushing. CI checks native behavior and browser gameplay.
Successful pushes to main deploy the tested browser artifact to Vercel after
staged checks pass.
| Read | For |
|---|---|
| Plan | Game design, architecture and phased development |
| Field-kit verification | UI, Survey Log, numbered groups and movement checks |
| Conventions | Code structure and contribution checks |
| Art style | Visual identity and Blender asset generation |
| Audio style | Sound identity and the synthesis pipeline |
| Browser development | Exports, Playwright checks and Vercel CI |
| Graphics qualification | Profiles, visual references and GPU measurements |
| Performance | Simulation and rendering benchmarks |
| Architecture decisions | Decisions and their tradeoffs |
Rebuild generated assets:
blender -b -P art/pipeline/build_all.py
uv run --python 3.12 --with numpy==2.5.4 --with scipy==1.18.1 audio_src/build.pyReleased under the MIT license.

