How To Create CS1.6 Online Private Dedicated Server counter strike 1.6 server counter strike 1.6 serial counter strike download counter strike wallhack counter strike aimbot counter strike download counter strike bots cs 1.6 bot cs 1.6 bots free counter strike download counter strike non steam cs 1.6 counter strike 1.5 download free counter strike counter strike game download counter strike server counter strike v1 6 How To Create CS1.6 Online Private Dedicated Server: cs 1.6 bots
Showing posts with label cs 1.6 bots. Show all posts
Showing posts with label cs 1.6 bots. Show all posts

Monday, January 26, 2009

users.ini - Setting up admins

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

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

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

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

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

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

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

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

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

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

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

amx_default_access

Valid Settings:
Example:
Description:
a through u
amx_default_access "j"
This is what access any player would have when joining your server. Be careful what you do with this. If you wanted to allow voting, you would assign this value the letter j as shown in the example.

amx_password_field

Valid Settings:
Example:
Description:
Anything
amx_password_field "_pw"
This password field needs to match on the server and the client. It can be what ever you want, but it must match. If you use the default shown above, then the clients should have setinfo _pw "password" set in their userconfig.cfg file in their cstrike folder. For more info on how to set a client up as an admin using password go here.

amx_mode

Valid Settings:
Example:
Description:
0, 1 or 2
amx_mode "1"
0 Disables admin access all together. AMX runs, but no one will have admin access even if they are set up to. 1 is normal operation for AMX. 2 will kick anyone not in the users.ini file. This is in effect the same as a private server.

amx_show_activity

Valid Settings:
Example:
Description:
0, 1 or 2
amx_show_activity "2"
This will cause AMX to make public some AMX functions as they happen in game (amx_show_activity "1"), and also the admin who is running the command if desired ("2"). This may be helpful in keeping admins accountable, but it also reveals who an admin is.

amx_scrollmsg

Valid Settings:
Example:
Description:
Any message.
amx_scrollmsg "Welcome fraggers! You're on %hostname%" 600
This message appears in the lower center of the screen and scrolls by at a specified interval. The number at the end is the interval in seconds, so 600 seconds would make the message appear every 10 minutes. Make sure to use quotes around your message. If you use %hostname% it will be replaced with your server's hostname.

amx_imessage

Valid Settings:
Example:
Description:
Any message.
amx_imessage "Welcome to %hostname%!" "000100255"
This message appears in the center of the screen. The number at the end is the the color you want the message to appear in. Use this web applet to get the numeric value of the RGB color you want to use. Make sure to use quotes around your message. %hostname% will be replaced with your server's hostname. You can specify several amx_imessage lines: the messages will cycle.

amx_freq_imessage

Valid Settings:
Example:
Description:
Length of time in seconds.
amx_freq_imessage "180"
Setting this to 180 would cause the amx_imessage to display every 3 minutes.

amx_flood_time

Valid Settings:
Example:
Description:
Length of time in seconds.
amx_flood_time "0.75"
Setting this to 0.75 means players can't use the say command more than once every 3/4's of a second. This helps to prevent people from flooding the server with unwanted chat.

amx_reservation

Valid Settings:
Example:
Description:
1~32
amx_reservation "1"
The value this is set to will be the amount of slots set aside for people with that access.

amx_time_display

Valid Settings:
Example:
Description:
See amx.cfg file.
See amx.cfg file.
This controls the text reminder at the bottom of the screen that tells you how many minutes are remaining on the current map. The amx.cfg has the best description for this. Most people will probably leave this its default setting.

amx_time_voice

Valid Settings:
Example:
Description:
0 or 1
amx_time_voice "1"
When a player uses the say command /thetime or /timeleft, this information is printed in the chat area. This setting will cause a voice to say what time it is as well when set to 1.

amx_vote_delay

Valid Settings:
Example:
Description:
Length of time in seconds.
amx_vote_delay "30"
This is the time in seconds before another vote is allowed.

amx_vote_time

Valid Settings:
Example:
Description:
Length of time in seconds.
amx_vote_time "20"
Time in seconds a vote will stay up for voting.

amx_vote_answers

Valid Settings:
Example:
Description:
0 or 1
amx_vote_answers "1"
Setting this to 1 causes what people voted to be known to everyone.

amx_votekick_ratio

