Settings and synchronization
Account, project, server and extension settings have different scopes. Check the selected server and role before editing. Saving a value in the database and delivering it to a running extension are separate stages.
Settings scopes
| Scope | Settings | Where to check |
|---|---|---|
| Account | Theme, security, sessions, profile | Account interface and SSO; individual fields depend on migration coverage |
| Project/server | Name, addresses, game, moderation, subscription | Project/server management |
| Panel and integrations | RCC, Discord, inspection rules, staff permissions | Selected server settings |
| CloudConfig | Values consumed by the running game extension | Network modules/sub/ServerConfig.js and adapter contract |
| Local adapter | Project/server ID, Network host, server token | Private server configuration directory |
ServerConfig owns server_params. Reads/updates use GetOrCreateServerConfig. Plugin-facing CloudConfig retains PascalCase, such as AutoAfkKick and AutoAfkKickTime. Database-only integration settings use snake_case, such as rcc_api_key, rcc_sync_bans, rcc_grant_access. UI payloads may use camelCase; the backend maps them.
Changing settings
- Open the intended server and wait for current values to load.
- Change a value permitted by your role and feature matrix.
- Wait for save confirmation. With autosave, keep the tab open until confirmed.
- For game settings, check extension connectivity and actual configuration application.
The backend calls ApiNet.PushServerConfig for runtime settings. A database-only integration change does not necessarily reload the plugin. An offline extension cannot be assumed to have applied a saved value.
Game boundaries
Discord/RCC settings and CRUD do not inherently need game branches. Drawings, traps, sleeping bags and some commands do depend on the adapter. A field in a shared form does not establish that a Rust setting works in Minecraft.
Local configurations contain credentials. Keep them out of Git, tickets and screenshots. Server tokens, account access_token values and CheckerSession codes are not interchangeable.
Sources: modules/sub/ServerConfig.js, socket/client/Server.mjs, .web/.../panel/settings, Rust Configuration/Config.cs, Minecraft adapter READMEs.
Integrations · Access · Errors