# XH-A01: A map change ran inside a plugin's server_exec (/docs/xhlds/codes/xh-a01)

**Printed:** when a map change (`changelevel`, `map`, `restart`, ...) starts inside a plugin's or the game's `server_exec` (Linux, crash reports on), once per map change, also in the server log.

A plugin (or the game) ran the server's waiting console commands with `server_exec` while a map change was among them (`changelevel`, `map`, `restart`, ... queued by a map vote, a map rotation or `server_cmd`). The map change then ran inside that plugin's call, before it returned: AMX Mod X unloaded every plugin, this one too, and loaded the next map's. When the plugin's code goes on after `server_exec` it runs on freed memory, and its next native call can crash the server, usually while the next map loads. The line names the plugin that called `server_exec`, which is not always the one that asked for the map change; without a plugin it names the module that called `server_exec`.

**Is it a problem?** Yes when it names a plugin: the server can survive it many times and then crash. A crash report after it names the plugin (`level_change_nested_plugin=`).

**What to do:** update or remove the plugin, and tell its author: `server_exec` runs every command waiting, map changes too. A plugin that runs `server_cmd` and `server_exec` when players join (e.g. to read `dp_clientinfo`) runs a map change that another plugin queued at that moment.

## On the server [#on-the-server]

[`xhlds_explain XH-A01`](/docs/xhlds/commands#xhlds_explain) prints this explanation on the server console, also over rcon.
