Zero Ronan Condon

Absolute Fucking Champion clan : n8z
posts : 816 site administrator
    
| ok, this is a short guide to online qw, a very short guide, but enough to get any of you started. for any beginners, i recommend mquake, which can be downloaded here. i am going to write this as quickly as possible, and this will set you up at least as much as is needed to play a war. (there are ppl who after years of the same cfg still sit there and tweak it.)
mqwcl config
1. best thing to do to get started is get my config here. you can then modify that but for now it will set up mquake reasonably well.
2. load up mquake and type in add_user {name}: this command will add your user to mquake, e.g. "add_user paddy" for this example.
3. copy my zero.cfg to your qw/users folder and replace "paddy.cfg".
4. load up mquake again and type login paddy: this logs you in under my settings.
weapons
in mquake, you dont need to use impulse commands, which is well handy, because for the simple "best shotgun" bind, you don't have to type in "impulse 2;wait;impulse 3" etc. in mquake there is a weapon command, and it's used like this:
(best shotgun): bind x "weapon 32" (notice its best weapon first in mquake.
(best nails/shaft): bind x "weapon 854"
(best explosive): bind x "weapon 76"
get the message? ok. quick recap over a few things you might want to change on my config for you lads who have been away too long:
1. /sensitivity (duh)
2. /m_pitch (duh, 0.022 for normal mouse, -0.022 for invert)
3. /fov (i use 100, nyeh)
4. /cl_fakeshaft (i have it set to 0 for normal shaft, recommend you do too.
5. /morekeys (if set to 1, it allows you bind the keypad as separate keys, handy for ppl who still play that side.)
6. /crosshair (1-9 in mquake, i use 2 like normal qw.)
7. /crosshaircolor (mine is set to 14, more or less white, screw with it, 1-255 til u find one u like.)
other than that, it's just a case of binding your weapons. most people now have a rocket-jump script for standard jumps, he's one if you want to put it in :
alias quicklookdown "cl_pitchspeed 20000 ; +lookdown ; wait ; -lookdown ; cl_pitchspeed 150"
alias quicklookcenter "cl_pitchspeed 2800 ; +lookup ; wait ; -lookup ; cl_pitchspeed 150"
alias superjump "quicklookdown ; +jump ; wait ; -jump ; impulse 7 ; +attack ; wait ; -attack ; quicklookcenter ; force_centerview"
bind a "superjump"
another handy one is the forward rocket-jump, this is the basic version of it :
bind "v" "rotate 180;impulse 7;cl_pitchspeed 5000;+lookdown;+attack;wait;-attack;rotate 180;-lookdown;force_centerview;cl_pitchspeed 150"
ok, nearly there. teamplay next. i always keep my teamplay binds in a separate config, for the simple reason that mquake rewrites your config every time you "cfg_save". this is a cool feature, because it lays it all out alphabetically and with comments. however, your teambinds usually arent in aphabetical order, and its annoying trying to find them. here are some standard teamplay binds, put them in a cfg file in ure /qw folder, e.g. tp_paddy.cfg.
//teamplay binds
//green † red ‡ yellow ‡ blue ‰
// = fancy left bracket
// = fancy right bracket
bind "f5" "say_team $\p ‡ %a%a\%hh\%b %l - get pent"
bind "b" "say_team $\p † %a%a\%hh\%b %l - [††† i am %p †††]"
bind "," "say_team $\p ‡ %a%a\%hh\%b %l - rl nme at %d "
bind "." "say_team $\p ‡ %a%a\%hh\%b %l - weak rl nme at %d"
bind "g" "say_team $\p ‰ %a%a\%hh\%b %l - going for quad"
bind "h" "say_team $\p ‡ %a%a\%hh\%b %l - help!"
bind "n" "say_team $\p ‰ %a%a\%hh\%b %l <--- need item"
bind "o" "say_team $\p ‡ %a%a\%hh\%b %l - nme %q near %l"
bind "p" "say_team $\p ‰†‰ %a%a\%hh\%b %l - ‰†‰ %q over ‰†‰"
bind "q" "say_team $\p ‡ %a%a\%hh\%b %l - get quad"
bind "w" "say_team $\p ‰ %a%a\%hh\%b %l - coming from %l"
bind "alt" "say_team $\p †† %a%a\%hh\%b %l - secure"
bind "mouse3" "say_team $\p ‰ %a%a\%hh\%b %l - %t"
bind "mwheeldown" "say_team $\p † %a%a\%hh\%b %l"
bind "mwheelup" "say_team $\p ‰‰ %a%a\%hh\%b %l - took %i"
bind "l" "say_team $\p ‡ %a%a\%hh\%b %l replace me"
//
// end of configuration script
//
the above binds aren't as daunting as they look. the "$\p" there (p for paddy) means that when you hit a team bind, it looks like "p quad over" rather than "(paddy): quad over". the purpose of team binds is to get as much information to your teammates as possible without spamming them.
legend:
%a = how much armor you have
%a = what type of armor (e.g. 64r)
%h = how much health you have
%b = your current best weapon. (if you are on ssg to stop losing ure rl, it still says rl.)
%l = your location.
%q = last powerup you saw
%p = the powerup you have
%i = the last object you picked up, and where u took it. (e.g. took mega at 666)
%t = this is pointing. shows up as "xxx at yyy" on ure screen to stop ppl seeing thru walls. point at something and hit it. handy, as you dont have to individually bind all your "available" keys.
%d = where you last died.
i'm not saying that these are the best binds in the world, they are more or less the ones us lads in nd use, and i think they're deadly. because :
in every message you send to your mates, it tells them not only the intended message, (quad over etc), but also tells them your health, armor, weapon and location on the fly. the cool thing is that when they get your message, but if they need to know, they also know your exact situation. e.g. while sitting on dm3 ra i see :
bunny : 0a\44h\rl:5 pent - took backpack at pent
rather than just knowing that bunny won an rl out the back of dm3, it also tells me that seeing as bunny is our quad guy, there is no way he is going to make the next quad on 44 health, and i have to go. it also tells me that he will more than likely come up the back lift and need backup when he does, so i'll probably come back through and clear sng with quad to ensure he gets to health and takes over ra. if you want to get really technical, it possibly means the next outside mega will be back in 20 seconds, and i can collect it after my quad is gone, come back through the pent lift and let bunny back to quad after he tools up in ra. fucked up, isn't it? but the coolest thing about it is that if you don't want to or can't read all the health/armor shite, it doesn't matter because you still get the main intended message.
anyhoo, the binds you use are very important, its wise to use the same binds as the guys on your team. also, those black boxes up there are colour codes. (red = danger, blue = informative, yellow/green = ok). some of the binds are mixtures to catch your attention. (remember, the brain reacts quicker to colours than letters.)
more information can be got on the mquake readme, about things like autorecording demos, fancy letters etc., but this is the basic setup and should get you going in no time. i will probably add to this as i wrote it in a hurry. any suggestions welcome.
zero.
|