VGKAMI
Advertise Get listed

Game Guides

The Isle Server Admin Commands and How to Use Them

Published 10 min read

To become an administrator on a The Isle server, stop the server, edit its Game.ini, add your SteamID64 beneath [/script/theisle.igamesession] with the ServerAdmins= setting, save the file, and restart. In Legacy, authorized administrators open the command console with Enter; /adminpanel opens the graphical panel, and some current builds also use Insert as a shortcut. Legacy and Evrima do not share an identical administration workflow, so identify your branch before using a command list.

What are The Isle server admin commands, and which version do they apply to?

Server administration is controlled by a SteamID64 allow-list in the server configuration rather than by an ordinary in-game menu. Once an account is authorized, the administrator can use console commands or, where supported, a graphical admin panel.

The command list most commonly documented with explicit syntax is for Legacy. Hosting documentation labels that list Legacy and warns that Evrima works differently. Evrima servers may expose graphical controls through a host-provided panel, but you should not assume that a Legacy slash command works on an Evrima build.

Branch Access method documented What you can safely conclude
Legacy Enter-key console; /adminpanel; Insert shortcut on supported builds The commands in this article’s reference table are the documented Legacy syntax.
Evrima Administration differs; current host documentation describes a graphical panel on supported setups Confirm the controls exposed by your host and build before attempting Legacy commands.

The underlying authorization model comes from a developer configuration example dated April 10, 2019. Practical command syntax and panel behavior can change with game and host updates, so treat the branch label and your server host’s current instructions as part of every command’s requirements.

How do I add myself or another administrator?

Use the following procedure whenever you need to authorize an account. Editing while the server is running is the most common cause of a change being lost when the host rewrites its configuration.

  1. Obtain the administrator’s SteamID64. Use the account’s numeric Steam identifier, not the player’s display name. Check every digit before saving; a single incorrect digit authorizes nobody.
  2. Stop the server completely. Wait for the host control panel or service status to show that the process has stopped. Do not edit a live file that the server can overwrite during shutdown.
  3. Open the server’s Game.ini. A Windows installation commonly uses TheIsleSavedConfigWindowsServerGame.ini. A Linux installation example is /TheIsle/Saved/Config/LinuxServer/Game.ini. Your provider may place the same file under a different root directory.
  4. Find or create the session section. The setting belongs under [/script/theisle.igamesession]. Keep the section header on its own line.
  5. Add the SteamID64 using the syntax accepted by your build and host. The developer example shows repeated +ServerAdmins= entries, while one hosting guide instructs one ServerAdmins= line per administrator. Do not combine several IDs on one line unless your host explicitly documents that format. For example:
    [/script/theisle.igamesession]
    +ServerAdmins=7656119XXXXXXXXXX
    +ServerAdmins=7656119YYYYYYYYYY

    If your provider specifically requires the non-plus form, use its documented form instead:

    [/script/theisle.igamesession]
    ServerAdmins=7656119XXXXXXXXXX
    ServerAdmins=7656119YYYYYYYYYY
  6. Save the file and start the server. Join with the authorized Steam account and test access after the server has finished loading.

The two examples represent syntax differences between documentation and hosting implementations, not two values to paste together. If one format fails, stop the server, check the provider’s current template, and use only that format. An administrator is not granted by typing a command from an unauthorized account.

How do I open the console or admin panel?

Legacy command console

On Legacy, press Enter to open the command console. Type a slash command, press Enter to submit it, and watch the chat or server response for confirmation. Commands must be entered by an account that appears in the server’s admin list.

Graphical admin panel

Type /adminpanel to open the panel when it is available to your authorized account. A current panel guide also documents Insert as a direct shortcut on supported builds. The panel is useful for routine moderation and environment controls, including time, brightness, player moderation, and predefined teleport locations.

If Insert does nothing, use /adminpanel from the Legacy console instead. If neither works, verify authorization and branch before changing key bindings or reinstalling the client; the panel is not guaranteed to exist or behave identically on Evrima.

Which Legacy commands can an administrator use?

The table below collects the documented Legacy syntax. Replace each parameter with the target player’s current name, SteamID64, number of hours, or message as indicated. A command can fail if the target is offline, the name is ambiguous, or the server build uses different permissions.

Command Purpose Example or parameter rules
/announce <message> Send a server-wide announcement /announce Server restart in 10 minutes
/weather <condition> Set the weather Documented conditions are Rain, Sunny, Cloudy, and Stormy.
/time <hour> Set server time Uses a 24-hour clock; for example, /time 1400.
/heal <player> Heal a player and restore hunger and thirst Legacy documentation also notes relief for a broken leg: /heal PlayerName.
/slay <player> Instantly kill a target /slay PlayerName
/goto <player> Teleport yourself to a player /goto PlayerName
/bring <player> Teleport a player to you /bring PlayerName
/grow <player> Advance the target to the next growth stage On Legacy, the player still needs to click Grow after the command: /grow PlayerName.
/kick <name> <reason> Temporarily remove a player by name /kick PlayerName Reason
/kickid <steamid> <reason> Remove a player by SteamID64 /kickid 7656119XXXXXXXXXX Reason
/ban <name> <hours> <reason> Ban by name for a specified number of hours /ban PlayerName 24 Reason
/banid <steamid> <hours> <reason> Ban by SteamID64 for a specified number of hours /banid 7656119XXXXXXXXXX 48 Reason
/unban <steamid> Remove a SteamID-based ban /unban 7656119XXXXXXXXXX

The examples use ordinary names and explanatory reasons only to show placement. Preserve spaces in a reason exactly as your server accepts them, and avoid adding quotation marks unless your build’s command parser specifically requires them.

Should I use a player name or a SteamID64?