Valid Settings:
Example:
Description:
0.00 to 1.00
amx_votekick_ratio "0.60"
Vote ratios work like this: 0.10 = 10%, 0.50 = 50%, 1.00 = 100%. You get the idea. This is the percentage required for a kick vote to go through. Consider carefully what you set this to, or the minority of players on your server will have decision making abilities if you allow voting.

amx_voteban_ratio

Valid Settings:
Example:
Description:
0.00 to 1.00
amx_voteban_ratio "0.60"
Vote ratios work like this: 0.10 = 10%, 0.50 = 50%, 1.00 = 100%. You get the idea. This is the percentage required for a ban vote to go through. Consider carefully what you set this to, or the minority of players on your server will have decision making abilities if you allow voting.

amx_votemap_ratio

Valid Settings:
Example:
Description:
0.00 to 1.00
amx_votemap_ratio "0.60"
Vote ratios work like this: 0.10 = 10%, 0.50 = 50%, 1.00 = 100%. You get the idea. This is the percentage required for a map vote to go through. Consider carefully what you set this to, or the minority of players on your server will have decision making abilities if you allow voting.

amx_vote_ratio

Valid Settings:
Example:
Description:
0.00 to 1.00
amx_vote_ratio "0.60"
Vote ratios work like this: 0.10 = 10%, 0.50 = 50%, 1.00 = 100%. You get the idea. This is the percentage required for a vote to go through. Consider carefully what you set this to, or the minority of players on your server will have decision making abilities if you allow voting.

amx_extendmap_max

Valid Settings:
Example:
Description:
Multiple of amx_extendmap_step in minutes.
amx_extendmap_max "30"
This is the max amount of time in minutes a mapcycle can be extended. Make this an even multiple of the amx_extend_step setting. Setting this to 30, would allow the map to be extended two times if the amx_extendmap_step is set to 15.

amx_extendmap_step

Valid Settings:
Example:
Description:
Length of time in minutes.
amx_extendmap_step "15"
Time in minutes that a mapcycle will be extended if vote to do so succeeds.

Step 3: Setting up AMX Mod

Step 3: Setting up AMX Mod

Now that AMX Mod is installed and running, you need to do at least one more thing to start using it. You need to make yourself an admin. This can be accomplished through the users.ini file. To understand how that and the other AMX config files work, use the menu on the left and click on each file for detailed information.

Below is a brief description of what each file is for. They are all located in addons\amx\config.

amx.cfg
Primary AMX Mod configuration file.

mysql.cfg
Configuration file for storing AMX settings in a MySQL database.

clcmds.ini
Admin commands to perform on other players via Command menu.

cmds.ini
Add/Edit commands to the Commands menu with this file.

configs.ini
Execute configs through Command menu.

cvars.ini
Define what cvars can be changed in Cvars menu.

maps.ini
Add/Remove maps from Maps and Maps vote menu.

modules.ini
Add more modules to AMX to expand functionality.

speech.ini
Say things from the Speech menu.

users.ini
Use this file to grant admin access to a player.

plugins.ini
Use this file to add more plugins to AMX.

stats.ini
Used by AMX to store in-game stats settings.
File is modified when stats setting are saved using the Stats Menu or the amx_statscfg command.

language.ini
Used by AMX to store the server language.
File is modified when the server language is saved using the Language Menu or the amx_language command.

weaprest.ini
Used by AMX to store weapon restriction settings.
File is modified when restrictions are set using the Restriction Menu or the amx_restrict command.

Step 2: Installing AMX Mod

Step 2: Installing AMX Mod

At the time of this writing, version 0.9.9 is the current stable release and is what is listed on the AMX front page.

A. Download AMX and uncompress the file into your mod folder. You already have addons\metamod, and after uncompressing the AMX Mod file you downloaded, you will have addons\amx also. Here are all the folders you should have:
C:\HLServer
└ mod (ie. cstrike, tfc, dod)
└ addons
├ metamod
│ └ dlls
└ amx
├ config
├ dlls
├ examples
│ ├ include
│ └ source
│ └ default
├ logs
├ modules
└ plugins

B. Now that AMX is where it needs to be, we need to tell MetaMod to run it. Go to your addons\metamod folder. If you just installed MetaMod you will need to create the plugins.ini file. For Windows users the best method is to right-click in the MetaMod folder, choose New then Text Document. Now name it plugins.ini.

