Verify it is working

The one line that matters

In your server console after o.reload Cerebrust:

CerebRUST ingest initialized.

If you see that, the token was accepted, your server is bound, and data is flowing. Everything else on this page is about how quickly each part of the dashboard fills in.

Then check the dashboard

Sign in at app.cerebrust.xyz with the Steam account the token was issued to, and open My servers. Your server should be listed with its name and player count.

How long each thing takes

Not everything appears at once, and the delays are by design. Before concluding something is broken, check what you are waiting for:

What	When it appears
Server in My servers	Immediately after init
Players online, server FPS	Within 15 seconds (heartbeat)
Players on the live map	Within a few seconds of someone moving
Chat	As it is sent
Tool cupboards	Within 5 minutes (snapshot cycle)
Monuments	Once, shortly after init
Teams and bans	A few seconds after init
Map image	Only uploads when no players are online — see below
Leaderboard	On the hourly compile

The map is blank until the server is empty

The map render is a large upload, so the plugin waits until nobody is connected before sending it. On a busy server that can mean waiting for a quiet hour or a restart.

Until then the live map has no background image — markers still work, they just sit on nothing. A new map is only uploaded when the world actually changes, i.e. at wipe.

Verbose logging

If you need to see what the plugin is doing, set verbose_logging to true in oxide/config/Cerebrust.json and reload. Every ingest call, world scan and HTTP result is logged.

{
  "ApiBaseUrl": "https://api.cerebrust.xyz",
  "IngestToken": "crst_your_token_here",
  "verbose_logging": true
}

Turn it off again once you are done. It is genuinely very noisy and will bury the rest of your console output.

It initialised, then went quiet

The plugin is built to recover on its own. If CerebRUST is briefly unreachable, the affected endpoint pauses and retries with a backoff of up to two minutes, and queued events are replayed when it recovers. A watchdog re-checks every two minutes while the plugin is uninitialised, so a bad start-up heals itself without you running o.reload.

So short gaps are expected and self-correcting. If it stays quiet for more than a few minutes, go to Troubleshooting — and check status.cerebrust.xyz first.