Nodera / Documentation

The essentials, all in one place.

Players, grants, VIP, bans and strikes

A complete guide to player profiles, roles, rewards, VIP conditions, community bans and a transparent strike system.

On this page

Player management combines current status on the server, long-term profile, game rewards and community moderation. Individual tools have a different scope: a profile is tied to a selected server, while a ban or strike can apply to the entire community.

Current and all players

Online Players shows currently connected sessions. All Players contains known profiles of the selected server including first and last seen, role, squad and available links.

Click on the row to open the profile. Changing the player role is saved immediately, so please verify the correct player and server before saving.

Grants and withdrawal of values

On Player Grant you can add or remove Money, Gold, BTC or Fame from a player.

  1. Search for a player using autocomplete.
  2. Select a value type and enter an amount.
  3. Complete an internal note to make the reason traceable.
  4. Choose to send a grant or withdraw it.
  5. Check the final result and player profile.

For each type of grant and withdrawal, it is possible to modify the message sent to the player - eight templates in total. The game message will be sent only after the confirmed execution. BTC uses its own transaction records and the change is reflected directly in the wallet.

VIP and linked accounts

VIP is not just a switch in admin. The player needs a linked Steam, Google and Discord account and at the same time the correct SCUM role VIP or admin. In Player Settings, you can see the readiness of links, role sync interval and notification history.

The email notification switch for command /admin only affects sending email. It does not create or destroy the VIP role.

Community bans

Banlist is shared by the community. For each ban, Nodera tracks the delivery to individual servers, so you distinguish the decision to ban from its actual execution.

  1. Verify the player's identity and proof in the relevant log.
  2. Check the reason and scope of the ban.
  3. Follow the result for each server after saving.
  4. For unban, check the separate delivery result again.

A ban or unban is not considered done just because it was queued. It decides the final result on the target server.

Strikes and automatic penalties

On Strikes you enter the points, name, category and understandable description of the offense. The current boundaries are:

BodyAutomatic consequence
3Ban for 48 hours
5Ban for 7 days
8Ban for 1 year

Game announcement is set for each server - SendChat or Announce method, color and text. Community Discord template is shared. The owner can nullify all player strikes. Cancellation will only remove the ban that originated from the given system; other separate ban remains unaffected.

Example from Main

As of 1 September 2026, Main recorded 182 known identities and 3 open player sessions at the time of the audit. There was 1 active strike record and 4 canceled records in the community. The banlist contained one already removed ban where both the ban and unban were successfully delivered to Main. All eight grant messages have been configured.

Recommended checklist

  • Is the correct server and correct player selected?
  • Is the change server or community?
  • Does the decision have a clear note and proof?
  • Is the final delivery successful on all target servers?
  • At VIP: are all three accounts linked and role synced?

Privacy and cookies

You control cookies.

We use necessary cookies to keep the website working. Analytics and marketing cookies are enabled only after your consent. Read our Cookie policy and privacy policy. You can withdraw or change consent at any time through this setting.