You can also take the provided sample_plugins.ini that comes within the AMX package and rename it to plugins.ini.

Once you complete that or if the plugins.ini file is already there, open it in a text editor and add the following lines:
win32 addons\amx\dlls\amx_mm.dll
linux addons/amx/dlls/amx_mm_i586.so

Note: You can have both lines listed above in the plugins.ini file, but both are not required. If you are a Windows user, then the Linux line is ignored and vice versa.

You might also want to declare some AMX modules you want to use (only those whose name contains '_mm' -- other ones like MySQL do not need to be declared to MetaMod):
win32 addons\amx\modules\csstats_mm.dll
linux addons/amx/modules/csstats_mm_i586.so

C. Start up your server. At the server console, type meta list. You should see something like this:
Currently loaded plugins:
description stat pend file vers src load unlod
[ 1] AMX RUN - amx_mm.dll v0.9.9 ini ANY ANY
[ 2] CSStats RUN - csstats_mm.dll v0.9.9 cmd ANY ANY
[ 3] FUN RUN - fun_mm.dll v0.9.9 cmd ANY ANY
3 plugins, 3 running

If you do, then you have successfully installed AMX Mod! For the official instructions on how to install AMX, refer to the readme.txt file included with the download. Now you have AMX installed and running. In Step 3, we will go through how to configure AMX.

Step 1: Installing MetaMod (Steam based servers)

Step 1: Installing MetaMod (Steam based servers)

Step 1: Installing MetaMod

MetaMod is a replacement DLL for the game you run. This modified DLL replaces the stock version and allows for external plug-ins (such as AMX) to interface with the game. This step may be skipped if you already have MetaMod installed.

Version 1.17.1 is the current at the time this document was made. Also note that it's shipped within the AMX 0.9.9 package: if you plan to use this one, just go to step C.

A. Download MetaMod for the operating system you use: Windows | Linux

B. Make the following folders in your mod folder (ie. cstrike, tfc, etc.):
C:\HLServer (your path may vary)
└ mod (ie. cstrike, tfc, dod)
└ addons
└ metamod
└ dlls

C. Uncompress the fileFor windows:
metamod.dll

For linux:
metamod_i386.so you downloaded and put it in the addons\metamod\dlls folder you just made.

D. Enabling MetaMod on Steam based servers: (Click here for WON instructions)

MetaMod can be enabled by adding a command line switch to your server's shortcut or startup script. The old method done by editing the liblist.gam file should only be used on a WON based server. Steam servers often update that file with default values which disable MetaMod. The -dll switch is how it has to be done. Choose your type of server from below and follow the instructions:

* "Windows Listen Servers": Right-click on your game (ie. Counter-Strike) from the Games menu in Steam and choose Properties. Then choose Launch options. Now just add -dll addons\metamod\dlls\metamod.dll to the space provided and choose OK.
* "Windows Dedicated Servers from the Games menu in Steam": Right-click on Dedicated Server choose Properties. Then choose Launch options. Now just add -dll addons\metamod\dlls\metamod.dll to the space provided and choose OK.
* "Windows Dedicated Servers not from Steam menu (also WON servers)": Right-click on the shortcut for your server and choose Properties. From the Shortcut tab find the Target field. At the end of that line, add -dll addons\metamod\dlls\metamod.dll and choose OK.
* "Linux Dedicated Servers" Edit the script you use to start up your server and add -dll addons/metamod/dlls/metamod_i386.so to the end of the line. Save and exit.

D. Enabling MetaMod on WON based servers: (Click here for Steam instructions)

For WON servers, find the file called liblist.gam in your mod folder (ie. cstrike) and open it up in a text editor. Find the lines:
gamedll "dlls\mp.dll"
gamedll_linux "dlls/cs_i386.so"

And change them to this:
;gamedll "dlls\mp.dll"
gamedll "addons\metamod\dlls\metamod.dll"
;gamedll_linux "dlls/cs_i386.so"
gamedll_linux "addons/metamod/dlls/metamod_i386.so"

(Note: A semi-colon ; was inserted at the beginning of the original lines. This prevents them from being used without deleting the original lines. Also you can have both lines listed above in the liblist.gam file, but both are not required. If you are a Windows user, then the Linux line is ignored and vice vera.)

