[friagram]

Is this by design now or something?
batallion's backup, quick fix, etc keep their wearables when using the TF2_RemoveWeaponSlot or TF2_RemoveAllWeapons natives

seems RemovePlayerItem(client, weaponIndex); does nothing

[Powerlord]

Originally Posted by friagram Is this by design now or something? batallion's backup, quick fix, etc keep their wearables when using the TF2_RemoveWeaponSlot or TF2_RemoveAllWeapons natives seems RemovePlayerItem(client, weaponIndex); does nothing

I've been hearing this is an issue as of late. Blocking it in a TF2Items_OnGiveNamedItem hook should block it completely, though. Although I've heard that's not blocking Action slot items these days.

[friagram]

I just edited the tf2_removeweaponslot stock for now..
I check if the extra wearable prop is valid ent and kill it if it is.
Not sure if this was the best way to do it, but it works for now.

Unfortunately I can't always use ogni because the client may already have the item when I need to remove it in post inventory. guess I could like.. Trigger a regenerate and break recursion, but that seems sloppy.