Private-server owners and authorized moderators can open the command bar with F2 on keyboard or the terminal control beside the chat bar on supported mobile and console interfaces. Start with help or cmds; the current command list and autocomplete are safer than memorizing an older table.
Open and test the console
Join the correct private server and confirm owner or moderator status. Open the terminal, enter help, and inspect the current suggestions. Test a harmless information command or a command targeting yourself before affecting another player.
If the console does not appear, check permissions, device UI, server type, and whether the interface has finished loading. A public server does not grant private-server admin controls.
Base command index
help / cmdsList current commands and syntaxRun this before using any copied command.bringMove a selected player to the administratorUse on yourself or a consenting test player.fly / flightToggle flight for a selected playerConfirm the target and a safe landing area.freezeFreeze a selected player's movementUse only for moderation or an agreed scene and remember to restore control.weatherGet, set, lock, or unlock server weatherRead current syntax and announce a scene-wide change.espToggle the documented player-outline viewUse only within current admin permissions and server rules.platformReport the server platform contextUse as an information check.Target selectors can include forms such as @me, @all, @others, @random, or a player identifier, depending on the current command. Never assume every command accepts every selector. Autocomplete and help decide the live syntax.
Package commands
The Roleplay Server Package adds command families such as health, respawn, arrest, release, wanted level, vehicle repair or refuel, and mission control. V3.16 also announced item commands for roleplay-server moderators. These commands require the package, activation, and current permission.
Player state
Health, respawn, arrest, release, wanted
Use for an agreed scene or legitimate moderation. Check the target twice and understand the roleplay data warning.
Vehicle state
Repair, refuel, or health
Confirm the current subcommand and the target player's vehicle before executing.
World state
Mission and weather
Announce server-wide scene changes and stop test missions after validation.
Avoid command mistakes
Use @me before @all. Prefer autocomplete to copied punctuation. Announce disruptive changes. Keep an owner available when testing new package features. Do not use commands to impersonate staff, harass players, bypass server rules, or force unwanted scenes.
The maintained Private Servers command reference was checked for the base command families on October 26, 2026. Use the live help result as the authority for current names and arguments.
Command test protocol
Create a closed test session with the owner and one consenting moderator or player. Run help, capture the current autocomplete, and test information commands first. For a player-state command, target @me; for a vehicle command, use a disposable test vehicle; for weather or missions, announce the change and restore the original state.
Record the exact command family, action or subcommand, accepted target, result, permission role, package state, and date. Do not publish a guessed argument when autocomplete rejects it.
Recover from a mistake
If the wrong player is frozen, moved, or affected, reverse the state through the supported command or admin application and explain the correction. Stop a test mission after it completes. Restore weather or access settings when the event depends on the prior state. If no reversal is available, the owner should use the least disruptive supported reset and warn players before shutdown.
Permission troubleshooting
Confirm that the server is private, the account is owner or moderator, the relevant package belongs to this server, and the feature is enabled. V3.16 changed some group connections and added moderator item-command support, so old group-rank setups may need review. If help omits a copied command, treat it as unavailable rather than repeatedly submitting it.
Keep the live command list as the final authority.