E.Now, start up your server. To find out if MetaMod is running, type meta version on the server console and press enter. You should get something that looks like this:
Metamod v1.17.1 2004/05/30
by Will Day
http://www.metamod.org/
compiled: Jun 4 2004, 00:39:34 CEST (optimized)

If you do, then you have successfully installed MetaMod! For the official instructions on how to install MetaMod, go here. Now move on to Step 2 and lets install AMX next.

Step 1: Installing MetaMod

Step 1: Installing MetaMod

(WON based servers)

MetaMod is a replacement DLL for the game you run. This modified DLL replaces the stock version and allows for external plug-ins (such as AMX) to interface with the game. This step may be skipped if you already have MetaMod installed.

Version 1.17.1 is the current at the time this document was made. Also note that it's shipped within the AMX 0.9.9 package: if you plan to use this one, just go to step C.

A. Download MetaMod for the operating system you use: Windows | Linux

B. Make the following folders in your mod folder (ie. cstrike, tfc, etc.):
C:\HLServer (your path may vary)
└ mod (ie. cstrike, tfc, dod)
└ addons
└ metamod
└ dlls

C. Uncompress the fileFor windows:
metamod.dll

For linux:
metamod_i386.so you downloaded and put it in the addons\metamod\dlls folder you just made.

D. Enabling MetaMod on Steam based servers:

MetaMod can be enabled by adding a command line switch to your server's shortcut or startup script. The old method done by editing the liblist.gam file should only be used on a WON based server. Steam servers often update that file with default values which disable MetaMod. The -dll switch is how it has to be done. Choose your type of server from below and follow the instructions:

* "Windows Listen Servers": Right-click on your game (ie. Counter-Strike) from the Games menu in Steam and choose Properties. Then choose Launch options. Now just add -dll addons\metamod\dlls\metamod.dll to the space provided and choose OK.
* "Windows Dedicated Servers from the Games menu in Steam": Right-click on Dedicated Server choose Properties. Then choose Launch options. Now just add -dll addons\metamod\dlls\metamod.dll to the space provided and choose OK.
* "Windows Dedicated Servers not from Steam menu (also WON servers)": Right-click on the shortcut for your server and choose Properties. From the Shortcut tab find the Target field. At the end of that line, add -dll addons\metamod\dlls\metamod.dll and choose OK.
* "Linux Dedicated Servers" Edit the script you use to start up your server and add -dll addons/metamod/dlls/metamod_i386.so to the end of the line. Save and exit.

D. Enabling MetaMod on WON based servers: (Click here for Steam instructions)

For WON servers, find the file called liblist.gam in your mod folder (ie. cstrike) and open it up in a text editor. Find the lines:
gamedll "dlls\mp.dll"
gamedll_linux "dlls/cs_i386.so"

And change them to this:
;gamedll "dlls\mp.dll"
gamedll "addons\metamod\dlls\metamod.dll"
;gamedll_linux "dlls/cs_i386.so"
gamedll_linux "addons/metamod/dlls/metamod_i386.so"

(Note: A semi-colon ; was inserted at the beginning of the original lines. This prevents them from being used without deleting the original lines. Also you can have both lines listed above in the liblist.gam file, but both are not required. If you are a Windows user, then the Linux line is ignored and vice vera.)

E.Now, start up your server. To find out if MetaMod is running, type meta version on the server console and press enter. You should get something that looks like this:
Metamod v1.17.1 2004/05/30
by Will Day
http://www.metamod.org/
compiled: Jun 4 2004, 00:39:34 CEST (optimized)

If you do, then you have successfully installed MetaMod! For the official instructions on how to install MetaMod, go here. Now move on to Step 2 and lets install AMX next.

AMX Mod Setup Guide (Read Me)

AMX Mod Setup Guide (Read Me)

This document expects you are already familiar with installing and setting up a Half-Life server and the Mod you wish to run. For the purposes of the examples here, Windows drive letters and slashes will be used. The paths may be different than how your server is setup, so that much you will have to figure out.

Installing MetaMod and AMX is a fairly simple. If you find any errors in this document, please feel free to let us know. If you need further help, try out the AMX Mod forums and please take a couple minutes to use the search feature first. There is a good chance your question has already been asked and answered.

