Community administration
Connect your game server
Generate a game server key, add it to server.cfg, set your community slug, and bring the in-game tablet online.
Owner only, once per community. Managers see the panel but cannot generate a key.
1. Generate the key
- Open platenet.app/backpanel and stay on OVERVIEW.
- Scroll to GAME SERVER LINK.
- Press GENERATE KEY, then COPY.
The key is shown once. Keep it out of your repository, screenshots and Discord.
2. Copy your community slug
Open Game server setup in the same panel. Copy CommunitySlug exactly as written - lower case, hyphens included. GameUrl is already correct.
3. Add the resource
Take the resource from github.com/scentral/platenet and put it in your server's resources folder. The folder is named:
platenet
Do not rename it.
4. Set the key in server.cfg
## PlateNet
set platenet_api_key "YOUR_API_KEY_GOES_HERE"
add_convar_permission platenet read platenet_api_key
add_ace builtin.everyone command.platenet_api_key deny
ensure platenet
Replace YOUR_API_KEY_GOES_HERE with the key from step 1 and keep the quotes. All four lines are required - the permission line lets the resource read the key, the ace line keeps players from reading it.
5. Set the slug in config.lua
Config.CommunitySlug = 'your-community'
Paste the slug from step 2. Leave Config.GameUrl and Config.UpdateUrl as shipped.
6. Restart and confirm
Restart the game server. The console prints:
[platenet] v1.8.3 ready.
[platenet] Connected.
Last seen from your game server in GAME SERVER LINK turns CONNECTED.
7. Pair the tablet
Each member pairs their own device once, from their own browser:
- In game, press
F6or run/platenet. - Copy the
PN-.....-.....code. - Sign in at platenet.app, open platenet.app/device, enter the code.
- Check the preview and approve.
Full flow, including going on duty and position reporting, is in linking your game session.
Rotating and revoking
GENERATE NEW KEY replaces the key immediately - the game server stays disconnected until the new key is in server.cfg and the server restarts. REVOKE KEY disconnects it and leaves it disconnected. Both kill every token the old key issued. Paired devices survive a rotation.
If it does not connect
| The console says | Do |
|---|---|
| Setup required: add platenet_api_key to server.cfg. | Add the block in step 4 and restart. |
| Setup required: set Config.CommunitySlug in config.lua. | Paste the slug from step 2. |
| Setup required: set Config.GameUrl in config.lua. | Restore the shipped Config.GameUrl. |
| Setup required: Config.GameUrl must use HTTPS. | Restore the shipped Config.GameUrl. |
| Connection failed. Check the PlateNet setup. | The key and the slug do not belong to the same community. Regenerate and recopy both. |
| Update required. PlateNet stopped. | Replace the resource with the current release and restart. |
| Too many requests. Try again shortly. | Wait a minute before restarting again. |
| Live positions are unavailable. Enable OneSync. | Turn OneSync on. Everything else works without it. |
| The panel says | Do |
|---|---|
| NOT SET | No key has been generated. Start at step 1. |
| NEVER USED | The key is live and the game server has not reached it yet. Recheck steps 4 to 6. |
Back to the PlateNet documentation index / All Community administration pages