How To Create CS1.6 Online Private Dedicated Server

How to Pick the Right Weapon in CS

2009-04-13T10:40:00.002+08:00

First find out what kind of player your are, If you are a long Range player, go with rifles or some times of SMG.
If you are a close ranger, try out with the Shotguns and Smgs.
So now that you have a gun, at first try these out on bots to get a feel for them.
Try entering some games and duke it out with some New people.

Remember that SMG's may be a cheap solution, they are not your super close range killers.
On the opposite hand, remember The M249 may be expensive, however that expense keeps you from buying other weapons later on.
Get body armor
Get familiarized with your favorite combos and save them.
Sniper rifles may be hard to aim with, but with enough practice, you dont have to buy an AWP to get an instant kill.
Auto snipers are good if you are trying to kill someone from the shadows. THIS IS A COMMON MISINTERPRETATION!!! Never use it as an assault rifle, It may fire automatically, but that just makes it a waste of money.

How to Improve Your Skill in Counter Strike

2009-04-01T08:59:00.000+08:00

Play with people who are a little bit better than you. If you play with people that are horrible or people that are much better than you, then you're not learning anything. As you get better, move up servers.
Remember to close memory and bandwidth consuming applications (IE: MSN, AIM, Limewire, etc.). If you experience lag, then try contacting your ISP or try fixing it in some way. If you lag in Counter-Strike, it can greatly alter how well you play.
Talk only when you're dead. If you try to talk while you're alive, you're wasting time, unless of course you're using voice communication. Also, most people ignore radio commands, so don't expect your teammates to come when you hit "c3." Regardless, use radio commands only when they warrant it (don't use "Need backup" unless you actually do need help, etc.)
Keep moving at all times, and when you are turning corners, jump and duck and stay crouched for a little bit, in case anyone planned on you popping out. This strategy can work well against snipers, but in an enclosed space it is always best to move quickly and always make sure to aim at head level unless you know the opponent is crouched. ALWAYS aim at head level unless you know the opponent is positioned differently.
Avoid crouching. Contrary to popular belief, crouching is a bad way to improve your aim, as it slows you from moving quickly and does absolutely nothing to sniper fire, which is dead on. However, if you are able to crouch under something, such as a train, then this will provide extra cover.
If you have the person inside of the 4 lines that make up your crosshair, you'll only shoot within those 4 lines. Thinking about that when you attack will probably help you quite a bit. This is only true if you have dynamic crosshair enabled! Try disabling the dynamic crosshair; most upper level players disable it because it makes aiming a lot easier with rifles and the deagle.
Sound is the most important factor in CS. By listening to footsteps, you can know when to start walking silently (default - shift) or to crouch and hide in a dark area. Then when your enemy walks out into the open.... Boom headshot! Also pay attention to the type of footstep sound, there are different sounds for gravel, wood, cement, and steel. Knowing which sound was made can pinpoint an enemy and make him very easy to shoot through a wall. These sounds are especially useful in detecting the elevation of a player, a good example would be de_nuke. Avoid hiding in obvious places, often times it's more of a surprise to an enemy to find you in the open than behind a paper-thin box.
Make sure to follow your teammates and stick together, as taking on a group of players by yourself can mean certain death except for the best of CS players. Also try to make sure that your teammates aren't trying to use grenades before you go around a corner, you might be asking for a flash in the face!
Know which weapons to use in which maps .If hte map is an open and wide spaced Sniper rifles would be a good option but if you are using magnum in close quarters and alleys you are most likely to be killed by a opponent who has M4.
Here are the guns which you should use :-
If the map is a closed one which involve close range fire fight choose a good assault rifle,shotgun,smg or machinegun.
Do not use SMG,machine guns and shotguns if the range is quite big because they are not very accurate.Use assault rifle or sniper rifles instead.
Always buy a flash-bang and a HE-grenade if you can afford it after buying your weapons/armor so if somebody is camping you can flash him out or grenade him out. Also try flashing the enemy in a hallway so that he's trapped and you can easily take him out.
Know where and when to throw a flashbang.If you throw it straight in front of you it will blind you as well.So, always throw flashbangs on corners or after throwing it hide behind some wall or obstacle and make sure it doesn't come in your view and try not to waste it throw only ifyou know there is someone but you can also throw it to ensure your safety such as throwing it into bomb site before moving in and defusing or planting.Often terrorists hide nearby the planted bomb and wait for there prey to come !
Don't be a hero and use a knife when attacking somebody in the back, he might just turn around and you will be helpless (unless he's afk of course). Besides, he can hear you pull your knife (a "tsing" noise). Also, you can achieve a one hit knife kill if you put your knife in his head area (head-shot).
Learn what walls and boxes can be shot through. Pinpointing an enemy with sound is very helpful, but there still remains the problem of having to remove that threat. There are options like flashes, grenades, and peeking the player in a one on one situation, but overall your best bet is to take the opponent out without risking yourself or wasting a flash or grenade that you may need later. It really pays to do your homework and learn where you can shoot walls effectively. Maps like de_nuke are very good for learning how to "wall" efficiently.
Learn about how long it takes for you to get from your spawn to specific places. For example on de_dust2, as a terrorist, if you know how long it takes for a CT to get into lower B tunnels, then all you have to do is listen. If you don't hear anything, you don't have to peek lower B and can continue on to the bombsite. Or, if you hear some footsteps, you can take appropriate measures to ensure that you don't die helplessly.
Join a league! Get together with a few other people and join a league of some kind, there are leagues for all different skill levels. Most of the really competitive teams play in CAL or CEVO. Most games are played in a 5on5 format on select bomb defuse maps. Those leagues can be found at www.caleague.com and www.cevolved.com respectively. There are other, less competitive leagues, but most serious players don't lend them any respect.
Be sure when sniping that you are not moving when you fire your shot. If you're moving, you will miss and having to wait until you can fire your next shot can be deadly. In order to successfully snipe you must either shoot accurately before the other person or get the other person to miss giving you time to aim and make the kill. To fire accurately you must be still or crouched in order to stop staffing quickly be sure to tp the opposite direction of where you are going. This will make you stop suddenly making you more accurate faster. In order to make the opponent miss try a jump crouch where you jump far out into the field of vision of the opponent and then as you land crouch. It is hard to hit you when u do this and the second you land you will be able to make a clean shot.
Basicly Practice ALOT Play dealth match a little also scrim as much as you can it will make you better at strats then go right into a pub with MATURE players not little kids

