How to Ban Players From a Soulmask Server (Admin Commands and Unban Steps)

To ban someone from a Soulmask dedicated server, authenticate as an administrator, enable the server permission list, then add the player’s SteamID64. In the console (opened with the tilde key), the commonly documented sequence is gm key YOURPASSWORD, gm EnableServerPermissionList 1 1, and gm AddServerPermissionList 1 <SteamID64>. Community command references report that submitting the add command kicks the player and blocks the account.

Prefer not to run the server on your own PC? Godlike.Host offers hosted Soulmask servers with free DDoS protection and up to three free backups a day.

You must set the administrator password when the server starts with the -adminpsw launch argument. Administrator access is not retained between sessions, so run gm key again each time you reconnect. The commands below are the permission-list syntax reported by multiple server guides; CampFire Studio’s current private-server documentation remains the authority, and conflicting command lists mean you should verify behavior on your server build before relying on it for moderation.

#	Preview	Product	Price
1		THE SOUL GAME	$2.99	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

What you need before banning anyone

• A launch-time administrator password. Start the server with -adminpsw YOURPASSWORD (or the equivalent startup-argument field supplied by your host). If the server was started without this argument, there is no known in-game command for adding one afterward; restart it with the argument.
• Console access. Join the server, open the administrator console with the tilde (~) key, and authenticate there.
• The player’s SteamID64. The permission list uses this numeric account identifier rather than a display name. Names can change, contain unusual characters, or be duplicated.
• The correct permission-list ID. The commands below use list ID 1, which is the value shown in the commonly cited ban instructions. Some server documentation uses other list IDs for other actions, so do not substitute a different number without checking the command reference for your build.

These are operator commands, not chat commands. A slash command such as /ban PlayerName appearing in a recent web page is not established as equivalent to the permission-list commands and should not be treated as a fallback.

Find the player’s SteamID64

Copy the player’s Steam profile URL or otherwise identify the account, then use a SteamID conversion service to obtain the 64-bit numeric identifier. One community guide names steamid.io for this conversion, but that service was not independently verified. Check that the returned number belongs to the account you intend to moderate before entering it.

#1 Best Overall

THE SOUL GAME

$2.99

Buy on Amazon

Why a name is not enough

The permission-list command takes an ID, not a character name. A name-based ban can target the wrong person after a rename or fail when two players use similar names. Record the SteamID64 alongside the date, reason, and any relevant server logs so another administrator can reverse the action accurately.

When you cannot identify the account

Do not guess a number or paste a profile’s short numeric name in place of the SteamID64. Ask the player for a profile link, use the account information available in your host’s logs, or consult CampFire Studio’s current server documentation for an in-game identity command. The community material summarized for these commands does not establish a reliable name-to-ID command.

Authenticate as an administrator

1. Start the server with an administrator password in its launch arguments, for example -adminpsw YOURPASSWORD. Keep the password out of public chat, configuration screenshots, and shared log files.
2. Join the server and press the tilde key to open the console. Keyboard layouts can place this key differently; use the key that opens the console on your installation.
3. Enter gm key YOURPASSWORD and submit it.
4. Run the authentication command again after every new connection. Admin status is reported as session-based rather than permanent, so reconnecting or restarting the game requires a fresh gm key.

If the key command is rejected, first confirm that the server process was launched with -adminpsw and that the password matches exactly. Changing a setting in a panel after the process is already running will not retroactively create an administrator password; restart the server with the argument if it was missing.

Enable the permission list

With the console authenticated, enable list 1:

gm EnableServerPermissionList 1 1

The first 1 identifies the permission list. The final 1 turns that list on; the corresponding off value is 0. The effect of enabling the list is reported to be lost when the server restarts unless you configure persistence at launch.

Check the command response

Look for a success response or other confirmation in the console before adding the player. If the command is not recognized, try the same syntax without the gm prefix, because some community references show both forms. Do not assume a silent console means the list was enabled; test with a known administrative action or consult the current CampFire documentation for the response format on your build.

Ban a player by SteamID64

Enter the player’s numeric SteamID64 in place of the angle-bracketed value:

gm AddServerPermissionList 1 <SteamID64>

For example, the command’s structure is gm AddServerPermissionList 1 7656119XXXXXXXXXX; use the complete number you obtained, not this illustrative pattern. Community guides report that submitting the add command immediately kicks the targeted player and bans the account associated with that SteamID64.

Confirm that the right account was targeted

• Compare the ID you entered with your saved profile record before pressing Enter.
• Watch the console and server log for the kick or permission-list response.
• Ask a moderator who is still connected to confirm that the player was removed, but do not publish the SteamID64 in a public channel.
• Attempting to rejoin with the same Steam account is a practical check, but the command references do not define a separate, universally reliable “is banned” query.

If the player remains connected, wait for the console response and inspect the exact command spelling. Retry without gm only if the prefixed form is rejected. Avoid switching to an unverified name-based or slash command simply because it appears in a different guide.

Unban a player

To remove the SteamID64 from list 1, authenticate again if necessary and run:

gm RemoveServerPermissionList 1 <SteamID64>

Use the same numeric ID that was added. A display-name change does not affect the entry, and removing a different account will not release the intended player.

If removal fails

