V Rising Server Admin Commands and How to Use Them (PC v1.1.x)

To make yourself an administrator on a V Rising PC server, add your 17-digit SteamID64 to adminlist.txt, enable the in-game console, open it with ~, and run adminauth. That permission lasts for the current session, so you must authenticate again after reconnecting. The console is the full native command surface; RCON is a separate, smaller interface for remote server management.

This guide covers the current official v1.1.x dedicated-server branch, the exact file locations and settings, practical command syntax, RCON limits, and a safe workflow for moderation and world-changing operations. Patches can add, remove, or rename commands, so use list on your live server as the final authority.

What are V Rising admin commands, and where do I enter them?

V Rising has three different command surfaces that are often confused:

• In-game developer console: the native admin and debug interface. After adminauth, it exposes the command catalog available in your running build.
• RCON: a separate TCP service for a limited set of remote server-management commands.
• Chat: vanilla V Rising has no built-in slash-command system. Dot-prefixed chat commands normally come from a mod such as VampireCommandFramework, not from the native server console.

Native console commands are entered by name, without a leading slash. For example, use listusers true, not /listusers true. The community catalog currently shows 196 entries because it includes player-facing, hidden, and debug commands; many are inappropriate for routine administration. Run list on the server you actually operate to see the commands and syntax that build supports.

What do I need before administering a V Rising server?

The official dedicated server is free through Steam’s Tools section. If you install it with SteamCMD, the application ID is 1829350. Keep track of the installation folder, the launch parameters, and the persistent-data path before changing permissions. A server launched with -persistentDataPath .save-data does not use the default save location for its settings; all administration files must be edited under that custom path.

Self-hosting also means maintaining firewall rules, forwarding the configured ports, applying updates, and backing up saves. A managed host can handle much of that work, but you still need to understand the files and session-based authentication when troubleshooting commands.

How do I make myself an admin on a V Rising server?

Complete the file step first, then authenticate in the game. Eligibility comes from adminlist.txt; adminauth grants the permission to your current connection.

1. Find the persistent data folder. If the server starts with -persistentDataPath .save-data, its settings are in save-dataSettings. With no custom path, the Windows default is %USERPROFILE%AppDataLocalLowStunlock StudiosVRisingServerSettings.
2. Open adminlist.txt. Put one 17-digit SteamID64 on each line. Use IDs only: no character names, quotation marks, commas, or comments.
3. Save the file. Stunlock’s instructions state that this can be done without restarting the server. A running server may take a short time to re-read the file, so allow a moment before testing.
4. Enable the console in V Rising. Open Options > General, turn on Console Enabled, and return to the world.
5. Open the console. Press ~ (often the backtick key, immediately below Esc on a US keyboard).
6. Authenticate. Type adminauth and press Enter. If your SteamID64 is in the file, the session receives administrator rights.
7. Verify the live command set. Run list. You can also use list <category> where supported. Do not mistake list for autocomplete of listusers.

Run adminauth again after every reconnect or restart. Authentication is session-based even though the ID in adminlist.txt controls who is allowed to authenticate.

How do I check that admin authentication worked?

After entering adminauth, run a harmless discovery command such as list or servertime. If the console reports an unknown command or refuses an administrative operation, reconnect, open the console again, and authenticate once more.

• Check that the ID is the account’s SteamID64, not a display name or a shorter Steam identifier.
• Make sure each ID occupies its own line and that the file is named exactly adminlist.txt.
• Confirm that you edited the settings directory used by the running instance, especially when a launch parameter sets -persistentDataPath.
• Use the live list output rather than a copied command list from an older branch.

Which V Rising commands are most useful for moderation?

Moderation commands can disconnect, ban, or mute players. Character-name commands require the exact in-game character name; SteamID commands are preferable when a player is offline or names are ambiguous.

Command	Purpose and syntax	Operational note
kick <Character Name>	Disconnects the named player.	Use the exact character name.
bancharacter <Character Name>	Bans by character name.	Useful while the player is online.
banuser <SteamID>	Bans by SteamID64.	Works even when the player is offline; use the full ID.
bancharactertemp <Character Name> <Amount> <Unit>	Creates a temporary character-name ban.	Enter the amount and a unit accepted by the live build.
banusertemp <SteamID> <Amount> <Unit>	Creates a temporary SteamID ban.	Prefer this for a persistent identity.
banned	Lists current bans and their indexes.	Run it immediately before removing a ban.
unban <User Index>	Removes the ban at the displayed index.	Indexes can shift after another ban is added or removed.
setplayermuted <Voice|Chat|Both> <Character Name> <0|1>	Mutes or unmutes voice, chat, or both by character name.	1 enables the mute and 0 clears it, where available in the 1.1 command set.
setplayermutedbyid <Voice|Chat|Both> <Steam ID> <0|1>	Mutes or unmutes by Steam ID.	Useful when the character is not currently online.

