amx_who, status and Finding a Player's SteamID

Before you can ban, kick or add an admin, you need to identify the player precisely — their SteamID for a permanent entry, their userid for an unambiguous moderation target. Two commands give you this: the AMX Mod X amx_who and the engine's own status. They overlap but each shows something the other does not, and knowing which to reach for saves time.

1. amx_who: the admin roster

amx_who is an AMXX command that lists every connected player alongside their admin information — authid (SteamID), current access flags, and whether they have immunity:

amx_who

The output gives you each player's name, their SteamID, the access flags AMXX has resolved for them, and their immunity status. This is the command to run when you are checking "does this person actually have admin, and what can they do?" — it reflects what AMXX granted after reading users.ini, which is not always what you intended. It typically requires the admin (ADMIN_ADMIN) access flag to run.

2. status: the engine's view

status is a built-in engine command (run it from the server console or RCON) and it shows connection details AMXX does not:

status

For each player it prints the userid, name, uniqueid (the SteamID or the non-Steam authid), the IP address and port, and the current ping and packet loss. The header also shows the map, the server's own IP:port and the protocol version. This is the command for "what is this player's userid and IP, and how is their connection?"

3. Reading the SteamID

The uniqueid column is what you copy into a ban or an admin entry. On a Steam client it looks like STEAM_0:1:12345, where the middle digit and the final number together identify the account. On a non-Steam server it depends on your setup: with Reunion or dproto you may see a real-looking SteamID, a VALVE_ id, or a generated one, and duplicate or STEAM_ID_LAN values are a known non-Steam headache — see duplicate SteamIDs. Always copy the id verbatim; a single wrong digit means your ban or admin entry silently never matches, and you will spend an afternoon wondering why a banned player keeps rejoining. For a deeper walkthrough of every method, including reading the id from logs, see finding a player's SteamID.

4. From identity to action

Put the two together in the normal moderation flow:

1. Run status (or amx_who) to get the offender's userid.
2. Act on it unambiguously with the hash form: amx_slay #14, amx_kick #14, amx_ban #14 30 "reason".
3. Copy their uniqueid for a permanent SteamID admin entry or a lasting ban.

Using #userid rather than a name fragment is the habit that stops you from slaying the wrong player when two names look alike — the point hammered home in the slap/slay/kick guide.

5. Do it remotely over RCON

You do not need to be in the game to run these. Over an RCON connection, both commands work from your client console with the rcon prefix:

rcon status
rcon amx_who

This is how you identify and act on a troublemaker from spectator or even from a second machine, without ever joining the server yourself. It is also the only way to read the player list when the server is full and will not let you connect to sort out who is causing the problem. For the full set of remote commands, see the RCON commands list.

Common errors

• amx_who shows no access flags for an admin — AMXX did not match them to a users.ini entry (wrong SteamID, name mismatch, or an auth-method problem). See admin not recognised.
• status shows STEAM_ID_LAN or duplicate ids — a non-Steam validation issue; the client is not presenting a unique id. See duplicate SteamIDs.
• amx_who returns access denied — you lack the admin flag it requires. Run it from the server console/RCON instead, which always has full access.
• Ban or admin entry never matches — you mistyped the uniqueid. Copy it exactly from status, digit for digit.

Verification

Run status and confirm you can read a userid and a uniqueid for every connected player. Cross-check one player against amx_who — the SteamID should match. Then target that player harmlessly with their userid, for example amx_slap #<id> 0, and confirm the correct person is slapped. Once you trust the identity you read, you can safely commit it to a permanent SteamID admin or ban entry.