Almost every CS 1.6 server you have ever played on ran AMX Mod X. It is the platform that provides admin commands, ranks, menus, VIP shops, zombie modes and nearly every custom feature on a community server. But it is not a single mod you install and forget — it is a scripting engine with a specific place in a stack of layers, and understanding that stack is what turns "I pasted a plugin and it broke" into "I know exactly why".
1. Where AMX Mod X sits
Four layers stack on a CS 1.6 server, each loading the next:
| Layer | Role |
|---|---|
| Engine (HLDS / ReHLDS) | Networking, physics, entities. |
| Game rules (CS / ReGameDLL) | Rounds, weapons, buy menu. |
| Metamod / Metamod-r | A loader that lets add-ons hook the engine. |
| AMX Mod X | A Metamod plugin that runs your .amxx scripts. |
The key fact: AMX Mod X is itself a Metamod plugin. It cannot load without Metamod, and Metamod cannot load without the engine knowing about it via liblist.gam/plugins.ini. If Metamod is not set up, AMXX does nothing — see fixing Metamod bad load.
2. Plugins: .sma source and .amxx binary
A plugin is written in Pawn, a small C-like scripting language, and saved as a .sma source file. It is compiled by amxxpc into a .amxx binary that the server actually loads:
myplugin.sma --amxxpc--> myplugin.amxx
You drop the .amxx into addons/amxmodx/plugins/ and list it in plugins.ini. Compiling is covered in compiling .sma to .amxx, and the language basics in Pawn basics. Our own plugin directory keeps only the source and compiles it on demand — you can read a plugin like CSB Admin Menu before you ever run it.
3. Modules: the native extensions
Pawn on its own cannot touch the game deeply. Modules are compiled native libraries that expose extra functions to plugins. The common ones:
fakemeta // low-level engine hooks hamsandwich // game-logic hooks (spawn, damage, death) cstrike // CS-specific (money, team, models) csx // stats and rank events engine, fun // movement, effects, entity helpers sqlx, nvault // databases and persistent storage geoip // country lookup by IP
A plugin declares what it needs with #include; the matching modules must be enabled in modules.ini or the plugin fails with module failed to load.
4. The config files that run it
AMX Mod X is driven by a handful of files under addons/amxmodx/configs/:
plugins.ini— which plugins load, in what order.modules.ini— which native modules load.users.ini— who is an admin and what access flags they have.amxx.cfg— core cvars: access defaults, activity display, flood control.
5. What you get out of the box
A stock install already gives you the essentials: kick, ban, slap, map change, vote and menu commands (amx_kick, amx_ban, amx_map), plus nextmap, timeleft and mapchooser. Everything beyond that — ranks, shops, game modes — is third-party or CSB plugins you add on top. See adding an admin by SteamID to make yourself an admin, and the ban commands to moderate.
6. Versions
Three versions are in the wild: 1.8.2 (old but still common), 1.9 (the safe default), and 1.10 (current). Newer natives like client_print_color do not exist in 1.8.2, so a plugin that uses them needs 1.9 or later. If you are choosing, install 1.9; if you inherited an old box, consider upgrading.
Common misconceptions
- "AMXX is a cheat/anti-cheat." No — it is an admin and scripting platform. Anti-cheat plugins run on it, but AMXX itself is neutral.
- "I can paste any plugin." Only if its modules are enabled and its version matches your core, and only if you trust the source — see spotting a backdoored plugin.
- "AMXX replaces the game." No — game rules are the CS/ReGameDLL layer. AMXX scripts on top of them.
Verification
From the server console, run meta list and confirm AMX Mod X appears as a running Metamod plugin, then amxx plugins and amxx modules to see the scripts and native modules that loaded. If AMXX is missing from meta list, the problem is the Metamod layer beneath it, not AMXX. Once it loads cleanly, add yourself as an admin and write your first plugin to see the whole pipeline end to end.
