ANEURISM IV/Server administration
Join your server with its owner account to assign staff and manage access. Open the in-game console with the backquote key (`) or your chosen Console binding, then enter help to list commands.
The dedicated server's terminal and system journal contain logs. Run the commands below from a connected game client.
Owner and staff
The first host of a new world becomes its owner. A dedicated server takes that account from ANIV_COMMUNITY_OWNER_STEAM_ID. Ownership is saved in aniv.db and can't be assigned with setrank.
| Role | Access |
|---|---|
community.owner |
Full server administration, including staff assignments. |
community.admin |
Server management and moderation. Cannot assign ranks. |
community.moderator |
Admin tools for kicking, banning, announcements, and teleporting players. |
community.vip |
Reserved-slot access. No staff commands. |
community.user |
Ordinary player access. This is the default role. |
Staff can act only on players below their own authority. They can't moderate themselves or another staff member of equal authority. Nexus staff ranks don't grant local server powers.
Assign or remove a rank
As the owner, run:
setrank <player|steam-id> <community.admin|community.moderator|community.vip|community.user>
Replace the bracketed arguments with the player and role. A SteamID64 also works when the player is offline. Assign community.user to remove a staff or VIP role.
Bans
ban <player|steam-id> [permanent|30m|12h|7d|4w] [reason]
unban <player|steam-id>
The duration is optional; omitting it makes the ban permanent. Durations use m for minutes, h for hours, d for days, and w for weeks. The values above are examples. Banning a connected player also disconnects them.
A local unban removes your server's ban. Nexus bans are checked separately. If a player still can't join after an unban, read the rejection message before changing other settings.
Whitelist
whitelist add <player|steam-id>
whitelist remove <player|steam-id>
printwhitelist
Use a password for private hosting in this version. The whitelist also checks staff on reconnect, but the command won't let you add yourself or the owner. Enabling it can prevent you from rejoining your own server.
An empty whitelist allows ordinary admission. Adding the first entry enables the whitelist; removing the last entry disables it. If you've enabled it during a session, remove its entries before disconnecting. Ban and password checks still apply.
Owners and administrators can change entries for players below their authority. See A player cannot join if a whitelist change has an unexpected result.
Password
password [new-password]
With a value, this changes the password for new joins. With no value, it removes the current password. Passwords can contain up to 64 characters and must not contain line breaks or control characters.
The console omits password values from its history and audit output. For a dedicated server, also edit ANIV_SERVER_PASSWORD in server.env if you want the change to survive a restart. An in-game host must enter the password when starting the next session.
Keep administration data
Ranks, bans, ownership, and whitelist entries are stored in aniv.db. They survive restarts and gameplay world wipes. Back up the whole data directory to keep them with the world.