Skip to content

Groups and permissions

Every player on a BeamJoy server is in exactly one group. The group sets how many vehicles they may have out at once, whether they count as staff, and which of BeamJoy’s actions they are allowed to take.

BeamJoy ships with six, listed here from least to most authority. That order is the hierarchy, and owner has to stay at the end of it.

Group Vehicles Staff Notes
default 1 no where a brand-new player lands
player 2 no may vote on maps and kicks, and teleport to others
vip 5 no counts as whitelisted, and may spawn trailers
mod 10 yes moderation and every activity editor
admin no limit yes server settings, bans, the player database
owner no limit yes permissions and core settings

A vehicle cap of -1 in the data files means no limit. The vip group is whitelisted by its group rather than by name, which is what makes it useful on a whitelisted server.

From the server console:

bj group PlayerName mod

Leave the group off to read a player’s current one back. Staff can also do it from the config window in game, if their own group holds SetGroup — mod does by default.

Every privileged action in BeamJoy is gated on a named permission, and each permission has a default group. A player in that group, or any group above it, may take the action.

A group can also be granted a single permission outright, above its place in the hierarchy, without being promoted — that is how you let player run one thing mod normally owns, rather than moving the whole permission down for everybody.

default — everyone, including a guest

SendPrivateMessage

player

TeleportTo, VoteMap, VoteKick

vip

SpawnTrailers

mod

BypassModelBlacklist, SpawnProps, TeleportFrom, DeleteVehicle, Kick, Mute, Whitelist, SetGroup, TempBan, FreezePlayers, EnginePlayers, SwitchMap, EditRaces, EditSafeZones, EditVehiclePresets, EditHunterArenas, EditInfectedArenas, EditDerbyArenas, EditFreeroamData, EditBusLines

admin

SetConfig, EditPluginConfig, Ban, DatabasePlayers, SetEnvironment, SetMaps

owner

SetPermissions, SetCore, SetCEN

The table above is the shipped default, not a fixed rule. SetPermissions is owner-only precisely so that the group required for any individual permission can be moved, and the result is saved in permissions.json — see where your data lives.