This topic is locked
Quote
ok i just tried it out and ran into 2 problems:
1) there is "dead space" between empty slots -it would still try to cycle to the nades even if they are not equiped....you then have to cycle again to the next slot
2) the weapon cycle can still get screwed up by picking up and dropping different weapons
1) there is "dead space" between empty slots -it would still try to cycle to the nades even if they are not equiped....you then have to cycle again to the next slot
2) the weapon cycle can still get screwed up by picking up and dropping different weapons
it's a script hence the dead spot there is always going to be that space .the second part how is it affected by dropping/changing a weapon .unless you drop a weapon in which case you will have the dead space . see i really don't use this script i just wrote it quick for you. i use a bind that switches between primary and secondary and another one for my pistol .i think scripts will slow down the ammount of time it takes to draw the weapon .because you have to hit the button then it has to be read the executed then it will switch . i use scripts to change things like crosshair color in the middle of play to make it stand out against the background of what ever map comes up or team i spawn on. or for weapons load outs to switch weapons in game play for the next time i spawn .scripts like these are the ones that save you time.they can have there extra milli second or two to execute .i just like to have to have my weapons on the quickiest change possible.
MultiQuote