Name-based commands are convenient for quick actions, but they are less reliable when two players have similar names, unusual characters, or a name that changes during a session. SteamID-based commands identify the account directly and are the safer choice for moderation.

  • Use /kick or /ban when the displayed name is unmistakable and you need a fast, temporary action.
  • Use /kickid, /banid, and /unban when identity matters, especially for repeat offenders or similarly named players.
  • Record the SteamID64 alongside the reason for a ban so another administrator can reverse the correct action with /unban.
  • For assistance commands such as /heal, /goto, and /bring, confirm the target in chat before acting because these commands affect a living player’s position or condition immediately.

How do I handle common server situations?

Announcing a restart or rule reminder

Use /announce for information every connected player needs. A short message such as /announce Server restart in 10 minutes is easier to notice than several ordinary chat messages. Announce the reason and timing before taking disruptive action.

Removing or banning a disruptive player

For a one-time removal, use the appropriate kick command and include a concise reason. For a time-limited ban, supply the duration in hours. Prefer the SteamID forms when the name could match more than one player. A ban is not permanent by default in the documented syntax: the command requires an hour value.

Restoring a player’s condition

/heal restores health-related needs documented for Legacy, including hunger and thirst; the Legacy guide also describes broken-leg relief. Confirm that you have selected the intended player before applying it, particularly during an event where several players are nearby.

Moving players or investigating a report

/goto moves the administrator to the target, while /bring moves the target to the administrator. These are useful for responding to a report without asking the player to travel, but they can interrupt play. Tell the player what you are doing before moving them whenever circumstances allow.

Advancing growth

/grow advances the target to the next growth stage in Legacy. The player must still select Grow afterward, so the command alone does not complete the transition.

Changing time or weather

Use /time with a four-digit 24-hour value such as 1400. Use /weather with one of the documented conditions: Rain, Sunny, Cloudy, or Stormy. If you are running Evrima, use the controls exposed by your current panel instead of assuming these Legacy commands are supported.

What is different about Evrima administration?

Evrima is a separate administration target in the available host documentation. The Legacy command list should not be presented as universal Evrima syntax. A current graphical-panel guide describes controls for time, brightness, player moderation, and predefined teleport locations, which may be the practical route on an Evrima server when the host supports that panel.

Before publishing or following an Evrima procedure, check three things: the branch selected by the server, the panel or control interface supplied by the host, and the version-specific instructions for that host. If a Legacy command returns no response in Evrima, that is not evidence that your SteamID is wrong; it may simply be an unsupported workflow.

Why does my admin setup or command fail?

The server still treats me as a normal player

  • Confirm that the SteamID64 is correct and belongs to the account you used to join.
  • Check that the entry is under [/script/theisle.igamesession], not in a different section.
  • Make sure the server was stopped before editing and restarted after saving.
  • Verify whether your host expects repeated +ServerAdmins= entries or one ServerAdmins= line per administrator.
  • Check that you joined the same server instance whose Game.ini you edited; hosts sometimes maintain separate configurations for different worlds or branches.

The console does not open

Enter is the documented Legacy console key. If you are on Evrima, or if your client is using a different interface, the Legacy console may not be available. An authorized Legacy administrator can try /adminpanel; on supported builds, Insert may open the panel directly.

A command says the player cannot be found

Recheck spelling and capitalization, then use the SteamID form for moderation if the name is ambiguous. Assistance commands documented with a player name may still require the exact current in-game name.

The player was kicked or banned accidentally

Use the SteamID recorded for the action and issue /unban to remove a SteamID-based ban. A kick is temporary removal, whereas a ban includes the hour duration supplied in the original command. Keep a written moderation log so another administrator can identify the correct account.

The new configuration disappears after a restart

Stop the server before editing, save the file, and then start it. If the host regenerates configuration files, use its configuration editor or documented syntax rather than editing a generated copy. Reopen the file after shutdown to confirm that the admin entry is still present.

What should an administrator check before using a command?

  • Branch: Confirm Legacy or Evrima before relying on syntax.
  • Authorization: Confirm the acting Steam account is listed in Game.ini.
  • Target: Use a SteamID64 for moderation when a name is not unique.
  • Impact: Read the command’s effect before using destructive actions such as /slay, /kick, or /ban.
  • Duration: Supply the intended number of hours for a ban and keep the reason factual.
  • Communication: Announce planned restarts or disruptive maintenance before acting.
  • Recovery: Keep the target SteamID and moderation reason so an incorrect ban can be reversed.

Following this checklist separates routine assistance from irreversible or disruptive moderation and reduces mistakes caused by copying a Legacy command into an Evrima workflow.

Frequently Asked Questions

Can I add more than one administrator to a The Isle server?

Yes. The configuration examples support multiple administrator entries. Add each administrator’s complete SteamID64 on its own line, using the exact plus-sign or non-plus syntax required by your server host.

Do administrators need to be in the server before I add them?

No. Authorization is based on the SteamID64 saved in the server configuration, not on a player being online when the file is edited. The account must reconnect after the server restarts for the permission change to take effect.

Is a Steam profile name the same thing as a SteamID64?

No. A profile or in-game name is a changeable label, while a SteamID64 is the numeric account identifier used by the authorization and ID-based moderation commands. Copy the numeric identifier exactly when granting access or recording a ban.

Why can a host panel show controls that are missing from the console?

The panel and console are separate interfaces, and their available controls depend on the game branch, server build, and hosting implementation. A panel may expose time, brightness, moderation, or predefined teleport locations even when a particular slash command is unavailable.

What should I do before changing the administrator list on a live community server?

Schedule a short maintenance window, announce it to players, stop the server, and make a backup copy of the existing configuration. After restarting, test with the intended account before handing out the SteamID or adding another administrator.