AMX is a MetaMod plugin. Basically MetaMod is a DLL that replaces the game DLL of the server. MetaMod allows plugins to interface with it. AMX is one of those plugins. Other plugins such as HLGuard (anticheat), AdminMod (like AMX), StatsMe (in game stats but built in to AMX), etc. are also MetaMod plugins.

So on to Step 1!

Friday, January 16, 2009

weapons in Counter-Strike

How important is it to know your weapons in Counter-Strike? Very.

If you're a regular in the CS scene then you'll know that a game of CS can come up with many different scenarios and situations that you need to deal with pretty rapidly. Knowing the strengths and weaknesses of the various types of weaponry that appear in CS will keep you on level playing terms with your opponent, if not better.

The following is a guide to each weapon in the game as well as a little info about the pros and cons of each. It's written purely by my experience (vast, honest!), so if you are expecting scientific terms and research, this won't be it. However, if you're looking for advice on choosing a weapon this is the place to get some.

If you're an experienced player then you'll no doubt have your own opinion and may disagree with some of what appears below (surely not it all!), but if you're new to the game then read on and when you start your next game of CS you'll be a new man. Well...not really, but it might help!


Melee & Pistols

Knife

Obviously, the knife is never a serious option to go into battle with. But nevertheless, it can come in handy when you least expect it...right in the heat of battle. If you and your opponent get into some close quarters battle (and you both need aiming lessons), you may occasionally find that both your primary gun and your pistol clips emtpy, leaving you two options...reload or knife!

Reloading can often be very time consuming in those situations and it can often pay off to whip out the knife and slash away. Do, however, make sure that you are in range because if not your opponent will just keep backing off whilst he reloads, game over.

USP .45

This is the pistol that the CTs start the round with automatically, and it's widely regarded as the best pistol available, even above the Desert Eagle in some people's eyes (mine included). This is a pretty accurate gun on the whole, and can also pack a punch when you aim it well. One or two shots to the head and your opponent won't have much of a chance. The secondary function for this gun is a silencer which can come in very handy.

If you start the game as CT I'd recommend keeping this gun, buying more ammo for it and buying a kevlar vest...that should stnad you in good stead for the all important first round.

Glock18

This is the default T pistol for the Terrorists, and they could do worse than ditch it for a USP or a Desert Eagle. This is what puts the Ts at a bit of a disadvantage at the start of a match. It's a pretty weak gun and although it does have a big clip (20) for you to play with, it just won't cut it in a pistol fight generally. Secondary fire for the glock is semi-auto mode, which fires 3 bullets at once.

My advice (yes, again) if you spawn with this pistol would be to ditch it and buy a Desert Eagle or a USP .45 and some ammo...if your CT opponents are decent players, you won't have a chance against their usp and armor with that Glock of yours.

Desert Eagle

The most powerful pistol in the game, this gun is normally the option that most people who buy a pistol in the first round go for (to replace the Glock18?). It's the only pistol that is able to penetrate walls, crates, doors and the like. It also has pretty good accuracy, the only downfall being the 7 bullet clip, which doesn't last long at all. Hand Cannon, to sum it up.

With good accuracy this gun should get you far, but if you can't aim then 7 bullets won't last long and it'll take what seems an eternity to reload. A good alternative to a cheap sub-machine gun in the later rounds, if you're saving money for a rifle.

Sig P228

This is the least used pistol in the game, but probably only because players would rather buy a DE, or stick with their default gun. It's quite a powerful gun, and along with the 13 bullet clip, it can be put to very good use in the right hands. If your opponent is using a DE and reach a point where they need to reload, that's when you have a great opportunity to come out on top in the duel...6 bullets more than him and not exactly with a pea-shooter either.

Pretty decent accuracy, but then again, none of the pistols are too bad in that department...oh wait, spoke too soon.

Dual Beretta Elites

These are by far the most innacurate pistols available and I can't really justify spending $1000 on them. Each gun holds 15 bullets in the clip, meaning 30 total which is handy, but I guess you'll need it when these guns are as weak as they are. It'll take a good few shots to take out your opponent, unless you're lucky/good and land headshots.

But still, it's nice running about with akimbo pistols so I recommend trying them at least once! They look cool and it feels good, until you get involved in a battle, then you'll remember why you always buy USP/DE. Terrorist Only.

Five Seven

