[FlaminSarge]

Ap-Sap won't spawn because of sapper-handling code that hasn't been extended to it yet. Ham Shank is 1013 and should be fine as long as you have TF2ItemsInfo installed.

[Bitl]

Originally Posted by FlaminSarge Ap-Sap won't spawn because of sapper-handling code that hasn't been extended to it yet. Ham Shank is 1013 and should be fine as long as you have TF2ItemsInfo installed.

Just went ahead and added the Ap-Sap.

Modified version below.

EDIT: Added checks for TF2ItemsInfo.

if (idx == 735 || idx == 736 || idx == 810 || idx == 831 || idx == 933)

if (iItemDefID == 735 || iItemDefID == 736 || iItemDefID == 810 ||iItemDefID == 831 ||iItemDefID == 933) iItemSlot = 1;

[FlaminSarge]

You forgot about the TF2ItemsInfo integration part of it
" if (iItemDefID == 735 || iItemDefID == 736 || iItemDefID == 810 ||iItemDefID == 831) iItemSlot = 1;"
needs to have 933 in there as well, though I added a tf_weapon_sapper check instead.
I'm tempted to make all sappers use tf_weapon_sapper just for differentiation, because Valve updated it so that tf_weapon_sapper works properly for index 735 (instead of glitching out the viewmodel).

[Bitl]

Originally Posted by FlaminSarge You forgot about the TF2ItemsInfo integration part of it " if (iItemDefID == 735 || iItemDefID == 736 || iItemDefID == 810 ||iItemDefID == 831) iItemSlot = 1;" needs to have 933 in there as well, though I added a tf_weapon_sapper check instead. I'm tempted to make all sappers use tf_weapon_sapper just for differentiation, because Valve updated it so that tf_weapon_sapper works properly for index 735 (instead of glitching out the viewmodel).

Just added the checks.

[Mr. Man]

Is there a way to permanently turn off custom weapons? tf2items_customweapons_lowadmins 0 and tf2items_valveweapons 0 doesn't appear to work since they're still able to give themselves such.

[FlaminSarge]

With the upcoming TF2Attributes-based update, I can move a lot of the custom weapons out to the custom config file and use some of the unused attributes to mark them as custom (e.g. the Khopesh Climber). As such, that may not be necessary as I'll just include a tf2items.givecustom.txt file with the custom weapons in it and you can clear them as such. Alternatively, I can include a "disable" key that you can put in the custom config, and when the config is read, any of the custom indices that have the "disable" key will be disabled (example below). I was going to try an admin flag, but managing multiple groups/flags/permissions seems like a pain.

{
   "2171"
   {
      "disable" "1"
   }
}

[mrcodxd]

this is probably a dumb question, but is it possible to give a weapon without it disappearing when touching a locker?
also: I don't rlly understand resetex, can you explain it a bit?
thx

[MasterOfTheXP]

Originally Posted by mrcodxd this is probably a dumb question, but is it possible to give a weapon without it disappearing when touching a locker? also: I don't rlly understand resetex, can you explain it a bit? thx

sm_givew_ex gives permanent weapons that are always given after respawn/resupply/class change/you name it. (Not disconnect though). "sm_givew_ex target weaponid 1" to give it immediately and permanently.

sm_resetex undoes permanent weapons, but not immediately. They won't get the weapon anymore after resupplying.

[404UserNotFound]

Originally Posted by FlaminSarge With the upcoming TF2Attributes-based update, I can move a lot of the custom weapons out to the custom config file and use some of the unused attributes to mark them as custom (e.g. the Khopesh Climber). As such, that may not be necessary as I'll just include a tf2items.givecustom.txt file with the custom weapons in it and you can clear them as such. Alternatively, I can include a "disable" key that you can put in the custom config, and when the config is read, any of the custom indices that have the "disable" key will be disabled (example below). I was going to try an admin flag, but managing multiple groups/flags/permissions seems like a pain. { "2171" { "disable" "1" } }

With this new addition....would it be possible to take the custom attribute coding from Advanced Weaponiser 2 and do some quick recodes and make it work with this plugin?

Because I'd love to mess around with both plugins and see if I can convert some things over from AW2. I looked into the TF2Attributes thing, and noticed how it checks for named attributes, and I figured "Hey, maybe I could come up with something that would give names to the custom attributes, and then have the GW plugin detect those named attributes!"

Looking forward to the new update to the plugin though

[FlaminSarge]

I meant unused attributes, since those are nice markers. You could probably add attributes by just adding new entries in items_game, after which you can check for them existing on an entity via GetAttribute.