How to Be Harder to Hit in Counter Strike

2009-04-01T08:55:00.003+08:00

Counter-Strike is different from other shooters in that when you die, you're out for the rest of the round. This makes the task of staying alive much more important than in normal deathmatch games. There are a few ways to avoid being an easy target for the opposing team. Especially when it comes down to that 1 vs. 1 fight between you and the other man/woman, you don't want to be easy to hit. Note: These apply to both Counter-Strike 1.6 and Counter Strike: Source.

Don't stay in one place during open long distance gunfights. Move from side to side, strafe around and fire short 1-3 shot bursts at the enemy's head when you stop shortly between moves. It's never a good idea to stay in one place for a long time during fights, it will make you an easy target
When you surprise an enemy from the front and they start spraying at you, be mobile and try and get around them. Crouch, dance back and forth, jump on top of them, even switch to your pistol to increase your movement speed temporarily, do whatever it takes to avoid the gunfire.
Surprisingly, it's actually easier to outrun their spray when you're closer to them. It allows you the ability to run around them quicker. Why circle strafe 5 yards when you can strafe 1?
When your enemy is reloading, shoot, when your enemy is moving and and bursting, you move and shoot at them. Know how to counter their tactics. Consider utilising your knife when they are reloading, or even when they are shooting at you - a single "stab in the back" can take tens of points off their health.
If you're out in the open, you're fair game for snipers and a lot of other things. Use cover during fights over long distance, move back and forth between cover and burst shooting. Just make sure to change up your pattern so they can't figure you out.
When the opposite team starts rolling out the smokes and flashes, make sure you've got a retreat point you can maneuver to when you're blind. When they start kicking in the front door after they flash you, you don't want to be out where they can pick you off. Make sure your retreat point isn't too obvious either. When you can't find any retreat points to go to, it comes down to keeping mobile. Dodge back and forth, run and crouch when you stop, even bunny hopping will be of use sometimes.
You're less likely to die if you stick together with your team. It's easier to take on a threat when you've got people watching your back. Just make sure you're going with the right group. You can't count on a squad of n00bs to watch your back, make sure to stick with the more experienced players.
Don't be a coward. It's okay to run away from certain situations, but if you run away from everything, it's going to come down to either you vs. the entire other team, or you vs. that grenade bouncing your way.
Give help to your team mates. Your team will last longer this way, and hence keep you alive too as a benefit. Plus, if you cheap out on your team, there will likely be quite a few teamkills aimed at you in the coming rounds.
Know the maps that you play, and know the likely camping and sniping spots.
Be ready for anything. If you keep alert and think of the enemy's movements and tactics, you'll be less likely to be surprised by somebody jumping out at you with an ak spraying or a flash bouncing your way.

How to Install ZBOT for Counter-Strike 1.6

2009-02-12T13:34:00.000+08:00

This is how to install ZBOT for Counter-Strike 1.6. Think of ZBOT as an add on to Counter-Strike 1.6. Counter-Strike 1.6 does not allow you to play against bots alone. So, instead, there are files that are made called ZBOT that allows you to play with bots if the files are installed correctly into your cstrike folder.

NOTE: All the ZBOT files will be installed inside your cstrike folder. Go to
C:\Program Files\Steam\steamapps\your_email\counter-strike\cstrike

Also you want to make a backup of your liblist.gam file inside of your cstrike folder (Steam). It would be a good idea so just in case if you want to uninstall Zbot - you can. A tip is to move the file to your Desktop and make the file hidden.

Now lets begin.

1) Go to Google and type ZBOT for Counter-Strike 1.6 or just download it here.
(If link is not broken). There are various sites where you can download ZBOT from.

2) Extract the files to a temporary location to a place that you can easily remember; preferably the Desktop.

3) Open your newly added ZBOT folder and double click on Zbot. Double click again on cstrike.

4) Now open your cstrike folder at the path, C:\Program Files\Steam\steamapps\your_email\counter-strike\cstrike. Resize both cstrike windows so that they are facing one another. This is the easiest way to transfer files between two folders.
NOTE: The two cstrike folders will be confusing to follow. I will label which cstrike folders are which.

5) Look at the first folder, dlls in the ZBOT folder. Inside this folder is the zbotcz.dll file. Move it to the dlls folder in the Steam Folder.

6) Next is the Sounds folder in the ZBOT folder. Highlight both of the folders, misc and radio, with your mouse and move them both to your Sounds folder in the Steam Folder.

7) Then look at your Sprites folder in your ZBOT folder for a file called, shadow_circle.spr. Drag that file to your Sprites folder in the Steam folder.

8) Last but not least, highlight all the rest of the files: BotCampaignProfile, BotChatter, BotProfile, commandmenu.txt, zbot_command and liblist.gam in your ZBOT folder and move them to your Steam folder.