Another decent pistol for the CTs, this time in the shape of the 20 round clip of the 5-7. It isn't as strong as some pistols but it's not weak either, and in terms of accuracy it's very good.

CT only, and again an under-used pistol, I suspect because of the better alternatives. Since it was added into the game I've seen mixed responses about this gun, but in my opinion it's a decent sidearm. You could do worse than buy one of these when you are sniping...the 20 bullet clip will buy you some time to back off and get in a better sniping position if any enemies are attacking.


Shotguns

M3 Super

This is the cheapest of the two shotguns available, and deservedly so. If you're intent on being top of the score boards this just isn't the gun to do it with...it's got a pretty slow reload and rate of fire meaning that if the action is coming thick and fast, you probably won't last with only 8 rounds in the clip.

It's a fairly powerful gun, though, and can be useful in close quarters battle (CQB), but not as useful as it's counterpart, the XM1014. It's obviously pretty accurate, as you'd expect with a slow rate of fire, within a certain range of course.

XM1014

If you want a shotgun, this is the one to go for....if you have the $3000 to spare. It only has a 7 round clip which empties very fast, so you'll have to be a dab hand with it but other than that it's a very good gun. Again, it's quite powerful but this time the rate of fire is more sufficient when you need to clear out an enclosed space. This is a good gun for any small, enclosed maps but it's not to be used over any great distance, obviously.

What's also quite handy is that you can still fire whilst reloading, as with the m3 super, meaning that you'll still have some sort of cover (albeit slower firing rate as you reload) until you can find cover to reload fully.


Sub-Machine Guns

MP5

This is the most commonly used of all sub-machine guns by far, and probably the most used gun in the game. It's a very reliable gun with good accuracy and power. If you can aim well then the MP5 will be a good gun for you, if you can't use the mp5....well...learn!

Even when things aren't going so well you can usually afford an MP5 and that's what's great about it, you'll always have the mp5 as a way of digging you and your team out of a hole. It has a 30 round clip which is enough to carry you through most fire fights, aim at the head and it shouldnt be too difficult to get a couple of kills per clip (of course, that's if you're good at avoiding death primarily). It's also decent for mid-range battles.

TMP

This is like the sub-machine gun version of the glock 18; it has a good rate of fire but is very weak, the weakest of all SMGs infact. Again the clip size is 30, but that doesn't help much either when you look at the accuracy of this gun. It's very shoddy and the recoil for such a small gun is terrible.

Sometimes due to money restrictions, you can't afford an MP5 and are left with this gun, but I think even then you're best of buying a Desert Eagle and hoping you can pick up a gun along the way, that way you'll be saving some money for the next round too. One good point is that it's silenced so if you're skilled enough you can sneak up behind an opponent, dispose of him and steal his AK47.....this gun is CT only.

P90

A decent SMG, this used to be the most used gun in the game...until the CS team toned it down a bit because it was being over used. It was extremely accurate and powerful making it extremely easy to use. Now, however, it takes alot more skill to use the P90 as it's less powerful and much less accurate than before. Probably best used in close quarters battle this gun has a very nice rate of fire, and a massive 50 bullet clip, meaning you'll still be firing away while an opponent reloads his MP5.

I'm unconvinced about the accuracy of this gun...at times it can seem ok, but most of the time I use it, I don't get very far which is no good if I've just spent over $2300 for it.

Mac 10

This is yet another gun that doesn't get used very often in CS, in comparison with other guns. It's ok in the rate of fire department, and holds up in the power area, but accuracy is where it falls down....badly! The accuracy on this gun makes it worth saving the money for the next round, death is imminent regardless.

It's not that bad really I suppose, I just felt like dramatising hehe. This gun is ok if you are rushing, your opponents dont expect you, and you can get quick headshots in CQB. Other than that, give it a miss and if you do buy it, pick up the first alternative gun you see....unless it's a TMP but even then it's a tough call.

UMP

This gun has a slow rate of fire and only 25 rounds per clip, meaning that some people tend to steer clear of it where possible. It does, however, pack in some nice accuracy and a fair amount of power...in the right hands, this can be a very decent gun.

Probably best in mid-ranges, rather than CQB though, because of it's accuracy and slow rate of firing. If you do end up in an enclosed space then you won't last that long before you need to reload, which also takes quite long so try to avoid that scenario. Not a bad gun at all for the $1700 you'll pay.


