Both hinder mobillity alot. It would not even help newbies to use these as they would never learn and the disadvantage of not being able to wait before biting is HUGE.

The basic syntax for binding a command to a key is
bind keyname commandstring. bind is just a keyword that makes the engine realize that you want to attach a command to a button, keyname is just the name of the key(e.g. p, q, shift, tab, kp_ins(key pad insert key) or mouse1). commandstring is a string of commands separated by ; and contained withing qoutation marks(e.g. "+showscores;wait;net_graph 3;wait" ). You don't need quotation marks if your just passing along a command.

Commands can be aliases(which are user defined strings of commands) or commands made available to the player by the MOD makers.

Commands are of 3 types, those that are preceded by a sign and those that are not as well as those that are not preceded by a sign and take an argument. Commands that are preceded by a sign such as +jump are activated when the + command is executed and turned of when the -command is executed. If you only bind a + command to a key it will automatically execute the -command when you let up the key. The most important such commands are +attack, +jump, +duck, +forward, +backwards, +moveleft (?), and +moveright(?). If you bind more than one command to a key in conjunction with a + command the - command will NOT be executed when you let up the key(to do so you need to use and alias which can also define + and - commands).

Commands that take an argument are of the form "command argument"(e.g. net_graph 1 (turn on the net graph), gl_texturemode gl_linear_mipmap_linear (use trilinear filtering) and sv_cheats 1(turns on cheats(mostly for developers) if you are an admin)).

Aliases take the form, alias commandname commandstring. What it does is tell the engine to make a user defined command named commandname(this can be a +, - and normal command but an alias cannot take a variable). The command string is just as before a string of other commands and aliases. (don't bother trying this: alias command1 command2
alias command2 command1 )

Aliases and commands can be executed or created directly from the console but for aliases to be loaded on startup of the game you need to make or modify autoexec.cfg or userconfig.cfg(or any other name.cfg text file but then you have to put "exec name.cfg" in your config, execute the file from your console while ingame in the same way or bind "exec name.cfg" to a button(e.g. bind pgup "alien.cfg", bind kp_plus "low_ping_config.cfg")). In these files you simply make a list of aliases, commands to be executed, binds to be made etc. Empty lines or lines begun with // are ignored without giving you an error in the console.

to make a + or - alias simply do something like
alias +show_net_score "+showscores;wait;net_graph 3;wait"
alias -show_net_score "-showscores;wait;net_graph 0;wait" (is it showscores?).

You are much better off setting things up so that you can easily switch to whatever weapon you wan't to use, very quickly and manually instead of trying to script some leap and bite thing(there is a reason skilled players don't use them, and it's not because they think it is an unfair advantage ).

For a >2 button with a mouse wheel you can do something like this:

bind mouse1 "+attack"
bind mouse2 "slot1"
bind mouse4 "slot2"
bind mwheeldown "slot3"
bind mwheelup "slot4"

As well as turning on hud_fastswitch 1.

(mouse3 is typically the very inconvenient "button" that you activate by pressing the mouse wheel straight down).

If you only have 2 buttons and a mouse wheel you can use a quickly reached button on your keyboard for switching to the least common slot(in my, and most peoples case that would be slot 4).

I see a lot of people(including myself) getting accused of cheating(even on C-D servers) because they can properly select any weapon they want to use very quickly as well as having mastered basic movement(strafe turning, the usage of blink and leap and to a lesser extent bunny hopping). It's funny, but I have never been accused of cheating by a vet or claner allthough I see them hanging around all the time on C-D servers and they should be better at recognizing a cheater than a frustrated newbie.

Strafe turning: it is a necessity, I would say it is probably the most important skill in combat as both marines and aliens. Allthough it has nothing to do with scripting it is a "must know" as it makes you about 10 times as effective with leap and blink and is so easy anyone can do it. blink, leap or jump and then let go of forward and press strafe in the direction you want to turn and move your mouse in that direction. You will turn in the air and even gain some speed if you don't turn to fast(if ducking you can't turn as fast unless you are gorge or skulk). This offers you much agillity when leaping, blinking after a moving target and is the basis for bunnyhopping if you care to learn that as well.

Bunny hopping: strafe turn while you are in the air and then jump as soon as you land to avoid friction. There are scripts to help lessen the burden of strict timing but they more hinder you from learning how to do it without scripts than help you while you are learning.

The most innofencive of these(a bunch of people consider these types of scripts an illegitimite advantage allthough alot of people use them as well as being allowed in a few forms in many leagues which if anything should have stricter requirements than public servers on what you can and cannot do) would be to simply bind +jump to the mouse wheel and pull the mouse wheel quickly slightly before you land. The slighlty less offencive alternative(which is about as simple as using the mousewheel and is allowed in most leagues(for NS, not necessarilly other MODs)) is to do something like this:

alias +3jumps "+jump;wait;-jump;wait;+jump;wait;-jump;wait;+jump"
alias -3jumps "wait;-jump"

For lerks(which would have quirky movement with a jump script such as that)

bind anykey 3jump_on
alias 3jump_on "bind jumpkey +3jumps;bind anykey 3jump_off"
alias 3jump_off "bind jumpkey +jump;bind anykey 3jump_on"