To uninstall ZBOT:
---------------------

Remove these files in your cstrike folder (STEAM).

1) SOUND - - misc | radio

2) dlls - - zbotcz.dll

3) Sprites - - shadow_circle.spr

4) BotCampaignProfile | BotChatter | BotProfile |commandmenu.txt | zbot_command.txt

5) Delete the liblist.gam file and then go to your Desktop and unhide the liblist.gam you hid before and then move that to your cstrike folder (STEAM).

How to operate ZBOT?
--------------------------

Go into Counter Strike 1.6 and select New Game. Select your map and any other credentials that you want to have (Round Limit, etc) on the other menu.

When your map loads and you start the game. Press "H" on your Keyboard. This will bring up the menu
(As seen in Screen Shot F).

- Quick Add Bot

This adds a quota of one bot to the opposing side. (If you are on the terrorists team, the bot would be added to the CT side, and vice versa).

- Set Bot Level

This sets the bot(s) difficulty level. The difficulties are: Easy, Medium, Hard and Expert.

- Add Specific Bot

This adds a bot to either of the two teams, T and CT. You have a choice.

- End Round

This ends the current round of the match.

- Kill all Bot

This kills all Bots on the map.

- Bot Quota

This will add a quota of five, seven and nine bots on the map. It evens the team up of course.

- Weapon Mode

Knives Only => This will allow bots to only use knives.
Pistols Only => This will allow bots to only use Pistols.
Snipers Only => This will allow bots to only use Sniper rifles.
All Weapons => This will allow bots to use all of the weapons.
Allow Sheild => This will allow bots to use the Tactical Sheild.
Allow Shotgun => This will allow bots to use Shotguns.

- Bot Join Team

Terrorist => The next bot that you add will be added to this team.
Counter Terrorist => The next bot that you add will be added to this team.

- Bot Stop

On => Will stop all bots in place. This is great if you want to take screenshots of skins and stuff to post on fps :D.
off => Turns the option off if the "on" setting is set.

- Map Change

Changes the Map.

- Settings

Pause => Pauses the game
Restart => Restarts the map

users.ini - Setting up admins

2009-01-26T11:41:00.005+08:00

users.ini - Setting up admins

The users.ini file in your addons\amx\config folder is where players are given admin priviledges under AMX. It contains the different levels of admin access for a default install. Below are some examples of how to set up admin access for your admins.

The first part of the users.ini file is labeled "Access Flags". These letters will define what commands your admins will have access to:
Access flags:
a - immunity (immune to AMX commands such as kick, slap, or ban.)
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

The next part of the users.ini is labeled "Account Flags". These options control how the user is authenticated:
Account flags:
a - disconnect player on invalid password
b - clan tag
c - this is steamid (or wonid)
d - this is ip
e - password is not checked (only name/ip/steamid needed)

The last part is only required if your server is a listen serverDedicated Server:
The server runs in a text console and was a seperate download apart from the client. Or it has been run from the Dedicated Server entry in Steam.

Listen Server:
You start up your client and then start the server from the in-game menu, then others connect to you.. This will allow you to have admin access while running the server.
"loopback" "" "abcdefghijklmnopqrstu" "de"
The format of making an admin

The format of the entry for each admin is this:

Admin Access by Player Name or Clan tag
(Best for LAN, ok for Internet)

This is not the best way to grant admin access. It requires the client to set a password on their end. Many players can do this, how ever many do not grasp the concept of editing config files let alone with the correct info. It's a burden on the person setting up the access and the person receiving it in the end, and there is no added security with this method over access by Steam ID.
"Puking Horse"If you change your name, then this will not work. "bizzybee"A password is required here or anyone using the name specified will have that persons admin access. "abcdefghijklmnopqrstu"Access flags "a"Account flags:
The a value is optional. This would deter players from trying to get admin access with by kicking them after too many wrong guesses.
"[-O-]"If your name does not have the clan tag in it, then this will not work. "wacky"A password is required here or anyone using the clan tag specified will have admin access "abcdefghijklmnopqrstu"Access flags "a"Account flags:
The a value is optional. This would deter players from trying to get admin access with by kicking them after too many wrong guesses.
(Hint: Hover your mouse over the admin entries listed above for additional tips)

Above is what you do on the server's side. The client must have the password entered on their side also. To do that, create a file in your cstrike folder called userconfig.cfg if you don't already have one. In it, have the client put setinfo _pw "password" in it. For example:
setinfo _pw "bizzybee"

The password field and password should match what you have on the server. For more info on this, go here.
Admin Access by IP address
(Best for LAN, ok for Internet)

