---
title: "How to Unban a Player (banned Files, In-Game, and SQL)"
excerpt: "The three places a CS 1.6 ban lives, the removeid/removeip and writeid/writeip commands that actually delete it, the AMXX amx_unban limits, and how SQL-based bans differ."
category: "administration"
tags: "bans, admin"
image: ""
read_time: "8 min read"
---
<p>Removing a ban is fiddly because a ban can live in three different places, and clearing it from one does not touch the others. A player still blocked after you "unbanned" them is almost always banned somewhere you did not look. This covers the engine ban list, AMX Mod X commands, and database-backed bans, with the exact commands that remove each and persist the change.</p><h2>1. Know which kind of ban you have</h2><p>There are three independent systems:</p><ul><li><strong>Engine SteamID bans</strong> &mdash; added with <code>banid</code>, saved to the id ban file with <code>writeid</code>.</li><li><strong>Engine IP bans</strong> &mdash; added with <code>addip</code>, saved to the ip ban file with <code>writeip</code>.</li><li><strong>Plugin/SQL bans</strong> &mdash; an AMXX ban plugin storing bans in its own file or a MySQL table, independent of the engine list.</li></ul><p>List the engine bans first so you know what you are dealing with:</p><pre>listid
listip</pre><p><code>listid</code> prints every banned SteamID; <code>listip</code> every banned IP. If the player's ID or IP is not in either list, the ban is a plugin/SQL ban and the engine commands below will not help.</p><h2>2. Remove an engine SteamID ban</h2><p>Two steps, and the second is the one people skip:</p><pre>removeid STEAM_0:1:12345678
writeid</pre><p><code>removeid</code> drops the ban from the <em>running</em> server's memory; <code>writeid</code> rewrites the id ban file (commonly <code>banned_user.cfg</code>, or <code>banned.cfg</code> on older builds) so the removal survives a restart. <strong>Skip <code>writeid</code> and the ban comes back on the next map change or reboot</strong>, because the file still lists it and is re-read at startup. You can also <code>removeid</code> by the ban's slot number shown in <code>listid</code>.</p><h2>3. Remove an engine IP ban</h2><p>The IP equivalents, same two-step pattern:</p><pre>removeip 203.0.113.45
writeip</pre><p><code>writeip</code> saves the IP list (commonly <code>listip.cfg</code> or <code>banned_ip.cfg</code>). IP bans are blunt &mdash; they can catch a whole household or an ISP CGNAT pool &mdash; so if you are unbanning because you hit an innocent bystander, prefer SteamID bans in future. Note the engine can also short-circuit IP bans with <code>sv_filterban</code>; that cvar decides whether the list blocks or allows, so an unexpected ban behaviour can trace back to it.</p><h2>4. The AMX Mod X way</h2><p>From in-game as an admin, AMX Mod X exposes an unban command:</p><pre>amx_unban 203.0.113.45</pre><p>Be aware of a real limitation: <code>amx_unban</code> in the stock admin plugin operates on <strong>IP bans</strong> and runs <code>removeip</code>/<code>writeip</code> for you. It does not reliably clear a SteamID ban &mdash; for that you still use the console <code>removeid</code> + <code>writeid</code> above, or a ban-manager plugin that wraps SteamID unbanning in a menu. A maintained suite such as the <a href="/plugins/csb-ban-manager">CSB Ban Manager</a> or the <a href="/plugins/csb-admin-menu">CSB Admin Menu</a> gives you a searchable ban list and a one-click unban so you do not fat-finger a raw command.</p><h2>5. SQL / plugin bans are separate</h2><p>If you run a database-backed ban system (the common AMXBans-style setup), the ban lives in a MySQL table, not in the engine files, and the engine <code>removeid</code> will not touch it. Unban through that system's own tool &mdash; its web panel, its in-game menu, or a direct <code>DELETE</code> on the bans table keyed by SteamID. Clearing the engine list and leaving the SQL row is the number-one reason a "removed" ban re-applies the moment the plugin re-syncs its bans back into the engine on the next map.</p><h2>Common errors</h2><ul><li><strong>Ban returns after a restart</strong> &mdash; you ran <code>removeid</code>/<code>removeip</code> without <code>writeid</code>/<code>writeip</code>. The file still holds the ban and is re-read at boot.</li><li><strong><code>amx_unban</code> "worked" but they are still banned</strong> &mdash; it cleared an IP ban but the block is a SteamID ban. Use console <code>removeid</code> + <code>writeid</code>.</li><li><strong>Unbanned in-game, re-banned next map</strong> &mdash; a SQL/plugin ban re-synced into the engine. Remove it from the database, not just the engine list.</li><li><strong><code>removeid</code> says no such ban</strong> &mdash; wrong ID format or the ban is only an IP ban. Check <code>listid</code> and <code>listip</code> for the exact entry.</li><li><strong>Whole group of players unbanned by accident</strong> &mdash; you removed an IP range ban. IP bans are coarse; verify with <code>listip</code> before and after.</li></ul><h2>Verification</h2><p>After unbanning, list the relevant table and confirm the entry is gone:</p><pre>listid
listip</pre><p>Then restart the server and run them again &mdash; if the entry is still absent, your <code>writeid</code>/<code>writeip</code> (or database delete) stuck and the unban is permanent. Have the player reconnect to confirm. If they still cannot join, the ban lives in a system you have not cleared yet; work through all three sources above. To ban correctly in the first place, see <a href="/tutorials/find-player-steamid">finding a SteamID and banning with persistence</a>.</p>