Counter Strike – Scripting<\/p>\n
CS Scripting guide by ethereal<\/p>\n
Half-Life Counter-Strike Scripting
\nWelcome to the Counter-Strike scripting guide. This guide is meant for all the
\npeople who want to optimize their config and use clever and useful script to
\nenhance their Counter-Strike game. This guide covers the scripting aspect from
\nthe very simple and general up to the advanced and specific. You can go as far
\nas you want in this, but if you finish reading the guide you should be able to
\nmake your own advanced scripts.<\/p>\n
<\/p>\n
The Scripting Environment A config file is actually not much more than a list of commands that will be exec into the console, and the console will then execute all the commands in the +exec If you have the Half-Life icon on your desktop, right-click it, press D:\\games\\halflife\\halflife.exe -game cstrike.<\/p>\n Simply add +exec Now that you know how to use config files and execute scripting commands into The Bind and the Alias bind “ or, if more actions have to be bound to the same key, the ; can be used to bind “ as an example, you could warn teammates about you going to throw a flashbang:<\/p>\n bind “c” “use weapon_flashbang; say_team Watch it! I’m throwing a flashbang!”<\/p>\n The list of keys that can be used to bind actions to, can be found here. It is The Alias alias “ Pretty much the same as a bind, only it allows you to make a new name for it in alias “select_fb_grenade” “use weapon_flashbang”<\/p>\n alias “give_fb_warning” “say_team Watch it! I’m throwing a flashbang!”<\/p>\n bind “c” “select_fb_grenade; give_fb_warning”<\/p>\n The C key is now bound to execute the select_fb_grenade alias, and then execute \nThe Comment \/\/ This is the flashbang script, which warns my team before throwing a alias “select_fb_grenade” “use weapon_flashbang” alias “give_fb_warning” “say_team Watch it! I’m throwing a flashbang!” bind “c” “select_fb_grenade; give_fb_warning” The Basic Commands All you really need is a list of keys and a list of commands, and your own The Press\/Release command The Menu Selection commands \/\/ An MP5 buying script<\/p>\n alias “mp5_buy” “buy; menuselect 3; menuselect 1; slot10” bind F1 “mp5_buy” \/\/ Binds the script to the F1 key<\/p>\n The Echo command \/\/ Confirm Config Loaded<\/p>\n echo \nThe Wait command Toggle, Cycle and Press\/Release Scripts The Toggle Script \/\/ Toggle Script<\/p>\n alias “toggle_on” “ alias “toggle_off” “ alias “toggle” “toggle_on” \/\/ Initiate the first keypress to be Toggle ON<\/p>\n bind “ Take a look at this script and try to understand it. The key bound to “toggle” \/\/ Weapon Handedness Toggle Script<\/p>\n alias “handtoggle_right” “setinfo lefthand 0; alias handtoggle handtoggle_left” alias “handtoggle_left” “setinfo lefthand 1; alias handtoggle handtoggle_right” alias “handtoggle” “handtoggle_left” \/\/ Initiate first keypress to change to bind “v” “handtoggle” \/\/ Bind the V key to the handtoggle Script<\/p>\n \nThe Cycle Script \/\/ Cycle Script<\/p>\n alias “cycleoption1” “ alias “cycleoption2” “ alias “cycleoption3” “ :<\/p>\n alias “cycleoptionx” “ alias “cycle” “cycleoption1” \/\/ Initiate the Cycle at cycleoption1<\/p>\n bind “ As you can see, a toggle script is actual a cycle script with only 2 options. A alias “cycle_he” “use weapon_hegrenade; alias grencycle cycle_fb” alias “cycle_fb” “use weapon_flashbang; alias grencycle cycle_sg” alias “cycle_sg” “use weapon_smokegrenade; alias grencycle cycle_he” alias “grencycle” “cycle_he” \/\/ Initiate script to start at selecting HE<\/p>\n bind “g” “grencycle”<\/p>\n The Press\/Release Script \/\/ Press\/Release Script<\/p>\n alias “+scriptname” “ alias “-scriptname” “ bind “ Counter-Strike itself will automatically execute the -scriptname alias when the \/\/ C4 Planting Script<\/p>\n alias “+plant_c4” “weapon_knife; weapon_c4; +duck; wait; +attack; say_team I am alias “-plant_c4” “-attack; -duck” \/\/ Get up after planting the C4<\/p>\n bind “backspace” “+plant_c4” \/\/ Bind a key to the C4 planting script<\/p>\n The script selects the knife first to be sure that you don’t waste any ammo, Easy Scripting alias “longwait” “wait; wait; wait; wait; wait”<\/p>\n alias “longerwait” “longwait; longwait; longwait; longwait; longwait”<\/p>\n alias “verylongwait” “longerwait; longerwait; longerwait; longerwait; The average mathematician can see that the verylongwait encompasses 125 waits, Another time and text saver is the shortening of the menuselect commands:<\/p>\n alias ms1 “menuselect 1” It’s easier to make buying scripts by just using the ms0-9 commands. Also when alias clmenu “slot10; wait; slot10; wait; slot10; wait; slot10; wait; slot10; By adding the clmenu command at the end of all menu-using scripts, you are Counter Strike – Scripting CS Scripting guide by ethereal Half-Life Counter-Strike Scripting Welcome to the Counter-Strike scripting guide. This guide is meant for all the people who want to optimize their config and use clever and useful script to enhance … Read More »<\/a><\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-111","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/111","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=111"}],"version-history":[{"count":0,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/111\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=111"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=111"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=111"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nBefore we start playing around with the scripting language, it is important to
\nknow how to actually enter these scripts and use them in Counter-Strike. The
\nmain scripting command processor is the console. When you press the ~ or ` key
\non your keyboard, it brings down the console and shows you all past commands
\nand
\nhappenings in the game. You could consider it the raw text format of everything
\nyou do in the game. The console is also used to enter text commands into. All
\nscripts discussed below can be entered straight into the console and used
\nthereafter. However, to prevent you from having to type slabs of text, it is
\neasier to use configs. A config file will be of the format
\nplaced
\ninto your cstrike dir. It can be simply opened with the Windows text file
\neditor, and can be created by making a new text document
\nchanging
\nit to
\nthe binds, keys and settings. However, since Counter-Strike creates this file
\nand is not able to store elaborate scripts in it, you are advised to make your
\nown config file.<\/p>\n
\nentered into the console. In stead of typing in all the commands in your config
\none by one, you simply type:<\/p>\n
\nconfig file. Alternatively, if you want Half-Life to automatically execute your
\npersonal config file on startup, you should add the following command to your
\ncommand line:<\/p>\n
\nproperties and edit the “Target” box. It will be something alike to:<\/p>\n
\non startup.<\/p>\n
\nthe console, it’s time to get scriptin’!<\/p>\n
\nWe start off with the most basic of scripting commands: the bind and the alias.
\nA bind is a command that links a keypress to a command. If you open your
\nconfig.cfg in the cstrike directory with the text editor, you will see it
\nstarts
\noff with a whole list of binds. All binds are in the same format:<\/p>\n
\nseperate actions:<\/p>\n
\nusually wise to assign the most important binds (the ones you use most often)
\nto
\nkey that are easy to reach. All the different actions that can be bound will be
\ndescribed in the next piece of this guide. First, we have to take a look at the
\nalias.<\/p>\n
\nAn alias is a actually a way of grouping commands under a new name, which
\nallows for more advanced scripting as we will see lateron. This new alias name
\nis also a new command word, which executes all the actions in the bind. The
\nalias is used in the following format:<\/p>\n
\nstead of immediately binding it. The aliasname could be anything you can think
\nof, but two things should be kept in mind. First of all the alias name should
\nbe
\ndiscriptive, so you know by looking at the name, what alias it is and what it
\nis
\nused for. Second, you should never use existing commands or keys for an alias
\nname. The flashbang warning and selection bind as shown above, can be rewritten
\nusing the alias command:<\/p>\n
\nthe give_fb_warning alias. In this example, it may all seem a bit elaborate
\nsince the simple bind works just as well. However, aliasing allows more
\nadvanced
\nand comprehensive scripting as we will see lateron.<\/p>\n
\nThe last basic scripting command that should be discussed is the comment. You
\ncan add comments to your command lines in your config file, by simply adding
\nwhatever text you like after two slashes: \/\/. The console ignores all text
\nwritten after two slashes. For examply, you could comment on the flashbang
\nscript:<\/p>\n
\nflashbang<\/p>\n
\n\/\/ This part selects the grenade in hand<\/p>\n
\n\/\/ This part warns the team<\/p>\n
\n\/\/ This part binds the two actions to the C key<\/p>\n
\nEvery action you do in the game can also be done executing a command in the
\nconsole. You could actually play Counter-Strike simply by typing commands into
\nthe console. It probably wouldn’t get you very far though ;-). What you do have
\nto realise is that every keypress you make in the game can actually be
\nautomated. If you find yourself making the same series of keypresses time and
\ntime again in the game, then why not automate it? For instance, to buy an MP5
\nyou would press the “buy” key, the “3” key and the “1” key. Why not simply
\nassign one key to buy an MP5 for you? And why not add a kevlar vest, HE grenade
\nand primary ammo to that as well?<\/p>\n
\nimagination to link the keys to the commands. The command list provides you
\nwith
\nmost of the commands used in common scripting. I haven’t added every last video
\nand setting command since the list could go on for ages. The current command
\nlist should fulfill all your scripting and automating needs. However, some
\ncommands aren’t as simple as your standard say and say_team, and will be
\ndiscussed below.<\/p>\n
\nFirst of all there is the + and – type command. For instance, the attack
\ncommand comes as “+attack” and not simply “attack”. Why? Well the + indicates
\nthat the following command will be executed at keypress, while it’s –
\ncounterpart will be executed at key release. This means that when you press
\nyour
\nattack key (most likely mouse button 1), the console executes the +attack
\ncommand (fire the gun) and when you release the mouse button, the console
\nexecutes the -attack command (stop firing the gun). The +attack command
\nactually
\nkeeps firing until the -attack command is given. Try typing +attack into the
\nconsole just for fun, you will see that you will remain firing forever! Well
\nuntil you run out of ammo that is (this doesn’t work with the pistols as they
\ndon’t have continuous firing). The same is true for the duck command. If you
\ntype +duck in the console, you will remain in crouching position until the
\n-duck
\ncommand is given.<\/p>\n
\nNext there is the menuselect and slot10 commands. The menuselect command
\nselects a menu item by toggling the correct number. The command “menuselect 2”
\nselects the 2nd item from the menu. This menu includes teamchoosing menus,
\nbuying menus and radio sound menus. The “slot10” command is used to close any
\nmenus that are still open. So the script to buy an MP5 would be:<\/p>\n
\n\/\/ Buys MP5 and closes the menu<\/p>\n
\nThe third special command type is the “echo” command. This command echoes the
\ntext written behind it directly to the console. It is most often used to
\nconfirm
\nthe loading of a config. You are advised to add something like this to the end
\nof your new config file:<\/p>\n
\nThe last special command type is the “wait” command. This command forms a delay
\nof one game tick, which is actually a very short period of time. Why wait would
\nyou say. Well sometimes a whole line of commands in a row will get a bit
\nclogged
\nup and especially if your connection is a bit laggy, you might find that some
\ncommands in your script have been skipped or lost. If your script is
\nmalfunctioning, remember to try and put some waits in. They can be considered
\nthe ‘oil’ of a script. More waits generally make it run smoother. Waits can
\nalso
\nbe used to actually put some time in between commands. One can think of a
\nscript
\nthat plants the C4 bomb (requiring some time to plant the bomb) which says
\n“guarding the bomb” after it has been planted. However, since a wait is a very
\nshort time, you are advised to make a longwait, as discribed in the Easy
\nScripting section below.<\/p>\n
\nThere are three special types of scripts that can be used to fulfill your
\nadvanced scripting needs. They will be discussed below<\/p>\n
\nThe first is the toggle script. This type of script can be used to switch a
\ncertain setting on or off with only assigning one key to it. Pressing it once
\nput the setting on, pressing it again puts the setting off. It can be
\nconsidered
\nas a switch. The setup for this type of script is quite simple<\/p>\n
\n\/\/ Toggle ON<\/p>\n
\n\/\/ Toggle OFF<\/p>\n
\nwill execute the “toggle” alias when pressed. The first time the key is
\npressed,
\nthe toggle alias will in its turn execute the “toggle_on” alias, as Initiated
\nin
\nthe script. The toggle_on alias actually executes the desired command, and
\nchanges the “toggle” alias to execute the “toggle_off” alias the next time it
\nis
\nused. The next time the key is pressed, the “toggle_off” alias is executed,
\nwhich itself changes the script to execute the “toggle_on” alias the next time
\nagain. The switching script has been made. A common usage for the toggle script
\nis to assign a key to changing the weapon from the right to the left hand and
\nback. This script would look like this:<\/p>\n
\n\/\/ Toggle to Right Hand<\/p>\n
\n\/\/ Toggle to Left Hand<\/p>\n
\nleft hand<\/p>\n
\nThe next type of script is the cycle script. This script cycles between a range
\nof options and returns to the first option after the last one has been reached.
\nQuite similar to the toggle script, it will look like this:<\/p>\n
\n\/\/ Command 1 and Cycle to 2<\/p>\n
\n\/\/ Command 2 and Cycle to 3<\/p>\n
\n\/\/ Command 3 and Cycle to 4<\/p>\n
\n\/\/ Command x and cycle back to 1<\/p>\n
\ncommon usage for the cycle script is to cycle between the different types of
\ngrenades you are holding. It would look like this:<\/p>\n
\n\/\/ Select HE and cycle to FB<\/p>\n
\n\/\/ Select FB and cycle to SG<\/p>\n
\n\/\/ Select SG and cycle to HE<\/p>\n
\nThe last type of special script is the press\/release script. This script is
\nused like the press\/release commands in Half-Life (like +attack and +duck). It
\nexecutes a range of commands on keypress, and executes another range of
\ncommands
\non the release of that same key. It will look like this:<\/p>\n
\nkey is released, preventing you from having to make the link yourself. One of
\nthe best press\/release scripts I have come upon is the C4 planting script:<\/p>\n
\nplanting the bomb!; slot10″ \/\/ Plant the C4<\/p>\n
\nshould the script skip the weapon_c4 selection part. It ducks, places the bomb
\nwhile the backspace key is held and gives a warning to the team. At key release
\nit gets up again.<\/p>\n
\nThere are a couple of smaller scripts that make life a bit easier for the
\nscripter. First of all there is the longwait. In stead of having to type
\nwait;wait;wait;wait etc in your scripts, you can alias it to make it all a bit
\neasier:<\/p>\n
\nlongerwait”<\/p>\n
\nwhich is actually STILL a very short time in-game.<\/p>\n
\nalias ms2 “menuselect 2”
\nalias ms3 “menuselect 3”
\nalias ms4 “menuselect 4”
\nalias ms5 “menuselect 5”
\nalias ms6 “menuselect 6”
\nalias ms7 “menuselect 7”
\nalias ms8 “menuselect 8”
\nalias ms9 “menuselect 9”
\nalias ms0 “menuselect 0”<\/p>\n
\nclosing a menu, you will often find that when you just use the “slot10”
\ncommand,
\nit will skip it and leave the menu open. To be sure your scripts operate
\nsmoothly, use the clmenu alias:<\/p>\n
\nwait; slot10; slot10; slot10; slot10; slot10″<\/p>\n
\nensured the menu closes after the script has finished. Still not closing? Just
\nput two clmenu commands at the end ;-).<\/p>\n","protected":false},"excerpt":{"rendered":"