Because unban uses a moving index, record the identity before acting and re-run banned if the list has changed. For ID-based certainty, edit banlist.txt directly only after making a backup and stopping or safely maintaining the server.

Which commands show players, time, and server state?

These commands are low-impact ways to inspect or maintain a live server.

Command	What it does	Example
listusers <Include Disconnected>	Lists active users. Passing true includes disconnected users.	listusers true
playerinfo <Character Name>	Prints information about a player.	playerinfo Aria
servertime <Format>	Prints server time in a supported format.	Use the format shown by autocomplete or list.
triggerautosaveonserver	Forces an autosave.	Run before planned maintenance when players are informed.
debugviewenabled <true|false>	Toggles the debug overlay.	Prefer false after diagnostics.
adminonlydebugevents <true|false>	Restricts debug events to administrators at runtime.	Use while investigating an issue, then restore your intended policy.

Which character and world utility commands are available?

Utility commands can change a character or the simulation immediately. Test them on a disposable save or use a maintenance window before applying them to a shared world.

Command	Effect	Important detail
toggleinvulnerable <true|false>	Toggles invulnerability for yourself.	Check the state before returning to normal play.
toggleobserve <0|1|2>	Changes observe or ghost mode.	The numeric modes are build-defined; consult live autocomplete.
addtime <Hours>	Advances world time.	The command has a documented limit; do not assume unlimited values.
changedurability <Amount> [EquipmentType]	Repairs or damages equipped gear.	The equipment argument is optional; use the exact type accepted by your build.
changehealthofclosesttomouse <Amount>	Heals or damages the entity closest to the cursor.	Pause and verify the cursor target before executing.
consumeblood	Sets blood-pool parameters.	Use console autocomplete for the complete argument sequence; do not guess it.

Spawning, teleportation, castle manipulation, and other debug commands may appear in list even when they are absent from a practical command guide. Treat them as high-impact: confirm the target, save state, and arguments before pressing Enter.

What is the difference between the in-game console and RCON?

The in-game console is the correct choice when you need the broad native admin and debug catalog. RCON is useful for remote operations but intentionally exposes a much smaller server-management set; it is not a remote copy of every console command.

Administration method	Reach	Command breadth	Authentication and persistence	Best use
In-game console	Requires joining the server and opening the console.	Live native admin/debug catalog after adminauth.	adminlist.txt controls eligibility; adminauth applies to the current session.	Moderation, diagnostics, and character or world utilities.
RCON	Remote TCP connection.	Smaller server-management set.	Protected by the RCON password and network exposure.	Announcements, status, scheduled shutdowns, and remote configuration actions.
Vanilla chat	Available to players in-game.	No native command system.	Not an admin surface.	Normal communication; mod commands require the mod’s own installation and syntax.

How do I enable and use RCON?

RCON is configured in ServerHostSettings.json. The current official instructions document an enabled flag, a non-empty password, a TCP port, and a bind address.

1. Stop the server or use your host’s safe configuration workflow.
2. Open ServerHostSettings.json in the settings directory used by the running instance.
3. Set Rcon.Enabled to true, choose a strong non-empty RCON password, set the TCP port, and configure BindAddress as required by your network.
4. Save the file and restart the server so the service loads the change.
5. Allow the selected TCP port only where needed. Do not expose RCON broadly to the public internet.

The current secondary command list includes help, announce, announcerestart, shutdown, cancelshutdown, name, description, password, version, and time. RCON should not be expected to spawn items, teleport players, or execute every command shown by the in-game list.

Use RCON for tasks that do not require a player’s character context. For example, an operator can announce maintenance, schedule or cancel a restart, inspect the server version, or check time while away from the game. Keep the password separate from other server credentials, rotate it if it has been shared, and restrict the bind address and firewall rule to trusted administration networks whenever possible.

Which server files and ports matter for administration?

Keep the two JSON files’ roles separate:

• ServerHostSettings.json contains hosting and network settings, including ports and RCON.
• ServerGameSettings.json contains gameplay settings.

The official setup documents a game port and a query port, with example values 27015 and 27016. The game port must be allowed through the firewall, and both game and query ports are needed for server-list visibility. If you changed the defaults, forward and allow the values actually present in your files or launch parameters.

A common failure is forwarding the default ports while the launch script or host panel uses custom values. Check the active ServerHostSettings.json and startup arguments, then apply the same values to the operating-system firewall and router. Query-port access affects whether the server appears in listings even when direct connections still work.

When editing startup scripts, copy start_server_example.bat to a separate file first. Updates can overwrite the supplied example. Keep save backups before patching or launching after a patch, and schedule regular restarts; the official guidance recommends a daily restart for consistency and updates.

How should I use admin commands safely?

Most command failures are recoverable, but a mistaken ban target or world edit can affect every player. Use a least-privilege process:

