If I try to use “_weapon” in my binds and attempt to add something more after “;” then the bind will fail.
I would like to know if there is any known workaround for this problem?
What I tried:
set wpn1 "_weapon0" "" "default"
set wpn3 "_weapon2" "" "default"
set wpnhidden "ui_showGun 0"
set wpnshown "ui_showGun 1"
bind "1" "vstr wpnshown; vstr wpn1"
bind "3" "vstr wpnhidden; vstr wpn3"
It’s by design to prevent unfair scripts. Any commands beginning with an underscore can’t be combined.
So far as I know there’s no way to have showgun on automaticaly for one weapon and not another.
I just have a bind to toggle showgun, works fine, then just use in conjuction with class binds
Someone explain to me how is different sensitivity, accel and gun hidden/shown unfair advantage if anyone could do it?! SERIOUSLY?
hm, what’s next ? disable ALL custom/user-made tweaks ? deny access to console and access to ranked servers, for those players who edit even single cvar ?
wrong. at least 2/3 of game developers consider this-way “solution” as appropriate. for decades.
point is matter what side SD take.
originally im prefer iD-created/inspired tranparent development/editing-extending/using way, but to keep fairplay some dev’s prefer desperate measures, rather than try devlop palliative solutions, struggling with engine/resources/timeline limitations.
cuz there is PRACTICALLY no differences between ways of how supernatural superiority gained by some players, instead of gaining gaming skill itself.
First of all the “if anyone could do it” argument is pretty crap since scripts which may utilise an exploit or provide some significant advantage over “vanilla” settings don’t get advertised too widely as they are generally formulated specifically for an advantage over other players. Besides glitching or exploiting activities are very dark grey areas either on or over the border of hacking depending on who you ask.
Besides this I think this restriction was made to prevent any opportunity for a weapon variable to be used in any script which may profer an advantage. This was primarily based on the W:ET experience where many anti recoil, quick weapon switch, auto reload and attempts at burst fire binds existed and were effectively exploits of the extended config system.
A number of minor weapon exploits in ETQW could be further exploited if this kind of chain binding was allowed.
Sorry dude, the reason for this was far from arbitrary, there are plenty of useful scripts out there for all sorts of activities but weapons are basically off limits for anything beyond toggle commands.
MOOKA!
p.s. G’day Cankor
Yep, this has been limited on purpose to prevent macro actions for weapon related stuff.
