How to Install AMX Mod X 1.10 on ReHLDS

AMX Mod X 1.10 is the current line. On a modern stack — ReHLDS, ReGameDLL, Metamod-r — it is what you want: it has every 1.9 native plus later additions, its core carries fixes 1.9 never got, and it is what current plugin sources are written against. The one caveat is old binary plugins: an .amxx compiled for 1.8.2 is not guaranteed to run on 1.10, and if you do not have the .sma, you cannot fix that.

1. Prerequisites

In the server console, all three of these must answer:

version
regamedll_version
meta version

version must show a ReHLDS version: line, and the other two must print their versions. If one does not, install that layer first: ReHLDS, ReGameDLL, Metamod-r. AMXX is the top of the stack, not the bottom.

2. Download Base + Counter-Strike, both 1.10

Two packages, same version, same platform:

• AMX Mod X 1.10 Base
• AMX Mod X 1.10 Counter-Strike addon (provides cstrike, csx, the CS plugins and configs)

3. Extract

cd /home/steam/hlds/cstrike
tar -xzf amxmodx-1.10.0-base-linux.tar.gz
tar -xzf amxmodx-1.10.0-cstrike-linux.tar.gz
chown -R steam:steam addons/amxmodx
chmod -R u+rwX,go+rX addons/amxmodx
chmod +x addons/amxmodx/scripting/amxxpc addons/amxmodx/scripting/compile.sh

4. Register with Metamod

In cstrike/addons/metamod/plugins.ini:

linux addons/amxmodx/dlls/amxmodx_mm_i386.so

If you are replacing an older AMXX, make sure there is exactly one uncommented AMXX line. Two AMXX entries — a leftover 1.8.2 path plus the new one — is a genuinely nasty failure: Metamod tries to load both cores and the server crashes or behaves erratically.

5. modules.ini

addons/amxmodx/configs/modules.ini:

fun
engine
fakemeta
geoip
sockets
regex
nvault
cstrike
csx
hamsandwich
;mysql
;sqlite

Enable what your plugins actually #include. If you plan to use ReAPI, its module is dropped into modules/ and auto-loaded when a plugin requires it — you do not normally need to list it by hand, but doing so does no harm.

6. Restart and verify

meta list
amxx version
amxx plugins
amxx modules

Currently loaded plugins:
       name                 version   author         file             status
 [  1] Admin Base           1.10.0    AMXX Dev Team  admin.amxx       running
 [  2] Admin Commands       1.10.0    AMXX Dev Team  admincmd.amxx    running
 …
25 plugins, 25 running

amxx modules should show each module as running with its version. A module that is not running, or that shows a different version from the core, is a problem. A 1.9 module left in a 1.10 modules/ directory still loads and says running, so check the version column for it. Delete the stale file; the 1.10 packages ship all of them.

7. Old plugins on a new core

This is the whole reason people hesitate to move to 1.10. Three outcomes for an old .amxx:

• It just works. Most simple plugins do.
• Plugin failed to load: Invalid Plugin — not a version problem: 1.8.2, 1.9 and 1.10 compilers write the same file format, so the file is damaged or is not a real .amxx. Re-upload it, or recompile from the .sma.
• It loads and then throws Run time error 10: native error — it calls a native whose behaviour changed, or one that was removed. Again: recompile from source, fix what the compiler complains about.

Recompiling is usually trivial:

cd /home/steam/hlds/cstrike/addons/amxmodx/scripting
./amxxpc myplugin.sma -o compiled/myplugin.amxx

Fix any errors it prints, then copy the result into plugins/. If you are moving a whole server, work through the 1.8.2 → 1.10 upgrade guide — it covers the specific natives that changed and the ordering that avoids downtime.

Common errors

• Module requested a not existing function — you have a 1.9 or 1.10 module sitting in a 1.8.2 install; amxx modules shows it as newer, and 1.8.2 spells the message not exisitng. Modules and core must come from the same release. See that error.
• Plugin uses an unknown function (name "...") — the plugin calls a native your core or modules do not provide, for example one added in 1.9 (such as client_print_color) in a plugin loaded on 1.8.2, or one from a module you have not installed. Recompile against your version, or install the module. (Invalid Plugin is not a version mismatch; it means a damaged or non-.amxx file.)
• Plugins show bad load after the upgrade — the common upgrade symptom; see plugins bad load after upgrading.
• Run time error 4: index out of bounds in a plugin that used to work — an array-bounds bug that 1.8.2 tolerated and 1.10 catches. That is the newer core doing its job; fix the plugin.
• Server crashes at map start after the upgrade — two AMXX cores in metamod/plugins.ini, or a leftover modules/ from the old version.

Verification checklist

1. amxx version reports 1.10.x.
2. amxx plugins — count of running equals the total; nothing in bad load or error.
3. amxx modules — every module running.
4. amxmodmenu opens in-game.
5. addons/amxmodx/logs/error_*.log is empty after a full map with players.

Watch that error log for the first day. Runtime errors in AMXX do not crash the server; they get logged and the plugin keeps limping. An empty error_*.log after 24 hours of real traffic is the only upgrade verification that actually means anything.