Giving admin or OP on every game we host

You bought a server. You joined. The game doesn't recognize you as the owner. This article tells you the exact command, per game, to give yourself or someone else admin powers.

Most of these run in the panel's Console tab. A few need editing a file via the Files tab. None of them require SFTP for this specific task.

A word before you op anyone

"OP" or "admin" in most of these games means full control: spawn items, kick players, change the world, edit configs from in-game. It is god mode. Only give it to accounts you trust completely. For "trusted enough to manage building" but not "trusted with the bank", use the game's permission system (LuckPerms on Minecraft, role tables in others) instead of full op.

For Minecraft specifically, there's a longer article on this: Plugin permissions without LuckPerms pain.

Quick reference

Game	Where you set it	What you do
Minecraft Java	Console	op YourUsername
Minecraft Bedrock	Console	op YourGamertag
Valheim	adminlist.txt (Files tab)	Add your SteamID64, one per line
Vintage Story	serverconfig.json	Set your player's Role to admin, or run /op <player> admin in chat
Rust	Console	ownerid <SteamID64> "<name>" "<reason>", then server.writecfg
Eco	First player to join, then web admin	First-join auto-admin; manage subsequent users in the web UI
ARK / ASA	In-game console	enablecheats <ServerAdminPassword> per session
Project Zomboid	Console	adduser <name> <pw> then grantadmin <name>
Palworld	PalWorldSettings.ini + in-game	Set AdminPassword=, then /adminpassword <pw> in chat
V Rising	adminlist.txt	Add your SteamID64
7 Days to Die	serveradmin.xml	Add <admin steamID="..." permission_level="0" />
Terraria (TShock)	tshock/config.json	Or /auth-verify <pw> first-time
Satisfactory	In-game pause menu	Server Management → set admin
Factorio	Console	/promote <username>

Detail per game follows.

---

Minecraft (Java Edition: Paper, Purpur, Spigot, Vanilla)

Make yourself or someone op:

op YourMinecraftUsername

Remove op from someone:

deop UsernameToRemove

Op level matters. Set the maximum op level in server.properties (op-permission-level=4, which is the default). Level 4 = unrestricted. Level 1-3 = increasingly limited.

The list of ops lives in ops.json. You can edit it directly via the Files tab if the console isn't accessible, but the op command is usually faster.

Minecraft (Forge / Fabric)

Same as Paper/Purpur — op <username>. The Forge/Fabric server runs the vanilla op system unless a mod overrides it.

Minecraft (Bedrock Edition)

op YourGamertag

Make sure you're using the gamertag exactly as it appears in-game, including punctuation.

Valheim (dedicated server)

Valheim doesn't have an in-game "op" concept. Admins are listed in a file:

1. Stop the server (panel → power → Stop).
2. Files tab → find adminlist.txt.
3. Open it and add one Steam ID per line. Steam ID is the long-number form (not your display name). Find your Steam ID at steamid.io.
4. Save the file.
5. Start the server.

Once admin, you can use these in chat (open with Enter):

• /help — list admin commands
• /ban <name> — kick + permaban
• /kick <name> — kick only
• /save — force-save the world

Note: server-level Valheim mods (BepInEx) may provide more admin commands. See BepInEx and Valheim mods.

Vintage Story

1. Stop the server.
2. Files tab → serverconfig.json.
3. Find the "PlayerData" section. Each player has a Role field. Set it to admin:

   "Role": "admin"
   

4. Save, start the server.

You can also create custom roles in playerroles.json for finer-grained permission (build, claim, kick, etc.) without giving full admin.

In-game, admin commands include:

• /help — list everything
• /tp <player> — teleport to a player
• /op <player> admin — promote a player to admin while the server is running

Rust (dedicated server)

1. In console: ownerid <SteamID64> "<player-name>" "<reason>". Adds them as owner (highest permission).
2. Or: moderatorid <SteamID64> "<player-name>" "<reason>" for moderator level.
3. To make changes stick across restarts: server.writecfg.

Eco

In-game, the first person to connect to a fresh server becomes admin automatically. After that:

1. Open the panel's web admin UI (Eco's built-in web interface — port shown in your panel).
2. Login with the admin password from your server.properties for Eco.
3. Manage user roles from there.

Or edit Users.eco directly via Files tab if you locked yourself out.

ARK / ARK: Survival Ascended

Console (in-game, press Tab to open the console):

enablecheats <ServerAdminPassword>

The ServerAdminPassword is set in your GameUserSettings.ini. Find or set it in the Files tab.

Once cheats are enabled in your session you have admin power. This is per-session — you have to re-run it each time you reconnect.

Project Zomboid

Admin status persists. To promote:

1. Stop the server.
2. Files tab → Users.db (sqlite). Easier: use the console while the server is running:

   adduser <username> <password>
   grantadmin <username>
   

3. Or edit servername.ini and add the username to the AdminUsername line.

Palworld (dedicated server)

1. Files tab → PalWorldSettings.ini.
2. Set AdminPassword= to a strong password.
3. Restart the server.
4. In game console (open with the right key, varies): /adminpassword <yourpassword>.
5. You're now admin. Commands: /banplayer, /kickplayer, /showplayers, etc.

V Rising (dedicated server)

1. Stop the server.
2. Files tab → find adminlist.txt.
3. Add one Steam ID per line.
4. Save, start.

7 Days to Die

Permissions are in serveradmin.xml. Open it via Files tab, find <admins>, add an entry:

<admin steamID="76561198000000000" permission_level="0" />

permission_level=0 is the highest. Save, restart.

Terraria / tModLoader

Terraria's permissions work via a config file:

1. Files tab → tshock/config.json (if you're running TShock).
2. Pure vanilla Terraria: console command /auth-verify <password> to claim ownership the first time, then /auth <password> on subsequent logins.

Look up TShock's permission system for advanced setups; it's powerful but documented elsewhere.

Satisfactory

Open the in-game pause menu when connected → Server Management → set yourself or others as administrator. No console commands needed.

Factorio

/promote <username>

makes them an admin. /demote <username> reverses it. The console accepts these from any current admin, and the first person to log in gets default admin privileges (configurable).

---

When the console doesn't work

If the console tab isn't responding (red dot, "Wings unreachable", etc.):

• Wait 30 seconds. Wings sometimes pauses briefly during a startup phase.
• Check the server is actually running. Panel main page should show "running" status.
• If still stuck, edit the relevant file via the Files tab instead. Every "op" command above has a corresponding file you can edit when the server is stopped.

A general principle

If a game has a "first connection becomes owner" model: be the first to connect, then add others.

If it has a Steam-ID-based admin list: find Steam IDs at steamid.io.

If it has a config-file approach: stop the server before editing, restart after.

When in doubt: open a ticket in our Discord, tell us the game and the username/Steam ID, we'll point you at the right file. We see this question a few times a week and it's always 30 seconds to resolve once we know the game.