1. Limit adminlist.txt to trusted SteamID64 accounts and remove obsolete IDs.
2. Back up the save directory before patches, mass moderation, or any debug/world operation.
3. Use listusers, playerinfo, or banned to identify the target before changing anything.
4. Prefer SteamID-based moderation when a player is offline or a character name could be confused with another.
5. Run one command at a time and check the console response. Avoid pasting an unverified batch of destructive commands.
6. Use a test save or maintenance window for spawning, teleportation, castle, time, durability, and health operations.
7. After diagnostics, disable debug overlays and review who still has admin eligibility.

Announce disruptive work before using a shutdown or restart command. Run triggerautosaveonserver when appropriate, wait for the save response, and retain a dated backup rather than overwriting the only copy. If several administrators share responsibility, document which SteamID64 belongs to each person so a moderation action can be audited without relying on display names.

Why is a command missing or rejected?

V Rising maintains separate current and legacy dedicated-server branches. A command copied from another version, a community catalog, or a mod may not exist in your installed build.

• Run list after adminauth and use the capitalization and argument order displayed by the live server.
• Confirm you are in the developer console, not ordinary chat; native commands do not use a slash prefix.
• Re-authenticate after reconnecting because admin rights do not persist across sessions.
• If a character-name command fails, check spelling, spaces, and exact capitalization; use the SteamID variant when available.
• For unban, run banned again because indexes can change.
• If the server is not visible, verify both configured ports, firewall rules, and query-port forwarding.
• If a setting appears ignored, check that you edited the active persistent-data path rather than the default folder for another installation.

Autocomplete is especially important for commands with optional or enumerated arguments, such as servertime, toggleobserve, changedurability, and consumeblood. Do not infer a value from a guide written for an older branch. If the console accepts a command but produces an unexpected result, stop, restore the backup if necessary, and test the syntax on a copy of the world.

Should I self-host or rent a managed server?

Self-hosting gives you direct access to the installation, launch script, persistent-data path, ports, and backup schedule. It also makes you responsible for Windows or Linux maintenance, firewall and router configuration, patch testing, daily restarts, and protecting RCON credentials.

A managed V Rising provider can supply a control panel for status, logs, configuration files, restarts, updates, and permissions. Stunlock’s official hosting guidance names PocketHost as an example of a service for renting and managing a server. Prices, locations, hardware, retention policies, and affiliate terms change, so verify those details with the provider before buying. Regardless of host, the admin workflow remains the same: edit the active adminlist.txt, authenticate with adminauth, and use list to confirm the commands exposed by the installed build.

What should I do before updating the server?

Copy the save files, record custom ports and launch parameters, and preserve your edited startup script. After the update, verify the installed branch, authenticate again, run list, and test a harmless command before allowing normal play. This catches renamed or removed commands before an administrator attempts a destructive operation.

Frequently Asked Questions

Can I add an administrator while players are online?

Yes. Add the SteamID64 to the active adminlist.txt without restarting. The running server may need time to re-read the file, and the new administrator still has to open the console and run adminauth.

Why does adminauth work once and then stop working?

The command grants rights only to the current connection. Reconnecting, changing sessions, or restarting the client requires another adminauth; the SteamID remains eligible through adminlist.txt.

Can RCON execute teleport or item-spawn commands?

No native guarantee exists for those actions through RCON. RCON exposes a limited server-management set, while character, world, and debug utilities are handled through the authenticated in-game console when the live build provides them.

Where can I find the exact arguments for a command after a patch?

Open the developer console on the updated server, authenticate, and run list. Use its command discovery and autocomplete output instead of relying on a catalog from an older branch.

What is the safest way to remove a mistaken ban?

Run banned immediately before unban <User Index>, because indexes can shift. If you need identity-level certainty, make a backup and manage the relevant ban data directly rather than guessing an old index.

Do I need to restart after editing adminlist.txt?

No. Stunlock’s instructions say the file can be changed without restarting, although a running server may take a short time to re-read it. The account must still run adminauth in its current session.

Why can I connect directly but not see my server in the list?

Check that the configured game and query ports match your launch parameters and are allowed through the firewall and router. Both ports are needed for server-list visibility.

Can I use admin commands in normal chat?

No. Vanilla chat has no native command system, and native console commands do not use a slash prefix. Dot-prefixed chat commands generally come from a separately installed mod.

What is the default Windows settings location?

Unless you set another persistent-data path, use %USERPROFILE%AppDataLocalLowStunlock StudiosVRisingServerSettings. A custom -persistentDataPath moves the active settings directory.

The Bottom Line

For PC v1.1.x, put trusted 17-digit SteamID64s in the active adminlist.txt, enable the console, run adminauth each session, and use list to confirm the live syntax. Use the in-game console for native moderation and world utilities; reserve secured RCON for its smaller remote-management set. Back up saves, verify targets and ports, and recheck commands after every update.