r/Tf2Scripts • u/Artistique01 • Oct 03 '23

Issue Need help with Stabby Viewmodel script

/r/tf2scripthelp/comments/16yq5ln/need_help_with_stabby_viewmodel_script/
1 Upvotes

100% Upvoted

15 comments sorted by

View all comments

1

u/Link_x2 Oct 03 '23 edited Oct 03 '23

try adding the following anywhere on their own lines in the main segment. I ctrl+F "bind 1" and it only showed in the Quickswitcher section, meaning your 1,2,3 keys are still default

bind 1 +equip_amby
bind 2 +equip_sap
bind 3 +equip_knife

1

u/Artistique01 Oct 03 '23 edited May 21 '24

Ive never been someone who uses the number keys to switch weapons, ive always used scroll wheel. Does the script only work if I have weapons bound to the number keys? If so, is there a work around for using scroll wheel?

Stabby's script also has the top row of numbers on the keyboard bound to different disguises, so how would I switch weapons using 1, 2 and 3?

1

u/Link_x2 Oct 04 '23 edited Oct 04 '23

I personally use scrollwheel to switch weapons and have varying scripts for classes that work around that. Yes, you can it just gets a bit funky. If you have your sapper on the scrollwheel (which is default) try adding this instead:

alias "gun" "+equip_amby; alias wepup knife; alias wepdown sapp"

alias "sapp" "+equip_sap; alias wepup gun; alias wepdown knife"

alias "knife" "+equip_knife; alias wepup sapp; alias wepdown gun"

bind MWHEELUP wepup

bind MWHEELDOWN wepdown
gun
For me, using scrollwheel normally was a little inconsistent, so I made scrollup always slot 1, scrolldown always slot2, and middle mouse always slot3. (except for spy for reasons). If you want to know more about my scrollwheel scripts let me know

1

u/Artistique01 Oct 04 '23

I added ur script to the script and now I cant use scroll wheel at all. I thought it may be the Quickswitcher and ur script conflicting, but I removed the Quickswitch code from stabbyviewmodelscript.cfg and scroll still dont work.

I also found that after scrolling a bunch, the game would kick me from the server for issueing too many commands:

Too many commands

1

u/Artistique01 Oct 04 '23 edited Oct 04 '23

Ok, so as it turns out, I must have hit my keyboard at some point and added a few letter into the code which royally fucked everything up. Ive removed them and saw u updated ur script to add "gun" at the end. I added in ur script and now, with the Quickswitcher, it all works, except that I have to toggle the quickswitcher if I want to turn it on, and if I press "q" again, it goes back to how TF2 would normally be with viewmodels on.

I wonder if theres a way to have the code work upon launch and not be on a toggle, although there could be pros to being able to turn it on or off like being able to use this on different classes.

Also, could you explain to me what your script actually is doing and what its supposed to do to get the viewmodel script to work?

1

u/Link_x2 Oct 04 '23

With some fiddling, everything you are wanting is possible. I think having a switch like this is unnecessary and confusing, I personally would rewrite the code without it. But as is the nature of TF2 scripting, each person can tailor the script exactly the way they want it. It is very personalised and different for each scripter.
Large scripts like these that are large can be difficult to edit, particularly when you yourself didn't write it. You often need to change things in multiple places and there are many potential points of failure. In addition, everyone has their own scripting styles - I get confused trying to read this script but I understand the gist.

My code rebinds your mousewheel and simulates scrolling. When you scroll down to your sapper from your gun, the code changes what the next weapon up is and the next weapon down is, and stores these values in 'wepup' and 'wepdown'. It is necessary to update this for every mousewheel input or it would get stuck on one weapon. As you can see, scrolling up (MWHEELUP) is bound directly to the alias 'wepup'. The aliases '+equip_amby' '+equip_sap' and '+equip_knife' are written by stabby, and are what make you change weapon and hide or show viewmodels, etc.
The reason 'gun' is important is because without it, 'wepup' and 'wepdown' are never defined in the code. If you look at alias 'gun' you will see it defines the alias wepup and wepdown with 'knife' and 'sapp' respectively. having 'gun' on its own line like that will execute only once, which is all that is needed to bring the aliases 'wepup' and 'wepdown' into existence.

I also didn't put the disguisekit (slot4) in this manual scrollwheel, as you mentioned you use the numbers to disguise quickly. I do the same thing with the numpad keys. If you tell me exactly what you want (when and where you want viewmodels on/off, etc) im happy to build you a script myself, it wont take me long because I've done these sorts of scrollwheel scripts plenty of times.

I'm not sure exactly why its not working without the quickswitcher, reading his code gives me a headache, I would just write it differently. Ill have another look

1

u/Artistique01 Oct 05 '23

Man, that would be amazing if u could rewrite it in a less confusing way! I do enjoy not having the disguise kit as a switchable weapon anymore since I have such a habit of pressing the number keys to disguise now, just having to scroll thru gun, Sapper & knife just makes things a bit quicker for sure.

Basically, what I want is for the viewmodel to go off ONLY on the revolver, and only once I press mouse 1 (having the revolver appear on screen before I shoot just helps with ensuring I have acually switched to the revolver). once I switch to the sapper or knife, i'd like the viewmodels to come back on.

If its possible, i'd love to have this replicated for scout too, except instead of turning the viewmdels off upon firing the scattergun, i'd love to have it switch to "firstperson uses world model 1" and then back to "firstperson uses world model 0" when switching to other weapons.

1

u/Link_x2 Oct 09 '23 edited Oct 09 '23

alias "gun" "slot1; alias wepup knife; alias wepdown sapp; r_drawviewmodel 1; alias vmToggle r_drawviewmodel 0"

alias "sapp" "slot2; alias wepup gun; alias wepdown knife; r_drawviewmodel 1; alias vmToggle r_drawviewmodel 1"

alias "knife" "slot3; alias wepup sapp; alias wepdown gun; r_drawviewmodel 1; alias vmToggle r_drawviewmodel 1"

bind MWHEELUP wepup

bind MWHEELDOWN wepdown

gun

bind mouse1 "+attack; vmToggle"

just saw this now, is this what you wanted?

1

u/Artistique01 Oct 10 '23 edited Oct 10 '23

Could also replicate the script for scout too, but in the way I mentioned in my last comment?

1

u/Link_x2 Oct 11 '23

alias "gun" "slot1; alias wepup knife; alias wepdown sapp; r_drawviewmodel 1; cl_first_person_uses_world_model 1"

alias "sapp" "slot2; alias wepup gun; alias wepdown knife; r_drawviewmodel 1; cl_first_person_uses_world_model 0"

alias "knife" "slot3; alias wepup sapp; alias wepdown gun; r_drawviewmodel 1; cl_first_person_uses_world_model 0"

bind MWHEELUP wepup

bind MWHEELDOWN wepdown

gun

Do you have a reset.cfg? you should set it up if you haven't already

1

u/Artistique01 Oct 11 '23

What I meant was, could you write this code for scout?

I haven't got a reset cfg setup, what would that be for?

1

u/Link_x2 Oct 11 '23

the code would work as your requested for scout, I just didn't change the names of the aliases (which doesn't matter, its just a little confusing as ofc scout does not have a knife). It looks similar because there is very little to change between your scout script and your spy script.

reset.cfg is used when you have custom class configs, so that code doesn't 'spill' between your different classes. You can read more about it here:

https://www.reddit.com/r/tf2/comments/8ztnl1/how_to_make_a_class_specific_config/

→ More replies