This guide covers all admin commands, mod support, and server management tools available for your Avorion dedicated server on Legion Hosting. Learn how to manage players, control the galaxy, install mods, and troubleshoot common issues. For initial server setup and configuration, see our Avorion Server Setup Guide.
Admin Setup
Avorion uses an XML-based admin system that grants specific players elevated permissions. Admins are defined in the admin.xml file or can be added through in-game commands.
Adding Admins via admin.xml
The admin.xml file is located in your galaxy's save folder (e.g., galaxies/your_galaxy_name/admin.xml). You can edit this file through GPanel's File Manager.
<?xml version="1.0" encoding="UTF-8"?>
<admin>
<admin id="76561198012345678" />
<admin id="76561198087654321" />
</admin>Each <admin> entry contains a player's Steam ID (SteamID64 format). To find a player's Steam ID:
- Go to the player's Steam profile
- If their profile URL uses a custom name, use a SteamID lookup tool to find their SteamID64
- The SteamID64 is a 17-digit number starting with
7656119
Adding Admins In-Game
If you are already an admin, you can add other admins using the in-game chat command:
/admin <playerName>This adds the specified player to the admin list immediately without requiring a server restart.
First Admin: For the initial admin setup, you must edit
admin.xml directly through GPanel's File Manager since no admins exist yet to run the in-game command. After adding your Steam ID and restarting the server, you can use in-game commands to add additional admins.
Common Admin Commands
Admin commands are entered in the in-game chat (press Enter to open chat) with a / prefix. These can also be executed from the GPanel server console.
Player Management
| Command | Description |
|---|---|
/kick <name> |
Kick a player from the server. They can reconnect immediately. |
/ban <name> |
Ban a player from the server. Their Steam ID is added to banlist.txt. |
/unban <steamid> |
Remove a ban for a player by their Steam ID. |
/admin <name> |
Grant admin permissions to a player. |
/removeadmin <name> |
Remove admin permissions from a player. |
/say <message> |
Broadcast a server-wide message to all players. |
/players |
List all connected players with their Steam IDs and current sector. |
/whisper <name> <message> |
Send a private message to a specific player. |
Server Control
| Command | Description |
|---|---|
/save |
Manually save all loaded sectors and player data to disk. |
/stop |
Safely save all data and shut down the server. |
/seed |
Display the current galaxy seed. |
/status |
Show server status including player count, loaded sectors, and performance metrics. |
/difficulty <value> |
Change the server difficulty level (-3 to 3). Takes effect for newly generated sectors. |
/pvp <on|off> |
Toggle player vs. player combat on or off. |
/maxplayers <number> |
Change the maximum player count while the server is running. |
/password <password> |
Set or change the server password. Leave empty to remove the password. |
Teleportation and Navigation
| Command | Description |
|---|---|
/tp <x> <y> |
Teleport yourself to sector coordinates (x, y). |
/tp <playerName> |
Teleport yourself to another player's location. |
/tp <playerName> <x> <y> |
Teleport a specific player to sector coordinates. |
/give <playerName> <amount> <material> |
Give a player resources. Materials: Iron, Titanium, Naonite, Trinium, Xanion, Ogonite, Avorion. |
Galaxy Management
As an admin, you have tools to manage the galaxy structure and sectors.
Sector Management
| Command | Description |
|---|---|
/sector |
Display information about your current sector (coordinates, entities, factions). |
/regeneratesector <x> <y> |
Regenerate a sector, resetting it to its procedurally generated state. Warning: Destroys all player-built structures in that sector. |
/clearsector <x> <y> |
Remove all entities from a sector, leaving it empty. |
Warning: Sector regeneration and clearing are destructive operations. Any player ships, stations, or structures in the affected sector will be permanently deleted. Always warn players and back up before using these commands.
Material Tiers
Avorion's galaxy is organized in rings of increasing material tiers, radiating inward toward the barrier at the core. Understanding this helps when teleporting players or managing sector content.
| Material | Tier | Galaxy Ring | Color |
|---|---|---|---|
| Iron | 0 | Outermost ring | Grey |
| Titanium | 1 | Second ring | White |
| Naonite | 2 | Third ring | Green |
| Trinium | 3 | Fourth ring | Blue |
| Xanion | 4 | Fifth ring | Yellow |
| Ogonite | 5 | Sixth ring | Orange |
| Avorion | 6 | Core (past the barrier) | Gold |
Mod and Workshop Support
Avorion has robust Steam Workshop support, allowing you to extend your server with community-created mods.
Installing Mods
- Find the mod you want on the Steam Workshop for Avorion
- Note the Workshop ID from the mod's URL (the number at the end)
- Stop the server in GPanel
- Open GPanel's File Manager
- Navigate to the
galaxies/your_galaxy_name/directory - Edit the
modconfig.luafile (create it if it does not exist) - Add the mod's Workshop ID to the configuration
- Start the server — the mod will be downloaded automatically
modconfig.lua Format
-- Avorion Mod Configuration
modLocation = ""
forceEnabling = false
mods =
{
{workshopid = "1234567890"},
{workshopid = "0987654321"},
{workshopid = "1122334455"},
}
Important: All players connecting to a modded server must have the same mods installed. Steam Workshop mods are typically downloaded automatically when a player connects, but some mods may require manual installation on the client side.
Mod Management Tips
- Add mods one at a time and test after each addition to identify compatibility issues
- Some mods require a galaxy reset to take full effect (especially those that modify sector generation)
- Check mod comments and descriptions for known incompatibilities before installing
- Keep a backup of your
modconfig.luaand galaxy folder before adding or removing mods - Server-side-only mods do not require clients to install them, but most gameplay mods need both sides
Troubleshooting
Server Not Appearing in Browser
- Verify
listed=truein yourserver.inior startup variables - Check that the Steam query port (
steamQueryPort) is accessible — this is typically your game port + 1 - Wait 2-3 minutes after server startup for the Steam listing to propagate
- Try connecting via Direct Connect to confirm the server is running
- Ensure the server has fully started by checking for
Server startup completein the console
Server Crashes
If your Avorion server is crashing, follow these steps:
- Check crash logs — Look in the GPanel console and the
logs/folder within your galaxy directory for error messages - Remove recently added mods — If crashes started after adding a mod, remove it from
modconfig.luaand restart - Check sector corruption — If the crash occurs when loading a specific sector, that sector may be corrupted. Use
/regeneratesectorfrom the console (if accessible) or delete the sector file from thesectors/folder - Update the server — Ensure your server is running the latest version through GPanel
- Reduce worker threads — If the server is running out of resources, try reducing
workerThreadsandgeneratorThreadsinserver.ini - Restore from backup — If all else fails, restore the galaxy folder from a backup taken before the issues began
Performance Issues
- High tick time — Use
/statusto check server performance. High tick times indicate the server is struggling to keep up with simulation demands. - Too many loaded sectors — Each sector with players or active AI consumes resources. Encourage players to avoid spreading too far across the galaxy simultaneously.
- Large ships — Ships with excessive block counts increase simulation load. Consider setting guidelines for maximum ship sizes.
- Station spam — Many player-built stations in a single sector can degrade performance. Monitor sector entity counts with
/sector.
Player Connection Problems
- Version mismatch — All players must be on the same game version as the server. Ensure everyone has updated through Steam.
- Mod mismatch — Players need the same mods installed. If a player cannot connect, verify their mod list matches the server's
modconfig.lua. - Timeout errors — Can indicate server overload or network issues. Check server performance with
/status. - Password issues — If players report the password is not working, verify the password in your startup variables and
server.inimatch.
Quick Reference
The most commonly used admin commands for daily server management:
# Check server health
/status
# See who is online
/players
# Save all data
/save
# Broadcast a message
/say Server restarting in 5 minutes!
# Kick a player
/kick PlayerName
# Ban a player
/ban PlayerName
# Teleport to a player
/tp PlayerName
# Give resources to a player
/give PlayerName 10000 Trinium
# View current sector info
/sector
# Check galaxy seed
/seed
# Safely shut down
/stopRelated Articles
- Avorion Server Setup Guide
- How to Find Your Server IP and Port
- How to Upload Files via SFTP
- Getting Started with Your New Server
Need Help?
If you need further assistance with Avorion server administration or have questions about specific commands, our support team is ready to help. Submit a support ticket and we will respond as soon as possible.