You would want to use this method only if you are connecting to a server on a LANLocal Arena Network. On a LAN without internet access, players will not have unique Steam id's. So this method allows you to assign admin rights to your computer's address instead. If the IP is dynamic, then this could change though so keep that in mind.
"192.168.0.100"To find out what your IP is:
Win9x: Start/Run type winipcfg and press OK.
WinNT/2K/XP: Start/Run/cmd then type ipconfig and press enter. ""No password is required here, but the empty quotes are still required. "abcdefghijklmnopqrstu"Access flags. "de"Account flags:
The d indicates to authenticate the IP. The player name is ignored.
The e tells AMX to ignore the password field. Since you are connecting by IP this way, there is no need for a password. Note that the password field is still there, just blank.
Admin Access by Steam or WON ID
(Best for Internet, won't work for LAN with out Internet access.)

This is the method I prefer. Admin access is set up for the clients with this one line. The client doesn't have to do anything. Once you get the player's Steam ID, that's all that is needed. You don't even need a password since your Steam/WON ID is yours and no one else can have it unless your CD-Key gets out. (Use your wonid if applicable. Examples shown work for Steam and WON servers.)
"STEAM_0:1:12345"To find your Steam ID, connect to a server and type status inthe console. ""No password is required here, but the empty quotes are still required. "abcdefghijklmnopqrstu"Access flags. "ce"Account flags:
The c indicates to authenticate the Steam ID. The player name is ignored.
The e tells AMX to ignore the password field. There is no need for a password although it can be used if you insist. Note that the password field is still there, just blank.
Just a reserved slot?

I am going to use my preferred method shown above. While a reserved slot does not allow players to perform admin commands on others, it is still set up like any other admin would be set up, but with just one flag.
"STEAM_0:1:54321"To find your Steam ID, connect to a server and type status inthe console. ""No password is required here, but the empty quotes are still required. "b" Access flags. "ce"Account flags:
The c indicates to authenticate the Steam ID. The player name is ignored.
The e tells AMX to ignore the password field. There is no need for a password although it can be used if you insist. Note that the password field is still there, just blank.
Putting it all together

Now if all the players mentioned above were in the same users.ini file it would look like this:
"Puking Horse" "bizzybee" "abcdefghijklmnopqrstu" "a" ; Jason
"[-O-]" "wacky" "abcdefghijklmnopqrstu" "a" ; clan [-O-]
"192.168.0.100" "" "abcdefghijklmnopqrstu" "de" ; Jeff's IP
"STEAM_0:1:12345" "" "abcdefghijklmnopqrstu" "ce" ; Bigz - Mike
"STEAM_0:1:54321" "" "b" "ce" ; Mark

I like to use comments in config files and use of the TAB key keeps things formatted nicely too. Sometimes you can forget who some people are or they change their player name alot. So comments at the end of a line can be useful in adding more details about the person. Use a semi-colom ";" at the beginning of a comment in .ini files. What ever is behind the ; is ignored by AMX.

configs.ini - Configuration menu

2009-01-26T11:39:00.002+08:00

configs.ini - Configuration menu

The configs.ini file in your addons\amx\config folder contains a list of config files on your server that may be run from the Configuration Menu. This is enabled by using the amx_cfgmenu command and can be useful when starting a match, or for any special requirements you have. This is what the default configs.ini looks like:
; Menu configuration file
; File location: $moddir/addons/amx/config/configs.ini
; To use with Commands Menu plugin

; NOTE: By default in all settings the access level is set to "u".
; However you can change that, to limit the access to some settings.

; Commands Menu:
; <> <> <> <>
; "a" - execute from server console
; "b" - execute from admin console
; "c" - execute on all clients
; "d" - back to menu when executed

"PUBLIC Settings" "servercfgfile server.cfg;exec server.cfg" "a" "u"
"Clanbase" "exec clanbase.cfg;servercfgfile \'\'" "a" "u"
"Clanbase Charges Only" "exec clanbase_co.cfg;servercfgfile \'\'" "a" "u"
"Official CAL Match" "exec cal.cfg;servercfgfile \'\'" "a" "u"
"ProvingGrounds Server Config" "exec leagues/pg.cfg;servercfgfile \'\'" "a" "u"
"OGL CS Server Config" "exec ogl.cfg;servercfgfile \'\'" "a" "u"
"OGL CS FF Server Config" "exec ogl_ff.cfg;servercfgfile \'\'" "a" "u"
"OGL CS Advanced Server Config" "exec ogl_adv.cfg;servercfgfile \'\'" "a" "u"

(Note that a semi-colon ; was inserted at the beginning of some lines. This prevents them from being used.)

Adding additional entries to this menu should be the same as the lines in this file. Just change the name field and the file name (path too if applicable) to meet your need. Lets say you wanted to try out some deathmatch style maps in Counter-Strike, and edited a small config that had cvars in it to turn off the freeze time, friendly fire, and some other things. If this config was called deatchmatch.cfg, this is what the entry would look like in the config:
"CStrike Deathmatch" "exec deathmatch.cfg;servercfgfile \'\'" "a" "u"

This menu is accessed in the game by typing amx_cfgmenu in the console. Or by binding a key to that command. The menu will show up on the left side of your screen while playing. It looks like this:
Configs Menu
1. PUBLIC Settings
2. Clanbase
3. Clanbase Charges Only
4. Official CAL Match
5. ProvingGrounds Server Config
6. OGL CS Server Config
7. OGL CS FF Server Config
8. OGL CS Advanced Server Config

0. Exit
1/1

Just select the number of the config you want to be exec'd and that's it. Any changes made to the configs.ini file will show up after the next map change or server restart.

speech.ini - Speech menu

2009-01-26T11:38:00.003+08:00

speech.ini - Speech menu

The speech.ini file in your addons\amx\config folder contains a list of sounds and words that can be run from the Speech menu that the rest of the players can hear. This is enabled by using the amx_speechmenu command. This is what the default speech.ini looks like:
; Menu configuration file
; File location: $moddir/addons/amx/config/speech.ini
; To use with Commands Menu plugin
; NOTE: By default in all settings the access level is set to "u".
; However you can change that, to limit the access to some settings.

; Commands Menu:
; <> <> <> <>
; "a" - execute from server console
; "b" - execute from admin console
; "c" - execute on all clients
; "d" - back to menu when executed

"Hello!" "spk \'vox/hello\'" "cd" "u"
"Don't think so" "spk \'barney/dontguess\'" "cd" "u"
"Don't ask me" "spk \'barney/dontaskme\'" "cd" "u"
"Hey! Stop that!" "spk \'barney/donthurtem\'" "cd" "u"
"Yup" "spk \'barney/yup\'" "cd" "u"
"Nope" "spk \'barney/nope\'" "cd" "u"
"Maybe" "spk \'barney/maybe\'" "cd" "u"
"Seeya" "spk \'barney/seeya\'" "cd" "u"
"Man that sounded bad" "spk \'barney/soundsbad\'" "cd" "u"
"Hello and die" "spk \'vox/hello and die\'" "cd" "u"
"Move!" "spk \'hgrunt/move! _comma yessir!\'" "cd" "u"
"You will definitely pay!" "spk \'hgrunt/c2a2_hg_chat5a\'" "cd" "u"
"Laughter" "spk \'hgrunt/c2a3_hg_laugh\'" "cd" "u"
"Silence!" "spk \'hgrunt/silence!\'" "cd" "u"
"You talk too much" "spk \'barney/youtalkmuch\'" "cd" "u"
"You thinkin?" "spk \'barney/thinking\'" "cd" "u"
"Open fire Gordon!" "spk \'barney/openfire\'" "cd" "u"
"Couldnt make a bigger mess" "spk \'barney/bigmess\'" "cd" "u"
"I have a Bad feeling" "spk \'barney/badfeeling\'" "cd" "u"
"Yes sir!" "spk \'hgrunt/yessir!\'" "cd" "u"
"No sir" "spk \'barney/nosir\'" "cd" "u"

(Note that a semi-colon ; was inserted at the beginning of some lines. This prevents them from being used.)

The speech menu delivers sounds to the clients via WAV file, or the built in VOX speech system. To add some of your own sounds or phrases to the menu, here is an example:
"Fire in the hole!" "spk \'vox/fire in the hole\'" "cd" "u"
"Stop camping!" "spk \'misc/stopcamping.wav\'" "cd" "u"

The "Fire in the hole!" example uses the built in speech engine and sounds a little better than a speak-n-spell. For a full list of words supported, click here. The second example involves uploading a custom .wav file to the client. There are numerous plugins available for doing this, so find one that suites your needs. Just put the sound in the sound\misc folder in your mod folder. In the above example this sound was called "stopcamping.wav". Now from the Speech menu, this sound can be played so the clients can hear it.

This menu is accessed in the game by typing amx_speechmenu in the console. Or by binding a key to that command. The menu will show up on the left side of your screen while playing and looks like this:
AMX Mod Menu
1. Hello!
2. Don't think so
3. Don't ask me
4. Hey! Stop that!
5. Yup
6. Nope
7. Maybe
8. Seeya

9. More...
0. Exit

plugins.ini - Adding more plugins

2009-01-26T11:37:00.003+08:00

plugins.ini - Adding more plugins

The plugins.ini file in your addons\amx\config folder is the list of what plugins are run in your server. See below how to edit this file and add or remove plugins from your server. This is what the default plugins.ini looks like:

; AMX Mod plugins

; To disable any plugin, add a semi-colon ';' to the beginning of its line

; You can disable the Just-In-Time (JIT) compiler with the 'nojit' keyword:
; pluginname.amx nojit
; (read the docs for more details)

; Note: you don't need to declare csstats.amx here (CSStats will load it)

language.amx ; language management
admin.amx ; admin base (required for any admin-related)
;admin_mysql.amx ; admin base - MySQL version (comment admin.amx)
admincmd.amx ; basic admin console commands
adminhelp.amx ; help command for admin console commands
adminslots.amx ; slot reservation
menufront.amx ; front-end for admin menus
cmdmenu.amx ; command menu (speech, settings)
plmenu.amx ; players menu (kick, ban, client cmds.)
restmenu.amx ; restrict weapons menu
mapsmenu.amx ; maps menu (vote, changelevel)
antiflood.amx ; prevent clients from chat-flooding the server
adminchat.amx ; console chat commands
adminvote.amx ; vote commands
nextmap.amx ; displays next map in mapcycle
timeleft.amx ; displays time left on map
mapchooser.amx ; allows to vote for next map
scrollmsg.amx ; displays a scrolling message
imessage.amx ; displays information messages
welcomemsg.amx ; console motd @ client connection
statsx.amx ; stats on death or round end (CSStats Module required!)
stats_logging.amx ; weapons stats logging (CSStats Module required!)
telemenu.amx ; teleport menu (Fun Module required!)
miscstats.amx ; bunch of events announcement for Counter-Strike
pausecfg.amx ; allows to pause and unpause some plugins
statscfg.amx ; allows to manage stats plugins via menu and commands

; Add custom plugins below

About the JIT:

The Just-In-Time compiler has been introduced in AMX 0.9.9. It allows 10+ times faster plugin execution.

For the curious ones that would wonder how it works: your .sma plugins are compiled to .amx files with the sc compiler. The .amx files are Abstract Machine eXecutables: they contain bytecode (instructions that has to be interpreted). Before AMX Mod 0.9.9, the only way to run plugins was to interpret their bytecode constantly, and this was consuming much resources. Now thanks to the JIT, the .amx plugins are compiled at load time to instructions that can be sent directly to the processor, no longer needing the (slow) interpreter. Plugins run faster, and your server will no longer suffer high stress when you declare many.

By default, AMX Mod tries to load plugins with the JIT. You can control this thanks to the amx_usejit localinfo (add +localinfo amx_usejit value to the command launching your server).

There are three possible values for this localinfo:

* never: the JIT will never be used, all plugins will be run the old way
* config (default): the JIT will try to run all your plugins
You can ask AMX not to run the JIT on a specific plugin by adding the nojit keyword right after its line in your plugins.ini file:
myplugin.amx nojit ; This is my plugin, I don't want the JIT for it
* always: AMX will try to run all your plugins with the JIT, ignoring the nojit keywords you could have specified in your plugins.ini

Anyway, if the JIT compiler fails for some reason on a plugin, that one will be executed the old way.

Now there are two ways you can add plugins to your server:
Download pre-compiled plugins:

Then copy the .amx file to your addons\amx\plugins folder and add the line for that plugin to your plugins.ini file. Here are a few reasons this is not the best way:

* The compiled plugin needs to be compiled to your version of AMX or it may not work.
* When you upgrade AMX you should recompile all your plugins anyway.
* You should know how to compile plugins, its very easy and many edits can be made by non programmers such as myself.
* You'll never know if someone decides to be hax0rish and gives you a plugin with malicious code in it.

Download the source and compile it:

(Click here to learn how to compile!)

Then copy the .amx file to your addons\amx\plugins folder and add the line for that plugin to your plugins.ini file. Here are a few reasons this is the best way:

* You can edit the level of access to your choosing.
* Many other people have seen the code and may have offered improvements and can see if the plugin is malicious.
* It lets you learn a little bit more about the overall scheme of how AMX works. And that may come in handy.

Actually doing it:

There are literally hundreds of plugins that can be downloaded and installed into AMX to make it do many things. Here are a couple places to go and get more plugins:

* The official AMX Mod plugins page
* Newly released plugins forum

So go to one of those two links and find a plugin that you must have. It's a good idea at this point just to do one and will be less of a headache this way if you have trouble. Let's say you have a plugin called amx_gag.amx. This is what it would look like if it was in the plugins.ini file.
;; Custom plugs for my server
amx_gag.amx ; admin gag (admins can gag players)

I started a new section for any plugins that I added and left the default plugin section alone. Now to test and see if the plugin you added is installed and running, start up your server. In the servers console type amx plugins. You should get something like this:
Currently loaded plugins:
name version author file status
[ 1] Admin Base 0.9.9 default admin.amx running
[ 2] Admin Commands 0.9.9 default admincmd.amx running
[ 3] Admin Help 0.9.9 tcquest78 adminhelp.amx running
[ 4] Slots Reservation 0.9.9 default adminslots.amx running

(etc, etc. Not all plugins shown)

[ 24] Admin gag 0.6 default amx_gag.amx running
Trouble shooting:

If you see something like bad load under status or unknown under name while doing amx plugins, or [AMX] Plugin file open error (plugin "some_plugin.amx") while your server was starting up then possibly:

* the plugin wasn't copied to the addons\amx\plugins folder
* the name of the plugin doesn't match what you typed in the plugins.ini file.

AMX can also display [AMX] Function not found (name "some_function") (plugin "some_plugin.amx") at startup, then the problem is that the plugin requires a certain AMX Mod module to be loaded.

modules.ini - Adding more modules

2009-01-26T11:36:00.003+08:00

modules.ini - Adding more modules

The modules.ini file in your addons\amx\config folder contains what modules run in your server. Some plugins require more from AMX than it is capable of in it default state. So its core functionality is expanded by adding more modules, which allow plugin authors to do more as well.

Note that as of v0.9.9, AMX doesn't need you anymore to specify your modules path: it will look for them in addons\amx\modules.

This is what the default modules.ini looks like:
; AMX Modules

; NOTE: 'AMX+MM' modules have to be declared in both
; amx/modules.ini and metamod/plugins.ini since
; AMX v0.9.9 (same as 0.9.3, differs from 0.9.7)
; Simple way to identify them: their filename
; contains '_mm'.

; CS Stats
; This one must also be declared in MetaMod's plugins.ini!
csstats_mm.dll
csstats_mm_i586.so

; Fun: more functions for modifications in HL
; This one must also be declared in MetaMod's plugins.ini!
fun_mm.dll
fun_mm_i586.so

; MySQL access
; mysql.dll
; mysql_i586.so

; 3rd party modules

; Vexd Util.
; This one must also be declared in MetaMod's plugins.ini!
; VexdUM_mm.dll
; VexdUM_mm_i586.so

; For DoD compatibility, see this:
; http://djeyl.net/forum/index.php?showtopic=22018

(Note that a semi-colon ; was inserted at the beginning of the original lines. This prevents them from being used without deleting the original lines.)

Modules can be found at these two locations on the AMX site:

* AMX Mod modules
* AMX mod modules forum

(Note that some modules require an entry in the metamod\plugins.ini. Those whose names contain '_mm' do need to be declared to MetaMod, others like MySQL, MThread or GeoIP do not.)

Once your modules are declared, start up your server and type meta list. This lists MetaMod's plugins. You should get something like this:
Currently loaded plugins:
description stat pend file vers src load unlod
[ 1] AMX RUN - amx_mm_i586.so v0.9.9 ini ANY ANY
[ 2] CSStats RUN - csstats_mm_i586. v0.9.9 ini ANY ANY
[ 3] Fun RUN - fun_mm_i586.so v0.9.9 ini ANY ANY
[ 4] VexdUM RUN - VexdUM_mm_i586.s v0.9.9 ini ANY ANY
4 plugins, 4 running

You can also type amx modules to list the modules AMX has loaded. It should look like this:
Currently loaded modules:
name type version author status
[ 1] VexdUM amx&mm 0.9.9 AMX Dev Team running
[ 2] MySQL access amx 0.9.1 dJeyL running
[ 3] Fun amx&mm 0.9.9 OLO running
[ 4] CSStats amx&mm 0.9.9 OLO running
4 modules, 4 correct

Note the 'type' column: modules that contain 'amx&mm' have to be declared in MetaMod's plugins.ini. Others (MySQL in this example) don't.
Tip:

Module downloads may include files with the .inc extension. It's important that these files get in to the addons\amx\examples\include folder. As you compile plugins that use these modules, the .inc file(s) that came with the modules are required for the plugins that use them to compile.

maps.ini - Adding more maps to the maps menu

2009-01-26T11:34:00.002+08:00

maps.ini - Adding more maps to the maps menu

The maps.ini file in your addons\amx\config folder contains a list of maps that can be chosen from the Changelevel Menu using the amx_mapmenu command. This is what the default maps.ini looks like:

; Maps configuration file
; File location: $moddir/addons/amx/config/maps.ini
; To use with Maps Menu plugin

as_oilrig "OilRig - Assassination"
as_tundra "Tundra - Assassination"
de_aztec "Aztec - Bomb/Defuse"
de_cbble "Cobble - Bomb/Defuse"
de_chateau "Chateau - Bomb/Defuse"
de_dust "Dust - Bomb/Defuse"
de_dust2 "Dust II - Bomb/Defuse"
de_inferno "Inferno - Bomb/Defuse"
de_nuke "Nuke - Bomb/Defuse"
de_prodigy "Prodigy - Bomb/Defuse"
de_storm "Storm - Bomb/Defuse"
de_survivor "Survivor - Bomb/Defuse"
de_train "Trainyard - Bomb/Defuse"
de_torn "Torn - Bomb/Defuse"
de_vegas "Vegas - Bomb/Defuse"
de_vertigo "Vertigo - Bomb/Defuse"
cs_747 "747 Hijack - Hostage Rescue"
cs_assault "Assault - Hostage Rescue"
cs_backalley "Alleyway - Hostage Rescue"
cs_estate "Zaphod's Estate - Hostage Rescue"
cs_havana "Havana - Hostage Rescue"
cs_italy "Italy - Hostage Rescue"
cs_militia "Militia - Hostage Rescue"
cs_office "The Office Complex - Hostage Rescue"
cs_siege "Canyon Siege - Hostage Rescue"

(Note that a semi-colon ; was inserted at the beginning of some lines. This prevents them from being used.)

Adding maps to the menu for use is very simple and should be entered just as other maps are in this file. The map name first with out the .bsp extension. Then the name of the map and a brief description of what type it is "in quotes". So if you wanted to add the map fy_snow.bsp to your maps.ini file it would look like this:

fy_snow "Snow - Team Deathmatch"

Removing maps is as simple as removing the line from this file that represents the map, or by inserting a semi-colon at the beginning of the line causing it to be ignored.

This menu is accessed in the game by typing amx_mapmenu in the console. Or by binding a key to that command. The menu will show up on the left side of your screen while playing. It looks something like this:

Changelevel Menu

1. Havana - Hostage Rescue
2. Italy - Hostage Rescue
3. Dust II - Bomb/Defuse
4. Militia - Hostage Rescue
5. Cobble - Bomb/Defuse
6. Snow - Team Deathmatch
7. Mindmaze - Team Deathmatch
8. Assault - Hostage Rescue

9. More...
0. Exit

1/2

Just select the number in front of the map to change it and that's it! If you have more than eight maps, option 9. will show you them. Option 0. takes you to the previous menu.

Any changes made to the maps.ini file will show up after the next map change.

cvars.ini - Cvars menu

2009-01-26T11:33:00.003+08:00

cvars.ini - Cvars menu

The cvars.ini file in your addons\amx\config folder contains a list of variables that may be run from the Cvars Menu. This is enabled by using the amx_cvarmenu command. This is what the default cvars.ini looks like:

; Menu configuration file
; File location: $moddir/addons/amx/config/cvars.ini
; To use with Commands Menu plugin

; Cvars Menu:
; <> <> ... <>

"mp_timelimit" "0" "30" "45" "u"
"mp_friendlyfire" "0" "1" "u"
"mp_autoteambalance" "0" "1" "2" "u"
"sv_password" "" roxor "clanwar" "u"
"mp_limitteams" "0" "1" "2" "u"
"mp_freezetime" 0 "6" "u"
"mp_buytime" "1" "0.5" "u"
"mp_startmoney" "800" "1800" "3600" "u"
"mp_c4timer" "35" "45" "15" "u"
"mp_forcechasecam" "0" "1" "2" "u"
"pausable" 0 1 "u"
"sv_minrate" "2000" "3000" "u"
"sv_maxrate" "7000" "6500" "u"
"allow_spectators" "0" "1" "u"
"sv_voiceenable" "0" "1" "u"
"mp_logmessages" "0" "1" "u"

(Note that a semi-colon ; was inserted at the beginning of some lines. This prevents them from being used.)

Adding commands to the menu for use should be entered as other commands are shown in this file.

This menu is accessed in the game by typing amx_cvarmenu in the console. Or by binding a key to that command. The menu will show up on the left side of your screen while playing. It looks like this:

Cvars Menu

1. mp_timelimit
2. mp_friendlyfire
3. mp_autoteambalance
4. sv_password
5. mp_limitteams
6. mp_freezetime
7. mp_buytime
8. mp_startmoney

9. More...
0. Exit

1/2

20
0
1

2
6
1.5
800

Just select the number representing the cvar (variable) you want to change and when you press 0. to exit the change is made. For menu items that have multiple options, continue to press the number for that cvar until you see the setting you want, then 0. to exit. Any changes made to the cvars.ini file will show up after the next map change or server restart.

cmds.ini - Commands menu

2009-01-26T11:31:00.003+08:00

cmds.ini - Commands menu

The cmds.ini file in your addons\amx\config folder contains a list of commands that may be run from the Commands Menu. This is enabled by using the amx_cmdmenu command. This is what the default cmds.ini looks like:

; Menu configuration file
; File location: $moddir/addons/amx/config/cmds.ini
; To use with Commands Menu plugin

; NOTE: By default in all settings the access level is set to "u".
; However you can change that, to limit the access to some settings.

; Commands Menu:
; <> <> <> <>
; "a" - execute from server console
; "b" - execute from admin console
; "c" - execute on all clients
; "d" - back to menu when executed

"Pause" "amx_pause" "ad" "u"
" " "-" "" "u"
"Restart Round" "sv_restartround 1" "a" "u"

(Note that a semi-colon ; was inserted at the beginning of some lines. This prevents them from being used.)

Adding commands to the menu for use should be entered as other commands are shown in this file. The entry just below the "Pause" is for a space separator in the menu (see below). The difference between flags a and b is some commands may only work from the servers console and not the clients. Non AMX commands like "restart" for restarting map is a command that must be run from the server console.

Here are some examples of how to add a vote command to the menu for Dust2, and a command for restarting the current map:

"Restart Map" "restart" "a" "u"
"Vote Dust2" "amx_votemap de_dust2" "a" "u"

This menu is accessed in the game by typing amx_cmdmenu in the console. Or by binding a key to that command. The menu will show up on the left side of your screen while playing. It looks like this with the added commands from above:

Commands Menu

1. Pause

2. Restart Round
3. Restart Map
4. Vote Dust2

9. More
0. Exit

1/1

Just select the number of the command you want to run and that's it. Any changes made to the cmds.ini file will show up after the next map change or server restart.

clcmds.ini - Client Cmds Menu

2009-01-26T11:26:00.002+08:00

clcmds.ini - Client Cmds Menu

The clcmds.ini file in your addons\amx\config folder contains a list of commands to be performed on a client that can be chosen from the Client Cmds Menu. This is enabled by using the amx_clcmdmenu command. This is what the default clcmds.ini looks like:
; Client commands configuration file
; File location: $moddir/addons/amx/config/clcmds.ini
; To use with Players Menu plugin

; NOTE: By default in all settings the access level is set to "u".
; However you can change that, to limit the access to some settings.

; Client Commands Menu:
; <> <> <> <>
; "a" - execute from server console
; "b" - execute from admin console
; "c" - execute on selected player
; "d" - back to menu when executed

"Kick player" "amx_kick #%userid%" "b" "u"
"Slay player" "amx_slay #%userid%" "bd" "u"
"Slap with 1 dmg." "amx_slap #%userid% 1" "b" "u"
"Ban on 5 minutes" "amx_ban #%userid% 5" "b" "u"

(Note that a semi-colon ; was inserted at the beginning of some lines. This prevents them from being used.)

Adding commands to the menu for use should be entered as other commands shown in this file. Some commands require additional input when using like the amx_banip command. This command needs to know an amount of time to perform its task. You will notice in the menu the number 5 at the end of the command. This is the same way you would enter it in the console. The difference between flags a and b is some commands may only work from the server's console and not the client's.

If you wanted to add a 3rd party plugin like amx_rocket to the menu, and you wanted the menu to disappear after the command was run it would look like this:
"Make player a rocket" "amx_rocket #%userid%" "b" "u"

This menu is accessed in the game by typing amx_clcmdmenu in the console. Or by binding a key to that command. The menu will show up on the left side of your screen while playing. It looks like this:
Client Cmds Menu
1. RYNO SKIN
2. m0gely
3. Mr.Magoo
4. : ) Gurl
5. SMAN
6. GrEeN ToMaTo
7. *Groovy*Chicka

