Route authoring

Info & How It Works

Rust Routes is a self-hosted route authoring system for Rust servers: a web editor that reads your .map file and lets you draw routes on it, and a game addon that drives Bradley APC, the Travelling Vendor and NPC patrols along them.

Last updated: 10 September 2026 · Version 1.0

What Rust Routes Is

Two halves that speak one versioned route file. The website owns the layout — where a route goes, the order of its points, its type and movement settings. The addon applies that route in-game and hands control back cleanly when it should.

  • Web editor — upload a .map, see it rendered in 2D and 3D, then place and drag waypoints with undo/redo, layers, height snapping and autosave.
  • Game addon — an Oxide plugin that pulls your routes by map checksum and applies them to Bradley, the Travelling Vendor and NPC idle patrols.
  • Race layouts — grid points, ordered checkpoints and a shared anchor point, stored relative to that anchor so moving or rotating it moves the whole layout.
  • No cloud services — one Node process, one SQLite file, running on the server you put it on.

How the Two Halves Talk

Your map file is parsed read-only. The editor stores a render, a height grid and the monument list, plus a copy of the map so it can export an anchored version later — it never rewrites the map you play on.

  • Every map has a checksum, the same value the game server reports. That is how the addon knows which routes belong to the map currently loaded.
  • The addon pulls routes over HTTPS with an ETag, so an unchanged route file costs one small request.
  • Routes are cached on the game server and re-applied on every boot, so patrols keep running even if this website is offline.
  • After a forced wipe the checksum changes; the old cache is ignored and the new map's routes are pulled once you upload it.

Quick Start

  • 1. Sign in and open Maps.
  • 2. Drop your .map file in. Custom maps almost always report seed 1337; procedural maps use the seed from the filename.
  • 3. Open the editor and draw. Changes autosave, and every save keeps a version you can roll back to.
  • 4. Create an API token under API tokens. The value is shown once, when it is created or rotated.
  • 5. Install the addon — copy PathForge.cs into oxide/plugins/, then set ApiBaseUrl and ApiToken in oxide/config/PathForge.json and reload.

The server console prints the account, the token name and whether a project matching the loaded map exists. A bad token is printed as a loud rejection line rather than failing quietly.

In Game

Chat /pf opens the in-game panel. It is deliberately narrow in scope: it selects a saved route and a waypoint and adjusts height only — nudge, feet, eyes, snap to terrain — with a preview and save-back to the website. Layout stays on the website so the two never disagree.

  • Console: pathforge.status, reload, apply, restore, validate, push, preview, bradley.bind, npc.bind.
  • Permission: pathforge.admin — server admins are always allowed.
  • Start / remove patrol from the panel affects only entities that Rust Routes itself spawned for that route.
  • Restore puts the original vanilla path back without a restart.

For Plugin Developers

Other plugins can read and apply routes directly:

  • PathForge_GetRoutes(layer) · PathForge_GetRoute(idOrName) · PathForge_Revision()
  • PathForge_ApplyBradleyRoute(BradleyAPC, idOrName) · PathForge_ReleaseBradley(BradleyAPC)
  • PathForge_AssignNpcRoute(HumanNPC, idOrName)
  • Hook OnPathForgeRoutesLoaded(checksum, revision) fires once routes are in memory.

The convoy and custom layers are delivered through this API by design, not applied automatically.

Requirements & Honest Limits

  • Website: Node.js 22.13+ (it uses Node's built-in SQLite). No npm packages to install.
  • Addon: Oxide/uMod. A Carbon build should be a small change, but it is untested — treat it as a port note.
  • Monument previews in 3D are schematic — original simplified models, not Facepunch prefab meshes. Do not judge collision or route clearance from them.
  • After each monthly Rust update, recompile the addon and watch one lap before trusting it; the movement internals it rides on can move.
  • Map files are large. Uploading and exporting are the slow steps, not the editing.

About This Instance

This copy of Rust Routes is operated by Daily Grind Rust in the United Kingdom. New account registration may be open or closed depending on how the operator has configured it; if the sign-in page will not create an account, registration is closed.

What is stored, for how long, and your rights over it are set out in the Privacy notice. The rules for using the service are in the Terms.

Rust Routes is an independent project and is not affiliated with Facepunch Studios.