Where your data lives
BeamJoy keeps every setting, record and player row in one folder, created on first boot beside the plugin:
BeamMP-Server/└── Resources/ └── Server/ ├── BeamJoyServer/ the plugin └── BeamJoyData/ your server's own dataBeamJoyServer is replaced wholesale by an update. BeamJoyData is everything your server
has accumulated.
The split is the thing to remember. BeamJoyServer is the program and is disposable: an update
overwrites it, and a fresh copy of the same version behaves identically. BeamJoyData is
yours and exists nowhere else.
What is in it
Section titled “What is in it”The databases are plain JSON under BeamJoyData/db, so they can be read, diffed and kept in
version control if you want to.
| Path | Holds |
|---|---|
config.json |
the server’s BeamJoy settings |
core.json |
the server’s name, description, map and player and car caps |
groups.json |
your groups, their vehicle caps, colours and staff flags |
permissions.json |
which group each permission requires |
whitelist.json |
the whitelist |
players/ |
one file per account: group, language, mutes, bans, last IP |
activities/ |
races, arenas, routes and their leaderboards, per map and type |
maps.json |
the maps the server knows about and offers |
environment.json |
time, weather and the rest of the environment state |
vehiclePresets.json |
saved vehicle presets |
vehicleBuilds.json |
saved vehicle builds |
vehicleBuildPhotos.json |
their photos, as base64 JPEG |
staffAuth.json |
hashes of the staff and owner passwords, never the passwords |
bundled/ |
the races and arenas BeamJoy ships with, refreshed on each start |
Guests are never written to players/. Only players with a BeamMP account get a file, which is
also why a guest’s recorded time is kept against a name rather than an account.
The bundled folder is not yours to edit
Section titled “The bundled folder is not yours to edit”bundled/ is a mirror of the content shipped inside the release, rewritten whenever a file’s
bytes differ from what the installed version carries. Edits to anything in there are overwritten
on the next start.
A shipped course that you have changed through the in-game editor is a different matter: it
becomes a race on your server, lives in activities/, and keeps its recorded times. A later
release that fixes that same shipped course will still overwrite it, as a shipped fix always
does.
core.json writes your BeamMP config
Section titled “core.json writes your BeamMP config”The entries in core.json are not BeamJoy’s own settings — they are your BeamMP server’s name,
description, map, player cap, car cap and private flag. Changing them through BeamJoy rewrites
the server’s ServerConfig.toml to match. That is why they are owner-only, and why a change
made there and a change made by hand in ServerConfig.toml are the same change.
Moving a server
Section titled “Moving a server”Stop both servers, copy BeamJoyData across, install the same version of BeamJoy or a newer
one, and start.