---
title: "amx_map, amx_extendmap and Changelevel Commands"
excerpt: "The difference between amx_map, the engine changelevel command and amx_votemap, how extending a map really works, and how to avoid a failed changelevel."
category: "administration"
tags: "maps, admin"
image: ""
read_time: "8 min read"
---
<p>There are three different ways to change or prolong the current map on a CS 1.6 server, and admins routinely confuse them: the AMX Mod X <code>amx_map</code> command, the raw engine <code>changelevel</code>, and map <em>extension</em>. They behave differently — one validates the map for you and one will happily try to load a map that does not exist — so it is worth knowing exactly which does what.</p>

<h2>1. amx_map: the safe admin command</h2>
<p><code>amx_map</code> is provided by the AMXX admin-commands plugin. It changes the level, but first it validates that the map exists on disk and gives players a short heads-up before the switch:</p>
<pre>amx_map de_inferno</pre>
<p>Because it checks the map before committing, a typo gets rejected with a message rather than dropping everyone into a broken load. It requires the map-change access flag (see the <a href="/tutorials/amxx-admin-flags-reference">flags reference</a>). This is the command you should use day to day.</p>

<h2>2. changelevel: the raw engine command</h2>
<p><code>changelevel</code> is a built-in engine command, not an AMXX one. It changes the map immediately with no validation and no warning:</p>
<pre>changelevel de_nuke</pre>
<p>It is fine from RCON or the server console when you know the map is installed, but it has two sharp edges. First, it does no existence check — point it at a missing map and the server fails the transition. Second, because it bypasses the <a href="/tutorials/mapcycle-txt-setup">mapcycle</a> position logic, jumping to a map that is not in your cycle resets the rotation to the top afterwards. Prefer <code>amx_map</code> unless you have a specific reason to use the engine command directly.</p>

<h2>3. amx_votemap: let players decide</h2>
<p>When you would rather put the change to a vote than force it, use <code>amx_votemap</code>:</p>
<pre>amx_votemap de_dust2 de_train cs_office</pre>
<p>This opens a short vote between the listed maps and changes to the winner. For a permanent player-driven system rather than a one-off admin vote, install <a href="/tutorials/rtv-nextmap-setup">Rock The Vote and nextmap</a> instead — that is the maintained way to hand map choice to players.</p>

<h2>4. Extending the current map</h2>
<p>Extending means keeping the <em>current</em> map running longer by pushing back <code>mp_timelimit</code>, rather than changing to a new one. The extend feature is part of the end-of-map vote system (<code>mapchooser</code>) and is governed by two cvars:</p>
<pre>amx_extendmap_max 90     // ceiling: a map may be extended to at most this many minutes total
amx_extendmap_step 15    // how many minutes each successful "Extend" adds</pre>
<p>When "Extend" wins the end-map vote, the plugin raises <code>mp_timelimit</code> by the step, up to the max. There is no universal stock <code>amx_extendmap</code> command in a default install — an explicit "extend now" admin command comes from an add-on plugin such as <a href="/plugins/csb-admin-extend-map">CSB Admin Extend Map</a>. If you want admins to extend on demand rather than only through a vote, install that plugin; the cvars above still cap how far it can go.</p>

<h2>5. Manual extend without a plugin</h2>
<p>You can always extend by hand from RCON by raising the time limit on the fly:</p>
<pre>mp_timelimit 45</pre>
<p>That adds time to the running map immediately. It is blunt but reliable, and it is exactly what the extend feature automates. Just remember the value is in minutes and it applies to the current map only — the next map starts fresh from whatever your config sets. For the full list of round and map timing cvars, see the <a href="/tutorials/mp-cvars-reference">mp_ cvars reference</a>.</p>

<h2>Common errors</h2>
<ul>
<li><strong><code>changelevel failed</code> or the server hangs on switch</strong> — the target map is not in <code>cstrike/maps/</code>. Use <code>amx_map</code>, which validates first, or confirm the <code>.bsp</code> is installed.</li>
<li><strong>Rotation jumps to the first map after a manual change</strong> — you used <code>changelevel</code> (or <code>amx_map</code>) to a map not in the cycle. That is expected; add the map to <code>mapcycle.txt</code> if you want it in rotation.</li>
<li><strong>Extend does nothing</strong> — <code>mp_timelimit</code> is 0, so there is no time limit to extend. Set a real limit first.</li>
<li><strong>Map extends forever</strong> — <code>amx_extendmap_max</code> is too high or unset, so a popular map never ends. Cap it to a sane ceiling.</li>
<li><strong><code>Unknown command: amx_extendmap</code></strong> — there is no such stock command; the on-demand extend comes from an add-on plugin. Install one or raise <code>mp_timelimit</code> manually.</li>
</ul>

<h2>Verification</h2>
<p>Run <code>amx_map</code> with a valid map and confirm the warning appears and the switch completes. Try it with a deliberately misspelled name and confirm it is rejected rather than crashing the server. To test extend, set <code>mp_timelimit 2</code>, let the end-map vote appear, choose Extend, and read the limit back:</p>
<pre>mp_timelimit</pre>
<p>It should now show the original value plus <code>amx_extendmap_step</code>, capped at the max. Once the map controls behave, tie them into your rotation with the <a href="/tutorials/mapcycle-txt-setup">mapcycle.txt guide</a>.</p>