Dashboard, console, restarts and raid times

This part of the administration is used for the daily operation of the server: quick health check, safe command submission, setting of regular restarts and management of raid times. Normal saving of settings does not restart the server.

Daily control on the dashboard

Open the SCUM dashboard. The Server and schedule tab shows the selected server, the current connection, the next reboot and AutoChat status. Below you will find the latest kill feed and leaderboard, so you can quickly see if new data is coming in.

1. Check the correct server in the top bar.
2. Verify that both the server and the agent are online and the data is not marked as out of date.
3. Check the next scheduled reboot.
4. If you are resolving an incident, only then proceed to the console or logs.

Events

The Events page is, in the current version, a ready space without user functions. Planned community events are managed in the respective game modules or public content; this page does not replace them yet.

Safe use of the console

The authorized owner or SCUM administrator will find the console at SCUM console. The command passes through the managed channel NODERA-RCON and its result is recorded in the history.

1. Verify the selected server and the freshness of NODERA-RCON.
2. Enter a supported command.
3. Optionally add a note on why you are sending the command.
4. Send it and track the resulting status in history.

A status of "queued" or "submitted" is not yet a confirmation of success in the game. The final result is decisive. When a timeout occurs, do not automatically execute the command a second time - first verify that the first attempt was not reflected in the game.

Setting NODERAgent

On the NODERAgent page, the frequency of data collection and processing is set for individual servers. Here you will find a regular contact interval, player synchronization, pending actions check, log reading, regular reviews, backups and security limits.

A lower interval brings fresher data, but at the same time more work for the agent and the database. Only change a value whose consequence you know. LIVE map and player interval have their own LIVE settings page. Saving intervals does not require restarting the game.

Regular and manual restarts

At SCUM settings you can turn on the schedule, specify the start of the cycle, repeat in hours and time zone. Saving the schedule will only change the future schedule; does not trigger an immediate restart.

There are separate manual actions on the same page:

• Restart – normal shutdown and restart of the server.
• Update + Restart - use only when updating is scheduled.
• Soft, Gold or Full wipe – major interventions in the game world with precise confirmation text.

After each manual action, track the history, the final result and confirm that regular NODERAgent contact has resumed. Clicking the button alone is not proof of a successful server return.

Raid times

On Raid Times you create one or more time windows. For each one, you set the name, active days, time from-to, and notification advance before opening and closing.

1. Add or edit a raid window.
2. Select the days and time in the displayed time zone.
3. Use Save if you only want to prepare the change.
4. Use Save and Write if Nodera is to create the resulting configuration for the server.
5. Check the preview of effective days and times.

Example from Main

As of 1 September 2026, Main had an automatic restart every 6 hours in the Europe/Bratislava time zone. The next cycle was scheduled for 18:00 at the time of the check. Raid windows were Monday-Thursday 16:00-22:00 and Friday-Saturday 16:00-24:00; Sunday was not active. In the last 24 hours, 175 commands have completed successfully.

When something doesn't fit

• I can't see the console: check the role and permission to the server.
• Command pending: verify last contact NODERAgent, NODERA-RCON and final status in queue.
• The schedule changed but the server did not restart: that is correct; the change is valid for the next term.
• The raid time in the game does not fit: check the time zone, days, preview and whether you also used the Write action.