This guide covers server administration for Longvinter, including admin setup, in-game commands, player management, PvP zone control, tent/building management, and troubleshooting common server issues.
Admin Setup
To use admin commands on your Longvinter server, you must first register your Steam64 ID in the server configuration.
Finding Your Steam64 ID
- Visit steamid.io.
- Enter your Steam profile URL or username.
- Copy the steamID64 value (a long number like
76561198012345678).
Adding Admin Privileges
- Stop your server from GPanel.
- Open the File Manager and navigate to
longvinter-linux-server/Longvinter/Saved/Config/LinuxServer/Game.ini. - Find the
AdminSteamIDline under the[/Game/BluePrint/GameMode/BP_GameMode.BP_GameMode_C]section. - Set it to your Steam64 ID:
AdminSteamID=76561198012345678
To add multiple admins, separate their Steam64 IDs with commas:
AdminSteamID=76561198012345678,76561198087654321,76561198011111111
- Save the file and start your server.
AdminSteamID require a server restart to take effect. You cannot add admins while the server is running.
Admin Commands
Once you are set as an admin and connected to the server, you can use the following commands. Open the in-game chat with Enter or T and type the command.
| Command | Syntax | Description |
|---|---|---|
| Kick | /kick [PlayerName] |
Removes a player from the server. They can rejoin immediately unless banned. |
| Ban | /ban [PlayerName] |
Permanently bans a player from the server. They will not be able to reconnect. |
| Unban | /unban [PlayerName] |
Removes a ban from a player, allowing them to rejoin the server. |
| Teleport | /teleport [PlayerName] |
Teleports you to the specified player's current location. |
| Announce | /announce [Message] |
Broadcasts a server-wide announcement message visible to all connected players. |
| Save | /save |
Forces an immediate server save. Useful before maintenance or restarts. |
| Shutdown | /shutdown [Seconds] |
Initiates a server shutdown with an optional countdown in seconds. Players will be warned. |
Command Usage Examples
/kick PlayerName
/ban TroubleMaker99
/unban TroubleMaker99
/teleport FriendlyPlayer
/announce Server will restart in 5 minutes!
/save
/shutdown 300
/save before running /shutdown to ensure all progress is saved before the server goes down.
PvP Zone Management
Longvinter allows you to control player-versus-player combat on your server through the Game.ini configuration.
Global PvP Toggle
The simplest approach is to enable or disable PvP globally for the entire server:
# Enable PvP (players can fight anywhere)
PVP=true
# Disable PvP (no player combat allowed)
PVP=false
PvP Server Considerations
- PvP Enabled (
true): Players can attack and loot each other anywhere on the map. This creates a more competitive and survival-focused experience. Players drop their inventory on death. - PvP Disabled (
false): Players cannot damage each other. This is ideal for cooperative, relaxed, or roleplay-focused servers where the emphasis is on fishing, trading, and building. - Community Rules: Some server operators run PvP-enabled servers with community-enforced safe zones (e.g., towns or markets are no-PvP by honor system). Use
/announceto remind players of your rules.
Tent and Building Management
Tents are the primary building/base structures in Longvinter. Proper management keeps your server clean and performant.
TentDecay Settings
| Setting | Value | Effect |
|---|---|---|
TentDecay=true |
Enabled | Tents from inactive players will automatically decay and be removed after a period of inactivity. This frees up building space and improves server performance. |
TentDecay=false |
Disabled | Tents persist indefinitely regardless of player activity. Use this for smaller private servers where you want permanent bases. |
MaxTents Configuration
The MaxTents setting controls how many tents each player can place:
# Allow 2 tents per player (default)
MaxTents=2
# Allow more tents for building-focused servers
MaxTents=5
# Limit to 1 tent for competitive/survival servers
MaxTents=1
MaxTents values with many players can impact server performance. For servers with 20+ players, consider keeping MaxTents at 2-3 and enabling TentDecay.
Player Management
Effective player management keeps your community healthy. Here are best practices:
Handling Disruptive Players
- Warn first: Use
/announceto remind players of server rules. - Kick for minor offenses: Use
/kick [PlayerName]for first-time or minor rule violations. - Ban for repeat or severe offenses: Use
/ban [PlayerName]for griefing, harassment, or repeated violations.
Managing the Ban List
Bans are stored server-side. To review or modify bans:
- Use
/unban [PlayerName]in-game to remove a specific ban. - For bulk ban management, check the ban list file in the server's
Saveddirectory via the File Manager or SFTP.
Monitoring Player Activity
- Watch the Console tab in GPanel for player join/leave messages.
- Use
/teleportto check on players if you suspect rule violations. - Regularly review the server console for any error messages or unusual activity.
Troubleshooting
Connection Issues
| Problem | Solution |
|---|---|
| Server not appearing in browser | Ensure the server is running in GPanel. Check that ServerRegion is set correctly in Game.ini. The server may take a few minutes to appear after starting. |
| Players cannot connect via direct IP | Verify the IP and port are correct from GPanel. Ensure the server status shows as Running. Have players verify they are using the game port, not the query port. |
| "Server Full" message | Increase MaxPlayers in Game.ini if your plan supports more slots, then restart the server. |
| Password not working | Double-check the Password value in Game.ini. Passwords are case-sensitive. Restart after changes. |
Server Crashes
| Problem | Solution |
|---|---|
| Server crashes on startup | Check the console output for error messages. Verify your Game.ini has no syntax errors. Try reinstalling the server files from GPanel. |
| Server crashes during gameplay | This may indicate a corrupted save. Restore from a recent backup or reset the world. Check if the crash correlates with high player counts and consider lowering MaxPlayers or MaxTents. |
| Recurring crashes after update | Game updates may introduce temporary bugs. Check the Longvinter community channels for known issues. If the crash persists, open a support ticket. |
Tent Decay Problems
| Problem | Solution |
|---|---|
| Tents disappearing too quickly | If TentDecay=true, inactive tents will be removed automatically. Consider setting TentDecay=false if your players want permanent bases. |
| Too many tents cluttering the server | Enable TentDecay=true and lower MaxTents to reduce clutter. Announce changes to players before applying them. |
Version Mismatches
| Problem | Solution |
|---|---|
| Players see "Version Mismatch" error | Your server needs to be updated to match the latest game version. Restart the server from GPanel to trigger an automatic update, or reinstall via the GPanel settings. Players must also update their game client through Steam. |
Related Articles
- Longvinter Server Setup Guide
- How to Find Your Server IP and Port
- How to Upload Files via SFTP
- Getting Started with Your New Server