How to Ban and Kick Players on Arma Reforger

To kick or ban a player on Arma Reforger, identify the player with #players, then run #kick or #ban create with their in-session player ID or identity ID. Permanent bans use a duration of 0 seconds; temporary bans use a number of seconds. Live #ban create and #ban remove commands run through BattlEye RCon (the RCON Console in the panel) and are separate from the game.playerBanList block in config.json, which you pre-seed by hand. This guide covers the chat commands, the panel RCON Console method, and how to manage bans cleanly.

Before You Kick or Ban: Admin Rights and RCon

Arma Reforger has no in-game chat login. Admin rights come from adding your Bohemia identity ID to the game.admins array in config.json (managed on its own page in the panel), and moderation commands are run through BattlEye RCon — the RCON Console in the panel — authenticated by the server’s RCon password rather than an in-chat login.

Tip: The RCON Console appears on Arma Reforger servers and needs the WCS_Commands mod installed for #kick and #ban to function

Tip: The RCon password is held server-side and is never exposed to your browser

Listing Players to Get the Right Target

Most kicks and bans go wrong because the admin guessed the slot or pasted the wrong ID. Always run #players first so the slot numbers and identity IDs are right in front of you in chat.

1. Open chat
2. Run #players
3. Find the row for the player you want to remove
4. Note both their slot number and their full identity ID

Tip: Slot numbers shift as players join and leave; if the list is busy, use the identity ID to be safe

Kicking a Player

A kick removes the player from the current session but does not stop them from rejoining. Use it for one-off issues like AFK players, accidental team kills, or someone who needs a cooldown.

Tip: #kick takes no reason argument; any trailing text is ignored, and reasons are only supported on #ban

Tip: If the player reconnects and the same problem continues, escalate to #ban

Note: A kick does not write to playerBanList, so the player is free to rejoin immediately

Banning a Player

A ban removes the player and prevents them from rejoining for the duration you set. Use 0 seconds for a permanent ban or any positive number of seconds for a temporary one. The create subcommand is required.

Tip: Durations are in seconds: 3600 for one hour, 86400 (24 hours) for a serious incident

Tip: Reserve permanent bans for cheating, doxxing, or repeat offenders

Warning: Double-check the player identity ID before a permanent ban; reversing one means a manual config edit

Banning from the Panel RCON Console

If a player has already left or you are not in the game, you can moderate from the RCON Console in LoafHub. This is a dedicated sidebar item (separate from the basic Console) that appears on Arma Reforger servers and needs the WCS_Commands mod installed. It gives you a live Players roster with structured Kick, Ban, and Unban controls rather than typing raw commands.

1. Open hub.loafhosts.com and select your Arma Reforger server
2. Open the RCON Console from the sidebar
3. Use the Players roster to confirm the target’s player ID or identity ID
4. Use the Ban control with the identity ID, duration in seconds, and reason
5. Confirm the ban appears in the console output

Tip: The console keeps the full ban output line, which is useful for your moderation log

Where the Ban List Lives

Arma Reforger stores bans inside config.json in the playerBanList array under the game block. Each entry is an object with the player’s identityId, a name for your reference, and a reason. There is no separate ban file to manage.

Tip: You can pre-populate playerBanList by hand for players you already know to block

Tip: Use the name field for your own records; the server matches on identityId

Unbanning a Player

To unban someone, run #ban remove with their identity ID through the RCON Console, or remove their entry from the playerBanList block in config.json and restart the server. There is no #unban command in Arma Reforger; unban is the remove subcommand of #ban.

1. Open the File Manager and locate config.json
2. Find the playerBanList array under the game block
3. Delete the object for the player you are unbanning
4. Save config.json and restart the server
5. Alternatively, run #ban remove with the player’s identity ID from the RCON Console

Tip: Take a backup before bulk-editing playerBanList; LPV5 has scheduled backups for exactly this kind of change

Frequently Asked Questions

What is the kick command in Arma Reforger?

From the in-game chat, type #kick followed by the player’s in-session player ID: #kick 5. #kick takes no reason argument, and any trailing text is ignored. Admin rights come from being in the game.admins array in config.json (there is no in-chat #login). The player is disconnected but can rejoin immediately.

What is the ban command in Arma Reforger?

Use #ban create with the player’s in-session player ID, a duration in seconds, and an optional reason: #ban create 5 3600 spam (a one-hour ban). The create subcommand is required, and a duration of 0 seconds makes the ban permanent. Live #ban create bans run through BattlEye RCon at runtime and are separate from the game.playerBanList block in config.json, which you pre-seed by hand.

Where is the Arma Reforger ban list stored?

Bans live in the playerBanList array under the game block of config.json. Each entry is an object with identityId, name, and reason. There is no separate ban file, so editing config.json is the manual way to add or remove a ban.

How do I unban a player on Arma Reforger?

Either run #ban remove followed by the player’s identity ID from the RCON Console, or open config.json, remove their entry from playerBanList, save, and restart the server.

Can I issue a temporary ban?

Yes. The seconds argument in #ban create controls duration. Use any positive number for a temporary ban (3600 for an hour, 86400 for a day) and 0 for a permanent one.

Can I ban a player who is offline?

Yes. If you already have their Bohemia identity ID, you can add them to the playerBanList array in config.json directly, or run #ban create [reason] from the RCON Console (use the identity ID, since the in-session player ID only exists while they are online). They will be blocked the next time they try to connect.

Are kick and ban reasons visible to the player?

Reasons are passed through to the disconnect message and into the server log. Keep them brief and accurate; they are part of your moderation record and what the affected player sees on the way out.