Assault Rifles

AK47

Here we have one of the most popular guns around, people either love it or hate it, but the great majority tend to react favourably when you bring up the topic of the AK. It is the least expensive rifle in the game at only $2500 definitely a bargain, especially when you consider that it's the most powerful assault rifle as well as having 30 bullets in the clip.

So why so cheap? well, I didn't mention the recoil yet....on full auto this gun is about as inaccurate as they come. Only upon mastering how to use this gun will you appreciate how good it is. In close quarters battle it is superb, it's powerful, good rate of fire and on full auto you can empty a small space very quickly. For me though range is where the AK47 excels, if you use burst firing. This gun can be used as a sniper rifle but without the scope, that's how good it is from distance. Two or three accurate shots from this gun across a mid to long range distance will hurt an opponent pretty badly, stop, let the crosshair recover, and fire two or three more and he'll be dead....often he'll be dead before you even get to fire the last few bullets. Learn to handle the recoil and you'll love this gun. T Only.

SG552 Commando

Much like the AK47, this gun is good in both CQB and long range scenarios, but it tends to be a lot more accurate when using burst fire obviously. It is less powerful than the AK but comes with a built in scope to assist you in long range fights. When you're zoomed in the rate of fire does drop noticably but accuracy is helped which is what you want from range.

A lot less effort is required to learn how to use this gun than the ak, again because of the recoil issues, overall a good gun....Terrorists should feel safe with this 30 round gun in their hands. It's more expensive than the AK47, but that doesn't necessarily mean it's a better gun, maybe it's just easier to handle. T Only.

Colt M4A1

The favourite gun of the CT masses, the colt is a great gun and is more often than not likely to be compared with the AK rather than the Commando. It's the cheapest of the two CT assault rifles and represents more value for money than it's CT counterpart, the Aug. It has a 30 round clip and is also pretty darn powerful.

The accuracy on the colt can be quite wayward on full spray, so you're best bet again is to stick with burst firing unless in CQB. The main difference between the Colt and the other assault rifles is the silencer it comes with. This can be a great tool when used effectively and before the enemy can work out where you're coming from they can be almost dead. The silencer may make the Colt slightly weaker, but it makes it all the more deadly. CT only.

Steyr Aug

This gun is very popular, like all assault rifles, and is the CT equivalent of the SG552 Commando. It is more expensive than the Colt, which is probably mainly down to it having an additional scope for you to use.

It's a pretty powerful gun with a good rate of fire, which again is slowed when you're zoomed in, although it does take a bit longer to reload than the Colt does, or the T's commando for that matter. Overall though, a great gun and worth the money if you can afford it as it's pretty accurate, and even better in bursts. An Aug on full auto will clear a small room pretty darn quickly. CT only.


Sniper Rifles

Scout

The poor man's sniper rifle, not really, but if you are low on cash this sniper rifle probably won't be out of your reach ($2750). One scout bullet can do a lot of damage on an unsuspecting victim on the other side of a map, but it can just as easily kill them if you get a headshot.....if not, two body shots should do the same job. It has two zoom functions as secondary fire, just to make it that little bit easier.

If you're a sniping fan and can be very accurate, this is a great gun for the money you pay...it's accurate (obviously) but more importantly it's not that inaccurate when you're on the move. Obviously you can't run and jump around whilst shooting and expect to hit someone, but if you're crawling or even walking then you're in with a chance (very much unlike the AWM). The 10 bullets in each clip should suffice, providing you have the ability to stay well clear of any CQB.

AWM/P

There are endless debates about this gun as so many people love it, yet so many people hate it and of course, lots couldnt care. It used to the case that one shot anywhere on the body would be a kill, until it was toned down so that a leg/arm shot wouldn't kill anymore. That's still an ok deal in my opinion though, under $5000 for a gun that will kill if you can hit your opponent's head or chest area.

If you like sniping you'll more than likely love the AWM, it's a great sniper rifle (again 2 zoom functions) and can be put to great effect with a Desert Eagle as your sidearm/backup. It has a slower rate of fire than the scout but from great distances you can afford to wait the little extra. Stay out of CQB as well, because when you're zoomed out you won't have a crosshair (disabled by CS team to discourage people pushing into small areas for easy kills).

G3/SG1

