Choose a BeamMP Plan
Pick Basic for friends/private, Club or Community for public servers. Scales with slots and features.
Set up, manage, and troubleshoot your BeamMP server with step-by-step guides.
🛠 Getting Started
Access Your Game Panel
Use the welcome email to log in, view your server, console, IP:Port, and metrics.
Add Your Server Key (Keymaster)
Paste your BeamMP Keymaster key under Startup → Authentication Key, then restart.
Name, Description & Privacy
Set server name/description and choose Private (direct connect) or Public (listed).
⚙ Server Management
Set Map (Vanilla & Custom)
Use paths like /levels/gridmap_v2/info.json. Custom maps: lowercase level folder.
Max Cars per Player
Control per-player vehicle count via Max Cars in config.
Update BeamMP Server
Reinstall for vanilla or upload new BeamMP-Server-linux and set perms to 755.
Scheduled Tasks & Backups
Use the panel’s Schedule to automate restarts and backups for stability.
🧩 Advanced & Mods
Install Mods (Client/Server)
Upload .zip mods to /Resources/Client. Don’t extract. Keep versions current.
Colored Server Names
Use codes like ^4 for red: ^4My Server. Combine styles for emphasis.
🧯 Troubleshooting
Server Not Showing in List
Verify key is valid, server isn’t set to Private, version matches client, and outbound is allowed.
Crashes After Adding Mods
Stop server → remove recent mod .zip → restart. Add mods one by one and check console.
Choose the right plan based on player count, mod usage, and whether your server is public or private.
- Basic: friends/private, light mods, low player count.
- Club: public listing, moderate player counts, common mods.
- Community: higher slots, heavy mod lists, scheduled backups.
Tip: start small and scale up instantly from the Client Portal as your player base grows.
Your welcome email includes panel credentials. From the panel you can start/stop, view console, manage files, and schedule tasks.
- Open the panel and sign in.
- Select your BeamMP server → Console for live logs.
- Use Files to upload configs, maps, and mods.
- Set up Schedules for restarts and backups.
Use a Keymaster server key to authenticate your server and enable public listing.
- Visit Keymaster and create a new key.
- Copy the key string.
- Game Panel → Startup → paste into Authentication Key.
- Restart the server to apply.
If you rotate keys, always restart the server afterward.
Control how your server appears and who can join.
- Name: concise and descriptive (use color codes if desired; see “Colored Server Names”).
- Description: include rules, map, and mod pack highlights.
- Privacy:
- True: hidden from the list; players join via Direct Connect using IP:Port.
- False: listed for everyone; requires valid Keymaster key.
Point to the level’s info.json. For custom maps, ensure lowercase folder names.
Vanilla examples
/levels/gridmap_v2/info.json
/levels/automation_test_track/info.json
/levels/east_coast_usa/info.json
/levels/hirochi_raceway/info.json
/levels/italy/info.json
/levels/jungle_rock_island/info.json
/levels/industrial/info.json
/levels/small_island/info.json
/levels/smallgrid/info.json
/levels/utah/info.json
/levels/west_coast_usa/info.json
/levels/driver_training/info.json
/levels/derby/info.json
Custom map
- Open the map .zip locally → find
/levels/<mapname>/info.json. - Upload the zip to
/Resources/Client(don’t extract). - Set Startup map path to
/levels/<mapname_lowercase>/info.json. - Restart the server.
If the server fails to load after a map change, revert to a vanilla map and check console logs.
Limit how many vehicles each player may spawn to reduce lag and griefing.
- Open Startup in the panel.
- Set Max Cars to a sensible value (e.g.,
1for strict control). - Restart the server to apply.
Keep your BeamMP server binary up to date for compatibility and stability.
- Stop the server.
- Upload the latest
BeamMP-Server-linuxinto the server root. - Set permissions for the file to
755(executable). - Start the server and watch the console for errors.
Use BeamHost scheduler to automate restarts, backups, and announcements. A schedule has: when it runs (cron timing), and one or more tasks (actions) that run at that time, each with an optional delay.
How scheduling works (Pterodactyl)
- Open Schedules in the Game Panel and click Create New.
- Fill the cron timing (Minute, Hour, Day of Month, Month, Day of Week) and leave the schedule Enabled.
- Save, then open the schedule and click New Task to add actions in the order they should run:
- Send command — runs a command in the server console (great for chat messages).
- Power action — Restart, Start, Stop, or Kill the server.
- Backup — creates a backup (configure ignored files if needed).
- Optionally set a Time offset (seconds) on each task to space them out (e.g., warn players, then restart).
- Click Run now once to test and confirm logs show execution.
Timezone: Schedules use the panel/server timezone. If times look off, check your panel/user timezone settings.
Common cron patterns
Every day at 05:00
Minute: 0
Hour: 5
DOM: *
Month: *
DOW: *Every 6 hours (on the hour)
Minute: 0
Hour: */6
DOM: *
Month: *
DOW: *Mondays at 03:30
Minute: 30
Hour: 3
DOM: *
Month: *
DOW: 11st of each month, 04:00
Minute: 0
Hour: 4
DOM: 1
Month: *
DOW: *BeamMP commands you can schedule (via “Send command”)
help # Show command help
exit # Gracefully shut down the server
kick <name> [reason] # Kick a player with optional reason
list # List players and info
say <message> # Broadcast a message to chat
settings [command] # Manage server settings (see `settings help`)
status # Show current server status
clear # Clear the console
version # Show server version
Tip: Use
say for announcements (warnings before restarts, “back online” messages, etc.).
Example: nightly backup + restart with warnings
Goal: 05:00 daily restart with a backup before, and chat warnings at T‑3 min and T‑30 sec.
- Create a schedule with timing: Minute 0 · Hour 5 · DOM * · Month * · DOW *.
- Add tasks in this order:
- Send command:
say Server will restart in 3 minutes for maintenance.(Offset: 0) - Backup: (Offset: 60) — start backup 1 minute after the first warning.
- Send command:
say Restart in 30 seconds… finish your run!(Offset: 150) - Power action: Restart (Offset: 180)
- Send command:
say Server is back online — have fun!(Offset: 300)
- Send command:
Example: announce an event every Saturday at 18:00
- Timing: Minute 0 · Hour 18 · DOM * · Month * · DOW 6
- Task: Send command →
say Saturday race night starts now! Join voice & follow the rules.
Example: restart every 6 hours
- Timing: Minute 0 · Hour */6 · DOM * · Month * · DOW *
- Tasks:
- Send command:
say Quick restart in 30 seconds to keep things smooth.(Offset: 0) - Power action: Restart (Offset: 30)
- Send command:
Best practices: Don’t stack heavy backups and restarts at peak hours. Keep warnings short, and always test a new schedule with Run now first.
Install mods as .zip files in /Resources/Client. Do not extract.
- Stop the server.
- Upload mod .zip files to
/Resources/Client. - Start the server and check Console for errors.
- Add mods one at a time to quickly isolate problems.
mods.json is automatically created and managed by BeamMP-Server. There is no need to edit it's contents.
Type your title/description, highlight parts, then click a color to apply. The formatted code string updates automatically.
Color codes quick reference
^r Reset ^p Newline ^n Underline ^l Bold ^m Strike ^o Italic
^0 Black ^1 Blue ^2 Green ^3 Light Blue
^4 Red ^5 Pink ^6 Orange ^7 Grey
^8 Dark Grey ^9 Light Purple ^a Light Green
^b Light Blue ^c Dark Orange ^d Light Pink
^e Yellow ^f White
Type your server title here, highlight a part, then click a color above to apply.
^6Server ^aTitle. Colors persist until changed.
Example: ^4High Altitude ^7Racing
If your server doesn’t appear publicly, check the following:
- Server is Public (not Private) in config.
- Valid Keymaster key pasted correctly; restart after changes.
- Server version is latest stable release.
- No startup errors in console; resolve and restart.
- Server port is correctly configured (if applicable)
Crashes or kicks after new mods usually indicate a conflict or corrupted file.
- Stop the server and remove the most recently added mod.
- Start the server and test with players.
- Re-add mods one at a time; watch the console for stack traces.
- Prefer actively maintained mod versions; avoid duplicates.
- Always keep mods as .zip files—do not extract.
- Ensure mods names are plain text without spaces or special characters.
If the server still crashes without mods, revert map to a vanilla level and re-test.
