Quote:
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.
Code:
{
"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