Skip to content

Install on your server

BeamJoy is installed by unpacking one zip into your BeamMP server’s Resources folder and restarting the server. There is no installer, no build step and no database to create.

You need a BeamMP server you can put files on and restart. Stop the server before copying files in — BeamMP watches everything under Resources/Server and reloads changed files, and letting it watch a half-finished copy only produces noise in the log.

Take the BeamJoy-Revived-<version>.zip asset from the releases page.

Inside the zip are two folders:

Server/
├── BeamJoyServer/ the plugin
└── BeamJoyServerHooks/ chat and console
Client/
└── BJ.zip sent to players

Unpack the zip into your server’s Resources folder, so that its Server and Client folders merge into the ones already there. When you are done, these three paths exist:

BeamMP-Server/
└── Resources/
├── Server/
│ ├── BeamJoyServer/ the plugin
│ └── BeamJoyServerHooks/ chat and console
└── Client/
└── BJ.zip sent to players

Unpack into Resources, not into Resources/Server. Unpacking one level too deep leaves you with Resources/Server/Server/BeamJoyServer, which BeamMP will not load, and no client mod at all.

On the first start with BeamJoy present, the plugin creates Resources/Server/BeamJoyData and writes its databases into BeamJoyData/db — settings, groups, permissions, the maps it knows about, and the races and arenas it ships with. See where your data lives for what ends up in there.

Your players need to do nothing. BeamMP sends them BJ.zip when they connect, and sends the new one automatically after you update.

A fresh install gives nobody any authority over it, including you. Claiming ownership is a console command, and it is the step that unlocks the settings, the editors and the moderation tools: first boot and ownership.