If you use such a script you will never get a good timing on when you are supposed to jump without any script, in fact you would learn to jump slightly to early and consistently miss when you don't use such a script. Allthough many leagues would allow such a jump script as that above they, by common convention, allow only 3 jump commands in a row executed at one keypress.

Allthough legitimacy of such scripting is debatable it is used by many people and anyone should at least get to know about the issues instead of brushing them under the rugg and pretending there is no issue. Make up your own mind on this issue and if you feel strongly about it's formal removal from the game post in suggestions and ideas or one of the(no doubt existing) threads on the subject.

One of the most difficult aspects of bunnyhopping is avoiding or handling objects in the map that come in your way(strairs, rails, slopes), no amount of scripting will ever remove that.

Personally I don't think scripting is good for much with few exceptions and for "comfort"(show scores and net graph at once, quickly switch between a few client settings to suit network conditions with the press of a button, toggle the volume up and down without having to reach for the knob on the speaker, )

Setting up your binds properly is a huge advantage. Evolutions(impulse commands), building chambers(impulse commands), comfortably switching between weapons(slot# commands), sayings(impulse commands), a comfy setup with lots of buttons close to your strafe keys(e.g. wasd or esdf(my favorite) as movement keys).

Some impulse commands(the once specific for combat missing):

marine/alien meaning. numbers must be preceded by impulse and a space.

1 Next Weapon -
3 Drop Weapon -
5 Ready Room
7 Follow Me/Chuckle
8 Covering/Need Healing
9 Taunt/Need Backup
10 Need Health/Incoming
11 Need Ammo/Attack
12 In Position/I'm Building Here
13 Enemy Here/ -
14 Move Out/ -
15 All Clear/ -
80 Need Order/ -
81 Acknowledge/ -
90 -/ Build Resource Tower
91 -/ Build Offence Chamber
92 -/ Build Defence Chamber
93 -/ Build Sensory Chamber
94 -/ Build Movement Tower
95 -/ Build Hive
100 flashlight/"alien flashlight"
101 -/ Upgrade: Carapace
102 -/ Upgrade: Regeneration
103 -/ Upgrade: Redemption
107 -/ Upgrade: Celerity
108 -/ Upgrade: Adrenaline
109 -/ Upgrade: Silence
110 -/ Upgrade: Cloak
111 -/ Upgrade: Scent of Fear
112 -/ Upgrade: Enhanced Sight
201 Spray Logo

Actually, if you have a script that uses a press and release to quickly switch between two attacks (leap and bute, blink and swipe) it can be verry effective.

or

Both of which are very effective if you give them some practice.

Theese work because I have the popup menu bound to z, so I can use mouse2 to controll my movement. I can leap, release leap and bite/xeno (whatever last attack was) a lot more effectivly than manually switching weapons and with only one click of the button.

Now, I know that similar results can be done with binding lastinv to MOUSE2, but you would have to click twice and the scripts make the press and release.

Attached is a tutorial about scripting, it is really helpfull. In it is a list of all the keys names also, that in itself is verry usefull.

That's a quick one, don't feel like making one that switches to knife after pistol is gone tho. I use it, and have gotten quite a few pistol kills since I started using it too.

I do have an idea for a script like what you want, it's long and would be kind of annoying because it would auto switch after every round of ammo is depleted.

NS is built on Half-Life, so it uses Half-Life's scripting system. It's very primitive; it's basically nothing more than advanced control configuration. I learned HL scripting from this site. The site's a bit dated, but so it HL - nearly all of the info on that site is still current.

[edit]Oh, and there's also my console guide, which may help.[/edit]

Mostly it's a customisation issue. Console scripting lets you alter your inteface to suit your particlar tastes much more than the options menu. Things such as toggleing stuff that's meant to be held down (like crouching), comms scripts, in-game options tweaking, helpful scripts...

It's by no means necessary. It's just a matter of personal taste.

As he said, he does not need to use one, (I mean, who would?) it just makes things easier.

Saying that though, you *could* aim, but an aimbot makes it easier.

I 'spose there must be a cut-off point somewhere between the two.



Soz to hijack, but as we are on scripting, can anyone tell me why this should crash ns when run?

//Fade Blink swich (push the button switch from slot1 to slot2, and then again to go from slot2 to slot1)
alias fadeblink "fadeblink1"
alias fadeblink1 "slot2; wait; +attack; wait; -attack; alias fadeblink1 fadeblink2"
alias fadeblink2 "slot1; wait; +attack; wait; -attack; alias fadeblink2 fadeblink1"
bind "mouse2" "fadeblink"

Two things.

• the syntax for the alias looks wrong (alias fadeblink2 fadeblink1) It should be [alias [nameofalias] [command string], quotes never hurt.
• I do not believe you can make an alias inside an alias

If you are trying to make an alias for a key that changes between two functions, make the alias' seperately, try this:

Try blinkswiping someone, using lastinv, when you're five feet away. Guess what: isn't going to happen.

That's his client-side lastinv script with my keys added in.

Edit:
You need to know that MOUSE5 is my lastinv key, PG_DN is slot1, KP_DOWNARROW is slot2, KP_LEFTARROW is slot3 and KP_5 is slot4.

I use one of those, it goes like this...

Tap 3 before you go into battle, and when you want to stop reloading, hit Q twice.

I think this'd do it.

The problem, I believe, lies with "alias fadeblink1 fadeblink2" and "alias fadeblink2 fadeblink1". Upon the third execution of "fadeblink" you become trapped in an infinite loop.

This should work (changes are bolded):
alias fadeblink "fadeblink1"
alias fadeblink1 "slot2; wait; +attack; wait; -attack; alias fadeblink fadeblink2"
alias fadeblink2 "slot1; wait; +attack; wait; -attack; alias fadeblink fadeblink1"
bind "mouse2" "fadeblink"

It actually is following that syntax. In "alias fadeblink2 fadeblink1", fadeblink2 is the alias name and fadeblink1 is the command string.

You can make an alias inside an alias. I do it all the time. In fact, due to bad experiences in the past with putting binds inside aliases (scripts often wouldn't work even when everything seemed right), I always use aliases within aliases rather than binds within aliases.

That would only work for the primary weapon. Substituting lastinv for slot1 in that script will increase its versatility.

Guess what? I do it all the time and it's super easy(well technically I have slots bound to keys and fastswitch on instead of lastinv but it's allmost the same). There is a(small) minimum time between switching and slashing, no scripting will ever change that and it's quite enough to make blinking and slashing without scripts just as easy except it gives you more controll and less hazzle. You may change your mind and wan't to blink again before swiping without having to make another script that will cancel and "reset" the binds of the last.

"You may want to blink more than once before you make your swipe" possibly?
Soz, you lost me a bit.


Mintman, a civilian, MMZ>Torak: Thanks.


One more thing, is there a practical difference between these two?

1)
alias fadeblink "fadeblink1"
alias fadeblink1 "slot2; alias fadeblink fadeblink2"
alias fadeblink2 "slot1; alias fadeblink fadeblink1"
bind "mouse2" "fadeblink"

2)
alias weap1 "slot2; bind [chosen key] weap2"
alias weap2 "slot1; bind [chosen key] weap1"
bind "mouse2" "weap1"



