[Chdata]

So in VSH I've been having botkiller skulls stick to EVERYTHING despite having the latest version of TF2Items (1.5.3).

Wot's happening?

I'm fairly sure it's tf2items, cause this doesn't happen if I disable Hale and thus the code that uses that doesn't run.

[xXDeathreusXx]

I'm noticing this too...

What happens is on hale check it changes you to soldier, but for some odd reason instead of no viewmodel, or just the stock rocket, if you have a botkiller, it will load up your botkiller, and when it fixes you up, it glitches, and you can continue to see the botkiller part, which then persists through the map duration.

My guess is something changed or glitched along the way with one of the new tf2 updates

[Chdata]

not just hale, but any time you use a botkiller weapon, it'll stick to all of your classes

[xXDeathreusXx]

Originally Posted by Chdata not just hale, but any time you use a botkiller weapon, it'll stick to all of your classes

This I don't know about, as it hasn't happened to me, but it does happen when I am picked for hale

[BBG_Theory]

it is not a FF2 or Saxton hale problem, it is from using tf2items with these weapons equipped.

[friagram]

The xmas update changed how wearables works (weapn extra wearables, cosmetic items, etc). It's now required that you sdkcall removewearable on them instead of kill. This will get rid of botkiller fobs properly.

[Chdata]

Ah. I'm not sure how I'd edit vsh 1.42 to do that though ;c

[Powerlord]

Originally Posted by Chdata Ah. I'm not sure how I'd edit vsh 1.42 to do that though ;c

I wrote a sample plugin to call EquipWearable and RemoveWearable a while back (before RemoveWearable was useful for something). The offset hadn't changed last I checked.

The IsWearable example part of that plugin could use some work, though...

Also, TF2Items 1.6.0 has had dev versions for a while, and I thought those were required due to the item changes introduced in one of this year's updates (the weapon rebalancing update).

[friagram]

Yes, removewearable works.
As I said, just call that instead if kill.
But now you also have to do it on equipped weapon wearables, every time you use removeweaponslot. So you may as well just edit your tf2stocks.

I was thinkng of posting what I have here, but not sure if it is a good solution, or if it would be used properly.

Basically it just initializes the sdkcall in the include the first time removewearable is called - by name or by removeweaponslot, and the keeps using that. Not ideal. I think tf2 needs a real native for this, and removeweaponslot should call it.

[Chdata]

So basically I could take Powerlord's code, edit my tf2_stocks to check if the weapon is a tf_wearable...

Are botkiller jigglyparts their own entity (separate from the weapon) or something? Wut?

Edit:

So I guess m_hExtraWearable would have to do with that. Time to prepare a big list of weapons that have that I guess. Unless there's a better way than just calling removewearable for every index that matches one with extra stuff on it.