8. Kick Player

9. More
0. Exit
1/2

Options 1. through 7. will display player names. If you select one of these numbers, what ever punishment is shown at number 8. is what's going to happen to them. By pressing 8., you will cycle through the list of commands specified in the clcmds.ini file. If you have more than seven players, option 9. will show you them. Option 0. takes you to the previous list of players.

You may notice in the menu some player names are a slightly darker color or grayed out. This indicates a player who has immunity. If the plugin is immunity aware then you will not be able to perform it on them.

Any changes made to the clcmds.ini file will show up after the next map change or server restart.

mysql.cfg - Using MySQL to store settings

2009-01-26T11:24:00.003+08:00

mysql.cfg - Using MySQL to store settings

The mysql.cfg file in your addons\amx\config folder stores the information AMX needs to connect to a MySQL database. This is what the default mysql.cfg file looks like:
// MySQL access configuration file
// File location: $moddir/addons/amx/config/mysql.cfg

// *NOTE* Linux users may encounter problems if they specify "localhost"
// instead of "127.0.0.1"
// We recommend using your server IP address instead of its name

amx_mysql_host "127.0.0.1"
amx_mysql_user "root"
amx_mysql_pass ""
amx_mysql_db "amx"

Then you will have to create your table with the same fields as in usual users.ini: auth, password, access and flags, all as VARCHAR(32) fields. Of course you can tweak this all if you feel like you can modify the admin_mysql.sma plugin source.

Anyhow we recommend using phpMyAdmin, which is a great MySQL database administration tool written in PHP.

amx.cfg - The main config

2009-01-26T11:23:00.003+08:00

amx.cfg - The main config

The amx.cfg file in your addons\amx\config folder is where most of the settings are made for AMX. This file is executed every map change. So if you make a change to this file, it's not necessary to restart the server unless the change is needed immediately.

All the settings in this file have comments describing what that setting does, and the different values that can be used. Below you will find additional help for the amx.cfg file