---
title: "Fix: 'You have no access to that command' on amx_ban"
excerpt: "Why an admin command is refused, how AMXX flags map to commands, the users.ini SteamID and password auth traps, and reloading admins so your access takes effect."
category: "errors"
tags: "admin, access"
image: ""
read_time: "8 min read"
---
<p>You type an admin command and AMX Mod X refuses it:</p><pre>You have no access to that command</pre><p>This means AMXX either does not recognize you as an admin at all, or it recognizes you but your access flags do not include the one that specific command requires. Every admin command is gated by a flag; being "an admin" is not enough — you need the right flag for that command. The fix is to get your admin entry recognized and give it the flags the command demands.</p><h2>1. Check whether AMXX sees you as an admin</h2><p>From in-game, list the recognized admins:</p><pre>amx_who</pre><p>This shows every connected player and their access flags. If your name shows no flags (or you are not listed as admin), AMXX did not match you to an admin entry — an authentication problem (step 3). If you <em>are</em> listed but missing a flag, it is a permissions problem (step 2). Read <code>amx_who</code> before assuming which one you have.</p><h2>2. Map the command to its flag</h2><p>AMXX commands require specific access flags, defined by letter. The relevant ones for moderation:</p><ul><li><strong><code>b</code></strong> — reservation / slot access.</li><li><strong><code>c</code></strong> — kick access (<code>amx_kick</code>).</li><li><strong><code>d</code></strong> — ban access (<code>amx_ban</code>, <code>amx_banip</code>).</li><li><strong><code>e</code></strong> — slay/slap access.</li><li><strong><code>f</code></strong> — map change access.</li></ul><p>So <code>amx_ban</code> specifically needs flag <code>d</code>. An admin set up with only <code>c</code> can kick but will get "no access" on a ban. The commonly assigned "full admin" flag string bundles most of these; if your entry has a narrow flag set, widen it to include <code>d</code> for banning.</p><h2>3. Fix the users.ini entry and its auth mode</h2><p>Admins are defined in:</p><pre>addons/amxmodx/configs/users.ini</pre><p>Each line is an identity, a password, an access-flags string, and an account-flags string that says <em>how</em> to authenticate:</p><pre>"STEAM_0:1:12345678" "" "abcdefghijklmnopqrstu" "ce"</pre><p>The last field is where recognition breaks. The account flag decides the auth method:</p><ul><li><strong><code>c</code></strong> means "this is a SteamID" — authenticate by Steam ID, no password. This is the reliable method for a Steam server.</li><li><strong><code>d</code></strong> in the account field means match by IP.</li><li>Without <code>c</code>/<code>d</code>/<code>e</code> set appropriately, AMXX expects a <strong>password</strong> and you must set <code>setinfo _pw "yourpass"</code> in your client config — forget that and you are never authenticated.</li></ul><p>The most common failure is a SteamID entry whose account flag does not include <code>c</code>, so AMXX waits for a password that never comes and treats you as a non-admin. Set the account flag to authenticate by SteamID and make sure the SteamID string matches your real ID exactly — find yours with <a href="/tutorials/find-player-steamid">the SteamID guide</a>.</p><h2>4. Reload admins so the change takes effect</h2><p>Editing <code>users.ini</code> does nothing until AMXX re-reads it. From the console:</p><pre>amx_reloadadmins</pre><p>This reloads the admin list without a map change. Reconnect if your access still is not picked up, since some setups match admins on connect. Then run <code>amx_who</code> again and confirm your flags now include what the command needs.</p><h2>5. Check the immunity and default-access cvars</h2><p>Two settings quietly change who can do what. <code>amx_default_access</code> grants a baseline flag string to <em>every</em> connecting player — leave it empty on a public server, because a stray value here can either hand out access you did not intend or, if misconfigured, interfere with how entries are matched. Separately, a target's immunity flag (<code>a</code>) blocks lower admins from acting on them, so a ban that is refused because the target is immune reads differently from "no access to that command" — the command ran but the action was denied. If <code>amx_who</code> shows you hold flag <code>d</code> yet a specific ban still fails, check whether the target carries immunity rather than assuming your own access is broken. Keeping the flag model explicit — who is an admin, what flags they hold, and who is immune — is what stops these three separate refusals from blurring together.</p><h2>Troubleshooting</h2><ul><li><strong>Not listed as admin in <code>amx_who</code></strong> — auth failed. The SteamID does not match, or the account flag does not say to auth by SteamID, or a required password is unset.</li><li><strong>Listed but missing flag <code>d</code></strong> — you are an admin without ban access. Add <code>d</code> to your access-flags string.</li><li><strong>Worked before, broke on a non-Steam server</strong> — IDs there depend on Reunion/dproto; an unstable ID no longer matches your <code>users.ini</code> line. Pin the auth method to what those hand out.</li><li><strong>Edited users.ini, still refused</strong> — you did not run <code>amx_reloadadmins</code> or reconnect. The file is cached.</li><li><strong>Password mode never authenticates</strong> — you set the account flag to expect a password but never set <code>setinfo _pw</code> on your client. Switch to SteamID auth (<code>c</code>) instead.</li></ul><h2>Verification</h2><p>After editing <code>users.ini</code>, run <code>amx_reloadadmins</code>, reconnect, and check <code>amx_who</code> — your name should show the full flag string including <code>d</code>. Then run the command that was refused, such as <code>amx_ban</code> on a test target, and confirm it executes instead of printing the access error. If <code>amx_who</code> shows the flags but the command still refuses, the command needs a different flag than you think — re-check the flag it requires. A managed admin suite like the <a href="/plugins/csb-admin-menu">CSB Admin Menu</a> surfaces these flags in a menu so you are not editing the raw file by hand.</p>