Some operator references show different permission-list numbers for different actions; one guide lists list ID 4 for unmuting, not for banning. That does not prove that a ban belongs on list 4. If removal from list 1 is rejected, check the current CampFire documentation and your host’s command reference for the list ID used by your server version rather than guessing.

Make bans survive a restart

Enabling the list with gm EnableServerPermissionList 1 1 is reported as a runtime setting. After a server restart, that setting can be lost. Persistent permission-list storage requires the -serverpm launch argument.

The unresolved value problem

Community guides do not agree on the correct value for -serverpm. One guide presents -serverpm=2, but that value has not been confirmed against CampFire Studio’s documentation. Treat it as an unverified example, not a guaranteed setting. Before adding it to a production server, check the current official documentation or your hosting provider’s version-specific instructions.

Test persistence safely

1. Record the current ban and its SteamID64.
2. Configure the documented -serverpm value in the server’s startup arguments, then restart the process.
3. Authenticate with gm key YOURPASSWORD after reconnecting.
4. Check whether the permission list is still enabled and whether the test account remains blocked.
5. If the ban disappears, restore the known working runtime commands and remove the unconfirmed launch value until you have a version-specific answer.

A rented server may expose startup arguments in a control panel rather than a local command line. The principle is the same: the argument must be applied before the server process starts, and the process must be restarted for the change to take effect.

Complete command reference

If your build rejects a command, try the same command without the gm prefix. Syntax shown in 2026 pages for /kick, /ban, kick PlayerName, or ban PlayerName has not been corroborated with the permission-list format and is omitted as a working procedure.

Troubleshooting by symptom

“No admin command works”

• Confirm the process was started with -adminpsw, not merely that a password was typed into a panel after startup.
• Restart the server after adding the launch argument.
• Reconnect and run gm key YOURPASSWORD again; authentication does not carry over between sessions.
• Check capitalization, spaces, and the password’s exact characters.

“The ban command is unknown”

• Verify that the permission list was enabled first.
• Retry the command without the gm prefix, as some guides document that variant.
• Compare your server build’s syntax with CampFire Studio’s current private-server documentation. Do not replace it with an unverified slash command.

“The player was kicked but can return after a restart”

The list may have been enabled only for the current runtime. Configure the documented -serverpm launch argument, restart, and test persistence. Because the value reported by community guides is unresolved, verify it for your exact build before relying on it.

“The player’s character still appears”

An older community guide described a bug in which a banned player’s character remained visible after removal. That report is roughly 700 days old and may no longer apply. First verify the SteamID64, the permission-list response, and the player’s ability to reconnect. If the stale character remains but the account cannot join, treat it as a possible visual or world-state issue and consult current server documentation rather than deleting the character blindly.

“The unban command does not work”

Make sure you are using the original SteamID64 and the list ID that actually contains the ban. Permission-list IDs are not universal across every action in community references. Confirm the current list assignment with the official documentation or your provider before trying another number.

Limits of a SteamID64 ban

A SteamID64 ban targets one Steam account. It does not establish the identity of a person across accounts. Alternate accounts can evade an account-level ban, so a repeat offender may return with a different SteamID64 even when the original entry is functioning correctly.

Use a documented moderation record

• Store the SteamID64, player name at the time, date, moderator, and reason in a private staff log.
• Keep the evidence needed for an appeal or later identification, subject to your community’s privacy rules.
• When an alternate account appears, record the new ID separately; do not overwrite the original entry.
• Tell moderators which list ID and command form your server uses so they do not mix syntax from unrelated guides.

Self-hosted versus rented servers

The commands run in the game server console regardless of where the process is hosted, but the way you set launch arguments differs. On a self-hosted installation, add -adminpsw and any confirmed -serverpm setting to the executable’s startup command. On a rented server, enter them in the provider’s startup-parameter field and restart from the provider panel. If the panel hides or rewrites arguments, ask the host which CampFire-supported syntax applies to its server image.

Do not assume a host’s guide is current merely because it lists a command. Community pages conflict on prefixes, list IDs, and persistence values. Use the exact syntax supported by your installed game build and keep a test ban available before applying a large moderation policy.

Recommended operating procedure

1. Set and protect -adminpsw before opening the server to players.
2. At each moderation session, authenticate with gm key YOURPASSWORD.
3. Confirm list 1 is enabled with gm EnableServerPermissionList 1 1.
4. Verify the target’s SteamID64 independently; never rely on a display name alone.
5. Run gm AddServerPermissionList 1 <SteamID64> and record the result.
6. Configure only a -serverpm value confirmed for your build if bans must persist through restarts.
7. For an approved appeal, remove the same ID with gm RemoveServerPermissionList 1 <SteamID64>.
8. After updates or host migrations, retest authentication, list enabling, banning, unbanning, and restart persistence because command behavior is not established uniformly across all versions.

What is and is not confirmed

The permission-list sequence, the need for a launch-time administrator password, and session-based reauthentication are the consistent points across the available operator guides. The persistence value for -serverpm, slash or name-based alternatives, and the exact behavior of every current game build remain unresolved. CampFire Studio’s official private-server documentation should take precedence whenever it differs from a community command list.

Quick Recap

Bestseller No. 1

THE SOUL GAME

$2.99

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.