Add install-amx-mod-x-1-8-2/en.md
Browse Source
Daemon666 committed
parent 5967910014
commit 58631a4133651759c97601d89cbe1c2a06fac656
1 changed file
with 93 additions and 0 deletions
install-amx-mod-x-1-8-2/en.md
A
| @@ -0,0 +1,93 @@ | ||
| 1 | +--- | |
| 2 | +title: "How to Install AMX Mod X 1.8.2 on a CS 1.6 Server" | |
| 3 | +excerpt: "Install the legacy AMX Mod X 1.8.2 base and CS module on a CS 1.6 server, set up admins, and know exactly what you give up by staying on 1.8.2." | |
| 4 | +category: "installation" | |
| 5 | +tags: "amxmodx, 1.8.2" | |
| 6 | +image: "" | |
| 7 | +read_time: "8 min read" | |
| 8 | +--- | |
| 9 | +<p>AMX Mod X 1.8.2 is from 2013 and it is still everywhere, because thousands of plugins were compiled against it and a lot of mod packs (Zombie Plague, old CoD Mod builds, half the Romanian and Turkish server scene) ship with it. It works. But be clear about the trade: <strong>1.8.2 does not have <code>client_print_color</code></strong>, its string natives are older, and a growing share of plugins on the forums simply will not compile against it. If you are building a new server, install <a href="/tutorials/install-amx-mod-x-1-9">AMX Mod X 1.9</a> instead. Install 1.8.2 when you are restoring an old server whose <code>.amxx</code> binaries you cannot recompile.</p> | |
| 10 | + | |
| 11 | +<h2>1. Prerequisites</h2> | |
| 12 | +<p>Metamod must already be working. Run <code>meta version</code> in the server console; if it answers <code>Unknown command: meta</code>, stop and fix Metamod first (<a href="/tutorials/install-metamod-r">Metamod-r</a> or <a href="/tutorials/install-metamod-p-legacy">Metamod-P</a>).</p> | |
| 13 | + | |
| 14 | +<h2>2. Download the two packages</h2> | |
| 15 | +<p>AMX Mod X ships as a <strong>Base</strong> package plus per-game addon packages. For CS 1.6 you need exactly two:</p> | |
| 16 | +<ul> | |
| 17 | +<li><strong>Base</strong> — the core, the modules, the config files.</li> | |
| 18 | +<li><strong>Counter-Strike addon</strong> — the <code>cstrike</code> and <code>csx</code> modules, the CS-specific plugins and configs.</li> | |
| 19 | +</ul> | |
| 20 | +<p>Take both for the same version (1.8.2) and the same platform. Mixing a 1.8.2 base with a 1.9 CS addon produces module load failures that make no sense until you notice the version mismatch.</p> | |
| 21 | + | |
| 22 | +<h2>3. Extract into cstrike/</h2> | |
| 23 | +<p>Both archives are laid out as <code>addons/amxmodx/...</code>, so they extract straight over the mod directory:</p> | |
| 24 | +<pre>cd /home/steam/hlds/cstrike | |
| 25 | +tar -xzf amxmodx-1.8.2-base-linux.tar.gz | |
| 26 | +tar -xzf amxmodx-1.8.2-cstrike-linux.tar.gz</pre> | |
| 27 | +<p>Resulting layout:</p> | |
| 28 | +<pre>cstrike/addons/amxmodx/ | |
| 29 | +├── configs/ (amxx.cfg, plugins.ini, users.ini, modules.ini, maps.ini …) | |
| 30 | +├── data/ (lang files, translations) | |
| 31 | +├── dlls/ amxmodx_mm_i386.so <-- the Metamod plugin | |
| 32 | +├── modules/ fun_amxx_i386.so, cstrike_amxx_i386.so, … | |
| 33 | +├── plugins/ *.amxx | |
| 34 | +└── scripting/ *.sma, amxxpc, include/</pre> | |
| 35 | + | |
| 36 | +<h2>4. Register AMXX with Metamod</h2> | |
| 37 | +<p>Add one line to <code>cstrike/addons/metamod/plugins.ini</code>:</p> | |
| 38 | +<pre>linux addons/amxmodx/dlls/amxmodx_mm_i386.so</pre> | |
| 39 | +<p>On Windows:</p> | |
| 40 | +<pre>win32 addons\amxmodx\dlls\amxmodx_mm.dll</pre> | |
| 41 | +<p>The path is relative to <code>cstrike/</code>. Getting this wrong is the number one cause of <a href="/tutorials/fix-meta-list-no-amxx">"meta list shows Metamod but not AMX Mod X"</a>.</p> | |
| 42 | + | |
| 43 | +<h2>5. Fix permissions</h2> | |
| 44 | +<pre>cd /home/steam/hlds/cstrike/addons/amxmodx | |
| 45 | +chmod -R u+rwX,go+rX . | |
| 46 | +chmod +x scripting/amxxpc scripting/compile.sh 2>/dev/null</pre> | |
| 47 | +<p>If the HLDS user cannot read <code>configs/</code>, AMXX loads but every config is empty — no admins, no plugins.</p> | |
| 48 | + | |
| 49 | +<h2>6. Configure admins</h2> | |
| 50 | +<p>Edit <code>addons/amxmodx/configs/users.ini</code>. The format is:</p> | |
| 51 | +<pre>; <name|ip|steamid> <password> <access flags> <account flags> | |
| 52 | +"STEAM_0:1:123456" "" "abcdefghijklmnopqrstu" "ce" | |
| 53 | +"MyNick" "mypassword" "abcdefghijklmnopqrstu" "a"</pre> | |
| 54 | +<p>Account flags decide how AMXX identifies you: <code>c</code> = the entry is a SteamID, <code>d</code> = it is an IP, <code>a</code> = no password required, <code>e</code> = do not check password. <code>ce</code> — SteamID, no password — is the correct setup for a Steam server. Access flag <code>z</code> is a common shorthand for "user immunity/everything" in some plugin sets; the full flag list is in <code>amxx.cfg</code>'s comments.</p> | |
| 55 | +<p>If admin does not work after this, the cause is almost always one of: wrong SteamID (check with <code>status</code> in the console), missing <code>c</code> flag, or the file was edited while the server was running without <code>amx_reloadadmins</code>. See <a href="/tutorials/fix-admin-not-recognized">users.ini ignored</a>.</p> | |
| 56 | + | |
| 57 | +<h2>7. Restart and verify</h2> | |
| 58 | +<pre>meta list | |
| 59 | +amxx version | |
| 60 | +amxx plugins | |
| 61 | +amxx modules</pre> | |
| 62 | +<p><code>meta list</code> must show AMX Mod X as <code>RUN</code>. <code>amxx version</code> must print <code>1.8.2</code>. <code>amxx plugins</code> lists every plugin with a status:</p> | |
| 63 | +<pre>Currently loaded plugins: | |
| 64 | + name version author file status | |
| 65 | + [ 1] Admin Base 1.8.2 AMXX Dev Team admin.amxx running | |
| 66 | + [ 2] Admin Commands 1.8.2 AMXX Dev Team admincmd.amxx running | |
| 67 | + [ 3] Menus Front-End 1.8.2 AMXX Dev Team menufront.amxx running</pre> | |
| 68 | +<p>In-game, type <code>amxmodmenu</code> in the console. If the admin menu opens, admin access works.</p> | |
| 69 | + | |
| 70 | +<h2>What you do not get on 1.8.2</h2> | |
| 71 | +<ul> | |
| 72 | +<li><code>client_print_color()</code> — coloured chat requires a manual <code>SayText</code> message. Plugins from 2015 onward often use the native and will not compile.</li> | |
| 73 | +<li>Newer string/array natives, and a number of 1.9 API additions.</li> | |
| 74 | +<li>Fixes for several known crashes in the 1.8.2 core that were only addressed in 1.9.</li> | |
| 75 | +</ul> | |
| 76 | +<p>When you are ready, <a href="/tutorials/upgrade-amxmodx-1-8-2-to-1-10">the upgrade path to 1.10</a> is well trodden and mostly painless if you keep your <code>.sma</code> sources.</p> | |
| 77 | + | |
| 78 | +<h2>Common errors</h2> | |
| 79 | +<ul> | |
| 80 | +<li><strong><code>Plugin failed to load: Invalid Plugin</code></strong> — an <code>.amxx</code> compiled for a newer AMXX. 1.8.2 cannot load a 1.10-compiled plugin. Recompile from source.</li> | |
| 81 | +<li><strong><code>Module failed to load</code></strong> — an architecture or version mismatch in <code>modules/</code>. See <a href="/tutorials/fix-amxx-module-failed-to-load">the module load fix</a>.</li> | |
| 82 | +<li><strong><code>amxx: Unknown command</code></strong> — AMXX is not loaded. <code>meta list</code> will confirm; the fault is in <code>plugins.ini</code>.</li> | |
| 83 | +<li><strong>Admin menu does nothing</strong> — <code>amxmodmenu</code> exists but your flags are empty. Check <code>users.ini</code> and run <code>amx_reloadadmins</code>.</li> | |
| 84 | +</ul> | |
| 85 | + | |
| 86 | +<h2>Verification checklist</h2> | |
| 87 | +<ol> | |
| 88 | +<li><code>meta list</code> — AMX Mod X <code>RUN</code>.</li> | |
| 89 | +<li><code>amxx version</code> — prints 1.8.2.</li> | |
| 90 | +<li><code>amxx plugins</code> — everything <code>running</code>, nothing <code>bad load</code> or <code>error</code>.</li> | |
| 91 | +<li><code>amxmodmenu</code> in-game opens the menu for your admin account.</li> | |
| 92 | +<li><code>addons/amxmodx/logs/error_*.log</code> is empty after a full map.</li> | |
| 93 | +</ol> | |
| 0 | 94 |