TY. Finally, what's Romano's client-side lastinv all about? I tried and failed to interpret it, dispite HL script almost being psuedocode.

Yeah, I think you're right, but the slotx commands work a lot faster than lastinv ( for me at least ).

It is client side. slotX is a clientside command which is sent to the server. Lastinv goes to the server finds out what your last weapon was, then changes to that weapon. The clientside version just changes to that weapon.

No, and The Creator (Flayra) designed it that way.

I don't wanna bash you but that won't work : a +command must be ended by a -command, in that case, the script would work once.

alias release "+attack;wait;-attack"
alias +leapswitch "weapon_leap"
alias -leapswitch "release, lastinv"

WOULD work, however.

There is none.

It emulates what the lastinv command does, but does it quicker.

Since he's a vet and probably is in tournaments and stuff, that would probably either be a mousewheel bind for +jump, something like the triple jump script I posted earlier or nothing at all(the l33t way to do it).

Since the _special-exploit(thankfully) is gone(it allowed executing a small loop of commands as fast as possible while a button was held), that would probably be something like a lot of +attack;wait;-attack;wait;+attack....

It won't help you much though since you will allways empty your entire clip and can't change your mind. Attack and movement scripting will allmost allways reduce your flexibillity rather than help. It really isn't hard to max out the ROF of the pistol by hand, it only gets slightly more jerky but you can stop and wait for the alien to pop it's head back out in the doorway before wasteing the rest of the clip should you want to.

Yes, sorry about the "wan't"(if that was it) I allways spell want wrong if I'm not consiously thinking about it .

Such a script really doesn't help you much when you've gotten used to your config. It allows no flexibillity at all. You can't decide to blink, have a stroke of metabolize in mid-air, blink again, select swipe, regret it and select blink again, blink and then swipe, blink, blink etc. Scripting complex enough to let you do that is simply too many buttons and you may as well do it manually.

If you'd like you can perfect this code by adding appropriate -attack's but it is not necessary. I find this better than auto shooting because it still gives you control over how many shots you fire (unlike +attack;wait;-attack...etc). The only downside is firing with accuracy usig your mousewheel takes a lot of practice, practice better spent on learning how to fire it normally :S

For the auto switch after magazine empty script:
There is no such thing. There is no command that will know when you run out of ammo. Why? Simply because commands are autonomonous and are executed without bias. There is no way to test conditions/use logical selection (i.e. if,then,elseif) with commands, so there is no way to test if you have run out of ammo, this would need to be part of the core code (i.e if(hud_ammo <= 0)....). The only other possible simulation of this would be to time exactly how long it takes for you to empty a clip, and then use "wait" commands accordingly to time the switch, but the drawback is obvious to this, you may not always empty your clip all at once...
Ultimately, it's up to the scripter to decide which scripts suit him best and personalize scripts for certain sequences. Happy Scripting!