Fix: 'meta list' Shows Metamod but Not AMX Mod X

Metamod itself is working — meta version answers and meta list prints something — but AMX Mod X is not in that list, so none of your admin commands, stats, or plugins exist. This is almost always a registration problem: AMX Mod X is itself a Metamod plugin, and Metamod only loads it if it is correctly listed in Metamod's own plugin file with a valid path to the right binary. Metamod loading does not imply AMXX loading; they are two separate steps.

1. Confirm what meta list actually shows

From the server console:

meta list

Every Metamod plugin appears here with a status. AMX Mod X should show as a running plugin. If it is missing entirely, Metamod never tried to load it — the line is absent or wrong. If it appears but with a bad status, the file was found but failed to load (wrong architecture, corrupt, or missing dependency). Those are different fixes, so read the status before changing anything.

2. Check the Metamod plugins.ini entry

AMX Mod X is registered in Metamod's plugin list, not the engine's:

addons/metamod/plugins.ini

This file must contain a line pointing at the AMXX Metamod binary. The format is a platform tag followed by the path. On Linux:

linux addons/amxmodx/dlls/amxmodx_mm_i386.so

On Windows:

win32 addons\amxmodx\dlls\amxmodx_mm.dll

Do not confuse this with addons/amxmodx/configs/plugins.ini, which lists your .amxx scripts. That file is only ever read after AMXX loads. If AMXX is not in meta list, editing the AMXX plugins.ini does nothing — you are one layer too high.

3. Fix the filename and platform traps

Three things break this line constantly:

• Wrong platform tag — a win32 line on a Linux box (or vice versa) is silently ignored, so AMXX never loads and there is no error. Match the tag to the OS.
• Wrong architecture suffix — the Linux binary is typically the 32-bit amxmodx_mm_i386.so. If your line points at a name that does not exist on disk, nothing loads. List the addons/amxmodx/dlls/ folder and use the exact filename that is there.
• Wrong relative path — the path is relative to the mod folder (cstrike/). A leading slash or an extra cstrike/ breaks it.

4. Confirm Metamod is loaded via the game DLL, not the reverse

Because meta list works, Metamod is loaded correctly (through liblist.gam or the plus-set gamedll override). That rules out the Metamod-side install and points the finger squarely at the AMXX line. If instead meta version failed too, you would have a Metamod problem, not an AMXX one — see the broader Metamod and AMX Mod X install guide for that case.

5. Match the AMXX build to the engine

The classic GoldSrc engine is 32-bit, so the AMXX Metamod binary must be the 32-bit build. Mixing a 64-bit .so against a 32-bit engine gives a bad load rather than a missing entry, and the reverse (a 32-bit binary the OS cannot load because the 32-bit runtime libraries are absent on a 64-bit-only host) fails the same way. If meta list shows AMXX with a bad status rather than as running, this architecture mismatch is the usual reason — re-copy the AMXX release that matches your engine, and on a 64-bit Linux host make sure the i386 C runtime is installed so a 32-bit .so can load at all. The Windows build has no such split, but the win32 tag must still match the OS.

Troubleshooting

• AMXX absent from meta list — the line in addons/metamod/plugins.ini is missing, commented, or has the wrong platform tag.
• Line present but status is bad load — the binary exists but is the wrong architecture (a 64-bit .so against a 32-bit engine) or corrupt. Re-copy the matching build.
• Edited the wrong plugins.ini — you added your scripts to addons/amxmodx/configs/plugins.ini, but AMXX is registered in addons/metamod/plugins.ini. Fix the Metamod one first.
• Nothing changed after editing — the file is only read at map load. Change the map or restart the server.
• amxx version is an unknown command — AMXX genuinely did not load, confirming the meta list finding; keep working the Metamod line, not the AMXX config.

Verification

Change the map so both plugin files are re-read, then run meta list again — AMX Mod X should now appear as running. Confirm from the other side with:

amxx version
amxx plugins

amxx version should print the AMXX build, and amxx plugins should list your scripts loading. Once AMXX shows in meta list and answers amxx version, the two-layer chain — engine loads Metamod, Metamod loads AMXX, AMXX loads your plugins — is intact, and any remaining issue is with an individual script, which is a different problem covered in module failed to load.