metamod/plugins.ini Explained (Paths, win32 vs linux)

Metamod's plugins.ini is the file that tells Metamod which game-DLL plugins to load — AMX Mod X, bots like POD-Bot and YaPB, and any other Metamod plugin. It is small and its syntax is simple, but two things trip people up constantly: it is not the same file as AMXX's own plugins.ini, and each line has a platform column that must match your OS. This is a precise breakdown of the format.

1. There are two files called plugins.ini

This is the number-one confusion. There are two completely different plugins.ini files:

• addons/metamod/plugins.ini — lists Metamod plugins (native DLLs/SOs): AMXX itself, bots, and similar. This is the file this guide is about.
• addons/amxmodx/configs/plugins.ini — lists AMXX plugins (Pawn .amxx files): admin.amxx, your custom plugins. Covered in plugins.ini load order.

Adding a bot to the AMXX file, or a .amxx to the Metamod file, silently fails. AMXX is the bridge: it is a line in the Metamod file, and it then reads its own file for Pawn plugins.

2. The line format

Each non-comment line has two parts — a platform keyword and a path to the binary:

<platform> <path-to-plugin-binary>

For example, the line that loads AMX Mod X looks like this on each OS:

linux addons/amxmodx/dlls/amxmodx_mm_i386.so
win32 addons/amxmodx/dlls/amxmodx_mm.dll

The first token is the platform; the rest of the line is the file Metamod loads.

3. win32 vs linux

The platform keyword tells Metamod to only load that line on the matching operating system. win32 lines load on a Windows server; linux lines load on a Linux server. You can keep both lines for the same plugin in one file — Metamod loads the one that matches the host and ignores the other — which is exactly how a plugin ships a cross-platform plugins.ini:

linux addons/podbot/podbot_mm_i386.so
win32 addons/podbot/podbot_mm.dll

On Linux, Metamod loads the .so and skips the .dll; on Windows, the reverse. If you list only the win32 line and run on Linux, the plugin simply never loads — and there is no error, because Metamod correctly skipped a non-matching platform line. That silent skip is why "I added the line but nothing loaded" is so often a wrong platform keyword.

4. Paths are relative to the game directory

The path is relative to the mod folder — cstrike/ for Counter-Strike — not to addons/metamod/ and not absolute. So addons/amxmodx/dlls/amxmodx_mm_i386.so resolves to cstrike/addons/amxmodx/dlls/amxmodx_mm_i386.so. On Linux the file is a 32-bit .so ending _i386.so; on Windows a .dll. Use forward slashes; they work on both platforms. A wrong path, or a Linux server pointed at a .dll, produces a load failure at map start.

5. AMXX is just another plugin here

The key mental model: AMX Mod X is not special to Metamod — it is one Metamod plugin among several, loaded by one line in this file. Bots are peers of AMXX, each their own line. The load order between Metamod plugins rarely matters (unlike AMXX's Pawn plugins, where it can), so you can list AMXX and a bot in either order. Comment a line out with a leading semicolon to disable it without deleting it:

; win32 addons/podbot/podbot_mm.dll   ; disabled for now
linux addons/amxmodx/dlls/amxmodx_mm_i386.so

Troubleshooting

• Plugin does not load, no error — wrong platform keyword (a win32 line on Linux). Metamod silently skips non-matching lines. Use the keyword for your OS.
• "Couldn't load plugin" / bad load — wrong path or wrong binary type (a .dll on Linux). See fix Metamod bad load.
• meta list shows no AMXX — the AMXX line is missing or in the wrong plugins.ini. Work through meta list has no AMXX.
• Edited the file, nothing changed — plugins.ini is read at map load; change the map or restart.
• Put a .amxx in this file — wrong file. Pawn plugins go in addons/amxmodx/configs/plugins.ini, not here.

Verification

After editing, change the map and run meta list in the server console. Every plugin from this file that matched your platform should appear with a running status — AMXX, your bot, and anything else. A plugin you expected but do not see was skipped (wrong platform) or failed (wrong path); a plugin marked bad load loaded but errored. Cross-check against the Metamod-r install if the whole list is empty, which means Metamod itself is not loading.