Hi,
Sorry for the delay, you might have got a quicker responce
if you had posted in our main forum at filefront
www.gamingforums.com/foru...orumid=250

Ok, this script does work in wildwest, I suggest that instead
of putting the code in autoexec, you simply make yourself
a .cfg file (a normal text file with .cfg instead of .txt extension)
This is beacuse depending on how you start WildWest, it may
or may not execute the autoexec.cfg in the wildwest folder,
or indeed the main folder, and if it does, it may or maynot
then re-execute the wolfconfig_mp.cfg file in your WildWest
which will overwrite any scripts you may have enabled in the
autoexec.cfg (lol I sound like a lawyer)

After you have created you cutom .cfg file, execute it in
game.(by bringing down the console and type "/exec yourscript.cfg" without quotes)

If you use seta instead of set, it will put the script into
your wolfconfig_mp.cfg file, and you won't have to run it again. I also suggest that you force an "unbind" on any keys
you setup in this way :

seta weap1 "weaponbank 5; set weaptog vstr weap2"
seta weap2 "weaponbank 3; set weaptog vstr weap1"
seta weaptog "vstr weap1"
unbind MOUSE2
bind MOUSE2 "vstr weaptog"

However , using seta means that if you make an error you will
have to edit the wolfconfig_mp.cfg file directly, so only use
the seta on scripts that you know work (like this one)

Hewster

Click Gun to visit The WildWest