Share codes
A race can travel to another server as a block of text. No file, no upload, no account — copy a code, paste it somewhere else, and that server has the race.
Copy Share Code and Import from Code sit at the top of the race editor, under the save buttons.
Using one
Section titled “Using one”To share a race: open it in the editor and press Copy Share Code. The code is on your clipboard; the button says Copied! Paste it wherever you like — a Discord message, a forum post, a text file.
To import one: open the editor — on a new race or an existing one — press Import from Code and paste. It warns first, because importing replaces everything currently in the editor:
This will replace everything currently in the editor with the imported race. Continue?
The race is then yours to look at, adjust and save. Nothing is written until you do.
What a code is
Section titled “What a code is”A code starts with BJRACE1: and is the route, gzipped and encoded as text. It is long — a
dressed circuit is a lot of geometry — but it is only text, so anywhere you can paste a paragraph
you can paste a race.
What travels
Section titled “What travels”| In the code | |
|---|---|
| Name | |
| Mode, Loopable, Passive | |
| One-way gates, Branching paths | |
| Sectors and manual sector boundaries | |
| Gates | Every one, with its position, direction, size and branching links. |
| Start positions | The whole grid. |
| Pit lane | Both lines, the gates it joins between, and every box. |
| Props | All of them, up to the 1000 cap. |
| Race defaults | Everything the race carries: rules, ghosting, anticheat, display, timers, phases. |
What does not
Section titled “What does not”| Left behind | Why |
|---|---|
| The map | A code is a route on a map. Pasting a Utah race into a server running Italy gives you gates in mid-air. |
| The author | The receiving server stamps whoever imports it. |
| Recorded times | A leaderboard belongs to one server’s copy of a race. |
| The race’s internal id | The receiving server assigns its own. |
Positions are rounded to the millimetre, which makes a code roughly a quarter of the size with no difference you can drive.
It is validated like any other save
Section titled “It is validated like any other save”This is the important part for anyone worried about pasting a stranger’s code:
A malformed or hostile code cannot do anything a race editor could not do anyway. An invalid one is simply rejected: That doesn’t look like a valid race share code.
When the buttons are not there
Section titled “When the buttons are not there”Share codes need compression support in the game’s interface layer. Where it is missing the two buttons are hidden rather than shown broken, and an attempt elsewhere reports Race share codes aren’t supported by this game version.
If you cannot see the buttons and your server is current, that is the reason — not a permission.
Practical notes
Section titled “Practical notes”- Check the map first. A code carries no map name, so it is on you and whoever you give it to to say which map it was built for. Put it in the message.
- Rename on import if you must. A name already used on the receiving server will refuse to save; change it in Race Info before saving.
- Importing into an existing race replaces it. If you want to keep both, import into a new race, or use Save as new race afterwards.
- A pit lane needs the race to stay loopable. It travels intact, but the usual rules still apply on the other side.
- The race editor — everything a code is carrying.
- Importing a map’s own races — the other way to get races you did not build.
- Where your data lives — where an imported race ends up on disk.