This guide covers admin setup, available commands, player management, and troubleshooting for your No One Survived dedicated server. Learn how to configure admin access, use in-game commands, and resolve common server issues.
Admin Setup
No One Survived provides admin access through an admin password and optionally through a Steam ID whitelist. Admin capabilities give you full control over the server while playing.
Setting the Admin Password
The admin password is configured via the SERVER_ADMIN_PASSWORD GPanel startup variable, or in the config file WRSH/Saved/Config/WindowsServer/Game.ini:
[ServerSetting]
AdminPassword=YourSecurePassword123
You can also set this via GPanel's Startup tab by editing the SERVER_ADMIN_PASSWORD variable. After changing the password, restart the server for it to take effect.
Logging in as Admin In-Game
- Join your server as a normal player.
- Open the in-game console (typically by pressing ` or ~, or check the game's key bindings).
- Type the admin login command with your password:
AdminLogin YourSecurePassword123
You should see a confirmation message that you have been granted admin privileges for the current session.
Steam ID Whitelist
For an additional layer of security, you can restrict admin access to specific Steam accounts by configuring a Steam ID whitelist in the server settings:
[AdminSettings]
AdminSteamIDs=76561198012345678,76561198087654321,76561198011223344
When a Steam ID whitelist is configured, only players whose Steam IDs are listed can authenticate as admin, even if they know the admin password. This prevents unauthorized access if the password is leaked.
Admin Commands
Once authenticated as admin, you can use the following commands via the in-game console:
Player Management Commands
| Command | Syntax | Description |
|---|---|---|
| Kick | Kick <PlayerName> |
Removes a player from the server. They can rejoin immediately. |
| Ban | Ban <PlayerName> |
Removes a player and prevents them from rejoining until unbanned. |
| Unban | Unban <PlayerName> |
Removes a player from the ban list, allowing them to rejoin. |
| Player List | ListPlayers |
Shows all currently connected players with their names and Steam IDs. |
| Broadcast | Broadcast <Message> |
Sends a server-wide message visible to all players. |
Teleportation Commands
| Command | Syntax | Description |
|---|---|---|
| Teleport to Player | TeleportTo <PlayerName> |
Teleports you to the specified player's location. |
| Teleport Player to You | TeleportHere <PlayerName> |
Teleports the specified player to your current location. |
| Teleport to Coordinates | Teleport <X> <Y> <Z> |
Teleports you to the specified world coordinates. |
Item and Spawn Commands
| Command | Syntax | Description |
|---|---|---|
| Give Item | GiveItem <ItemID> <Amount> |
Spawns the specified item in your inventory. |
| Give Item to Player | GiveItemTo <PlayerName> <ItemID> <Amount> |
Spawns an item directly in another player's inventory. |
| Spawn Entity | SpawnEntity <EntityID> |
Spawns an entity (zombie, NPC, animal) at your location. |
Time and Weather Commands
| Command | Syntax | Description |
|---|---|---|
| Set Time | SetTime <Hour> |
Sets the in-game time (0-24). For example, SetTime 12 sets it to noon. |
| Set Weather | SetWeather <Type> |
Changes the current weather. Options: Clear, Rain, Storm, Fog. |
| Toggle Day/Night Cycle | ToggleDayNight |
Pauses or resumes the day/night cycle at the current time. |
RCON Access
If the game supports RCON (Remote Console), you can send admin commands without being logged into the game. This is useful for automated server management and external tools.
Enabling RCON
[RCONSettings]
RCONEnabled=true
RCONPort=27020
RCONPassword=YourRCONPassword
Once RCON is enabled, you can use any standard RCON client to connect to the server and execute commands remotely. The RCON port must be different from the game and query ports.
Player Management
Managing the Ban List
Bans are stored in a ban list file on the server. You can manage bans through admin commands or by directly editing the ban list file:
- Use
Ban <PlayerName>to add a player to the ban list. - Use
Unban <PlayerName>to remove a player from the ban list. - The ban list file can be edited via GPanel's File Manager for bulk changes.
Whitelist Mode
If you want to restrict your server to specific players only, you can enable whitelist mode:
[ServerSettings]
WhitelistEnabled=true
When whitelisting is enabled, only players whose Steam IDs are in the whitelist file can connect. Add Steam IDs to the whitelist file (one per line) via GPanel's File Manager.
World Management
Day/Night Cycle Tuning
The day/night cycle significantly affects gameplay. Longer days give players more safe time for resource gathering, while longer nights increase the survival challenge:
| Play Style | Day Length | Night Length |
|---|---|---|
| Casual / Building-focused | 60 minutes | 15 minutes |
| Balanced (default) | 40 minutes | 20 minutes |
| Hardcore Survival | 20 minutes | 40 minutes |
| Permanent Day | 120 minutes | 1 minute |
Difficulty Tuning
Beyond the preset difficulty levels, you can fine-tune individual settings to create a custom difficulty. Combine these for a tailored experience:
- Zombie density: Adjust
ZombieSpawnMultiplier(0.1 for almost none, 5.0 for overwhelming hordes). - NPC behavior: Set
NPCHostilitytoPassivefor friendly NPCs orAggressivefor a hostile world. - Resource scarcity: Lower
GatherRateMultiplierandLootRespawnMultiplierfor harder survival. - Combat difficulty: Combine high zombie spawns with low durability for a challenging combat experience.
Troubleshooting
Server Crashes
- Check the console log: Review the GPanel console output for error messages before the crash. Common causes include memory limits and corrupted save data.
- Memory issues: If the server crashes during world generation or with many players, it may need more RAM. Consider upgrading your server plan.
- Corrupted world save: If the server crashes on startup repeatedly, try restoring a backup or performing a world reset. See No One Survived Server Setup Guide for backup and reset instructions.
- Game updates: Crashes after a game update may indicate compatibility issues. Restart the server to apply the update, and check community forums for known issues.
Connection Issues
- Server not appearing in browser: Ensure the server has fully started (check GPanel console for a ready message). Verify that the query port is correctly assigned.
- Cannot connect via Direct IP: Double-check the IP and game port (not the query port). See How to Find Your Server IP and Port.
- Timeout on connect: The server may be overloaded or unresponsive. Try restarting via GPanel. If the issue persists, check the console for errors.
- "Version mismatch": Both the server and client must be on the same game version. Restart the server to apply pending updates.
Save Corruption
- Symptoms: Server fails to start, loads into an empty world, or players lose all progress.
- Prevention: Always stop the server cleanly through GPanel before maintenance. Avoid force-killing the server process.
- Recovery: Restore from a backup taken before the corruption occurred. If no backup exists, a world reset is necessary.
Zombie Spawn Issues
- No zombies spawning: Check that
ZombieSpawnMultiplieris not set to0. Verify the difficulty is not set to a mode that disables zombies. - Too many zombies / lag: Reduce
ZombieSpawnMultiplier. High spawn rates combined with many players can cause significant server lag. - Zombies not despawning: This may be a game bug. Restarting the server clears all spawned entities and resolves the issue temporarily.
Performance Optimization
- Reduce
MaxPlayersif the server struggles with the current player count. - Lower
ZombieSpawnMultiplierto reduce entity count and CPU usage. - Ensure the server has enough RAM for the map size and player count.
- Schedule periodic restarts (daily or every few days) to clear memory leaks and reset entity counts.
- If available, reduce the view distance or simulation range in server settings.
Related Articles
- No One Survived Server Setup Guide
- How to Find Your Server IP and Port
- How to Upload Files via SFTP
- Getting Started with Your New Server