I'm not a fan of this gun at all, and I don't think most of the CS players are either as it's widely under used. Considering this gun has two zoom functions and costs a small fortune ($5000), you'd think it would have good accuracy.....wrong. It seems ok at times but too often you'll end up dead thinking 'wait a minute, I should've hit him 6 times at least!'.

Decent rate of fire for a sniper rifle and it's powerful enough but not worth buying really, judge for yourself. You'll rarely find a player who swears by it and can actually do very well with it, but maybe not even as often as that. T only.

SG550

Much like the G3, this gun is pretty rarely seen in CS. It basically functions like the G3 but is CT only, is cheaper and is also less powerful.

I'm not convinced with this type of gun, it's not ideal for sniping yet it's certainly no good close up and for the money you pay you won't get very much longevity in return, as you'll be dead soon enough if you hold onto this gun (some will disagree but most people don't like it). Definitely not the gun to go for if you have lots of money at your disposal, try an Aug or an AWP?


Machine Guns

Para

One word that could describe this gun in my opinion is 'fun'. It's not a particularly good gun, although you may be lead to think so by the price ($5750). Generally you won't see many paras in game either, until it gets to a stage where teams have more money than they need and they're dominating. The next step in the cycle is to pull out the paras and have some fun.

It has a massive 100 round clip, which is more than enough for any situation, and is pretty good in the power area. It does fall down slightly on the rate of fire and reload times but that's to be expected. It's also pretty inaccurate when you go full auto, but it can work well if you're in very close quarters battle and want to empty a room. If you don't kill everyone in there then the room will still empty as you'll have scared them off with the noise of the thing. I'm not sure why the noise intimidates people, however, as people usually dont get very far with a para....unless they're really taking the p*ss and kicking your ass with any gun.


Grenades

High Explosive (HE)

These are excellent additions to any player's arsenal of weapons (one is maximum you can carry), if possible I try to buy one every round just for the initial damage factor. If you are about to go into the heat of battle, what better to weaken your opponent than a well timed High Explosive grenade. If you're lucky/skilled then he can be below 50 health before you even see him, meaning you're in with a great chance of winning any battle and you haven't even fired a bullet yet.

It can also be used in quite the reverse and you can keep any HE grens until you're pretty sure a guy is near death (perhaps after a long range fight with you?). While you both take cover to reload switch to your gren and lob it in his direction....if it lands anywhere near him it's your lucky day hehe. Another good thing about HEs is that they aren't limited to damaging one person (obviously), so lob one into a crowd of injured opponents and watch the kills rack up (beware if friendly fire is on).

Flashbang (FB)

Again, I try to buy at least one of these per round (2 is maximum), as theyre great when attacking or even when you're retreating. On the attack there's nothing better to throw one into a room/tunnel and burst through only to find an opponent who is facing the wall, spraying his gun and hasn't got a clue where you are.......talk about easy kill.

On the defensive, it's very effective to use one of these before you either reload or try and make a dash to a safer area (perhaps back amongst your team). When using these, however, do be aware of your team mates.....they'll get very unhappy very quickly if you keep blinding them. All in all it's best to keep FBs for when you may really need them, there are lots of people who waste them by throwing them at the first opportunity they get. Possibly even wait til you hear an enemy so you have an indication of where they are.

Smoke Grenade (SG)

The least used grenade of the 3 available, but still very handy in certain situations. One of the most common uses for these grens is obviously for covering purposes, especially against snipers. A sniper may be blocking a route you need to cross in order to penetrate a bomb spot/hostage room.....a quick smoke grenade in his view should buy the time needed to make the dash across his scope view.

Can also be good as a distraction, for example, you want to rush left but throw a smoke gren to the right to draw the enemy's attention allowing you to slip through and behind enemy lines.


Well, that's the end of this little (yeah right) weapon guide. Hopefully you've found it at least a little helpful when it comes to your weapon of choice.

Source

Wednesday, January 14, 2009

Intro

Hi Welcome to my blog on How To Create your own CS1.6 Online Private Dedicated Server

This Blog is still new at the moment, more information regarding How To Create your own CS1.6 Online Private Dedicated Server will be added in a few days. While waiting, Please Download Counter Strike 1.6 Non Steam and start practicing!


Non Steam CS 1.6 GAME
Non Steam CS 1.6 PATCH
Fragbase MapPack