2. Cstrike module installation
This is the next faze of the amxmodx installation and it is very important . CStrike module installation will be made manually.
Download here the cstrike module and unzip it anywhere on disk. Open then the amxmodx 1.8.0-cstrike\addons\amxmodx folder. There you have five subfolders : configs, plugins,scripting,modules,data . Copy the files inside each subfolder in the folders with the same name in HLDS\cstrike\addons\amxmodx ( HLDS is the main directory of your server) .Example: files from amxmodx1.8.0-cstrike\addons\amxmodx\configs will go to HLDS\cstrike\addons\amxmodx\configs folder , etc… You `ll be asked if you want to overwrite the existing files and you shall send OK .
Attention! Copy the files inside the subfolders , not the folders themselves !
Now you have installed the AmxModX with the CStrike module on your server . To see if it works properly go to console and type “meta list” . The result should be Amxmodx - RUN .
3.Manual installation of AmxModX
This installation is a bit complicated and I don`t recomand it to beginners . For those who want headaches we`ll make a breef presentation.
a.Go to www. amxmodx.org and download the base package for Windows
b.Unzipp it in HLDS\cstrike\addons
c.Go back to amxmodx.org and download the addons of your choice.
d. Unzipp it in HLDS|cstrike\addons
e.Add this line in HLDS\cstrike\addons\metamod\plugins.ini
To see if it works go to console and type “meta list” . The display should be Amxmodx - RUN.
In order to be in control of your server you have to configure the admin.
Open the HLDS\cstrike\addons\amxmodx\configs\users.ini with wordpad ( HLDS is the main directory of your server) . Scroll down the page and you`ll find a line looking like this :
“loopback” “” “abcdefghijklmnopqrstu" "de". You have to edit this line .If you want an ip admin replace “loopback” with the ip and the put the flag “d”, as you see in the image :
If you want a nick admin replace “loopback” with the nick and the flag should be set to “e”.
Admin account levels and flags :
; Access flags:
; a - immunity (can't be kicked/baned/slayed/slaped and affected by other commmands)
; b - reservation (can join on reserved slots)
; c - amx_kick command
; d - amx_ban and amx_unban commands
; e - amx_slay and amx_slap commands
; f - amx_map command
; g - amx_cvar command (not all cvars will be available)
; h - amx_cfg command
; i - amx_chat and other chat commands
; j - amx_vote and other vote commands
; k - access to sv_password cvar (by amx_cvar command)
; l - access to amx_rcon command and rcon_password cvar (by amx_cvar command)
; m - custom level A (for additional plugins)
; n - custom level B
; o - custom level C
; p - custom level D
; q - custom level E
; r - custom level F
; s - custom level G
; t - custom level H
; u - menu access
; z - user (no admin)
; a - disconnect player on invalid password
; b - clan tag
; c - this is steamid/wonid
; d - this is ip
; e - password is not checked (only name/ip/steamid needed)
Admin account examples :
; Format of admin account:
; <name|ip|steamid> <password> <access flags> <account flags>
; Examples of admin accounts:
; "STEAM_0:0:123456" "" "abcdefghijklmnopqrstu" "ce"
; "220.127.116.11" "" "abcdefghijklmnopqrstu" "de"
; "My Name" "my_password" "abcdefghijklmnopqrstu" "a"
Atention !You don`t have to set all the acces levels to every admin !
If you want to see the commands you have acces to, join the game and console type amx_help . The first 10 commands will show . Next, type amx_help 11 , amx_help 21 , etc..
Seting up the admin password
The line should look like this :
"Name" "password" "abcde….." "a" . As you see the account flag changed to “a” .Your admins will have to console type setinfo_pw password , before they connect to your server .