Search for a CS 1.6 admin plugin and you will trip over two names that look almost identical: AMX Mod and AMX Mod X. They are not the same project, their plugins are not interchangeable, and downloading a plugin for the wrong one is a classic reason a .amxx refuses to load. Here is the distinction and why it still matters in 2026.
1. AMX Mod — the original
AMX Mod was the original scripting platform, built by OLO (and associated authors) on top of the Small/Pawn language. It gave GoldSrc servers an admin system and a plugin API through Metamod, and for years it was the way to script Half-Life mods. It is, however, discontinued — development stopped long ago, it does not track modern engine changes, and it lacks the natives, modules, and fixes that arrived over the following two decades.
2. AMX Mod X — the community fork
AMX Mod X (AMXX) is a separate, community-driven fork that took the concept and rebuilt it into a far larger, actively-maintained platform. It is developed openly on GitHub, ships a rich module system (fakemeta, hamsandwich, cstrike, csx, reapi, and more), and continues to receive releases. When anyone today says "install AMXX" or references plugins.ini, amxx.cfg, or the amxx server command, they mean AMX Mod X. It is the standard, full stop — see what is AMX Mod X for the overview.
3. Why the plugins are not interchangeable
This is the part that bites people: AMX Mod plugins are not source-compatible with AMX Mod X. Although both use the Pawn language, they expose different includes and different natives:
- AMX Mod source includes headers and calls functions specific to its own API.
- AMX Mod X source includes
<amxmodx>,<amxmisc>,<fakemeta>,<hamsandwich>,<cstrike>, etc. — a different, much larger native set.
You cannot take an old AMX Mod .sma and compile it with the AMXX compiler and expect it to build; the includes and natives it references do not exist in the AMXX API. A plugin must be rewritten or ported, not just recompiled. And the compiled binaries differ too — an AMX Mod plugin binary will not load under AMX Mod X.
4. What this means when you download plugins
Practically, in 2026:
- If a plugin page says "for AMX Mod X" and gives a
.smathat#include <amxmodx>, it is for the modern platform — that is what you want. - If you find a very old plugin labelled just "AMX Mod" (no X), assume it will not work on a modern AMXX server without a port. Look for an AMXX equivalent instead; almost everything popular was reimplemented for AMXX years ago.
- The file extension is a hint but not proof: AMXX plugins are
.amxx. Old AMX Mod used.amx. Seeing.amxis a strong sign it is the discontinued platform.
5. Why AMXX won
The fork overtook the original for concrete reasons worth knowing. AMXX added a real module system — fakemeta for low-level engine hooks, hamsandwich for game-DLL virtual functions, cstrike for CS-specific natives, csx for stats, sqlx for databases, and later reapi for ReHLDS/ReGameDLL hooks. None of that breadth existed in the original AMX Mod. It also kept pace with engine changes: when ReHLDS, ReGameDLL, and the 25th anniversary update reshaped the platform, AMX Mod X shipped compatible builds while the original stayed frozen. The result is that the entire modern plugin ecosystem — admin menus, stats, VIP shops, gamemodes — is written for AMXX, and finding a maintained plugin for the original AMX Mod today is nearly impossible.
Common misconceptions
- "AMX Mod X is just a newer version of AMX Mod." No — it is a separate fork with a different API, not a sequential release of the same codebase.
- "I can recompile an AMX Mod plugin for AMXX." Not without porting. The includes and natives differ; the source will not build unchanged.
- "The X stands for version 10 / roman numeral." It does not indicate a version number; it is part of the fork's name. AMXX has its own version line — see AMX Mod X versions explained.
- "A .amx file works on my AMXX server." AMXX loads
.amxxfiles. A raw.amxfrom old AMX Mod will not load. - "AMX Mod is still maintained." It is discontinued. All active development, modules, and engine-compatibility work happens in AMX Mod X.
How to tell which one you have
On the server, run meta list in the console — the loaded scripting platform shows up as a Metamod plugin. AMX Mod X reports itself as AMX Mod X; the classic one as AMX Mod. Then check your addons/ folder: a modern install has an addons/amxmodx/ directory with plugins/, configs/, and modules/ subfolders. If you inherited a server on the discontinued AMX Mod, the right move is to migrate to AMX Mod X and replace the plugins with their AMXX equivalents — start from installing AMX Mod X 1.9. Everything else you read on this site assumes the AMXX platform.
