While not really a problem at TF2C's current items count, whenever the game eventually receives more multi-class items, the number of weapon entries needed to sustain them will be... quite a lot. As it is, even for otherwise completely identical weapons mechanically, you still need to make entire new entries in order to have, among other things;
A custom Description
A custom World-Model (if using the w / v split system, like most weapons do)
A custom Extra Wearable (unused as of now)
To an extent, this can already be seen with some stocks (namely, the Shotgun and Pistol), as well as the Gunboats. As of right now, we have access to "model_player_per_class" for custom c / v models, which is helpful, as well as "item_class" "saxxy" for an all-encompassing Melee item-class, which also helps.
It would be nice to have further support for so-called "item_description_per_class", "model_world_per_class", and "extra_wearable_per_class", respectively, preferably all functioning similarly to how the existing model_player_per_class works.
While not really a problem at TF2C's current items count, whenever the game eventually receives more multi-class items, the number of weapon entries needed to sustain them will be... quite a lot. As it is, even for otherwise completely identical weapons mechanically, you still need to make entire new entries in order to have, among other things;
To an extent, this can already be seen with some stocks (namely, the Shotgun and Pistol), as well as the Gunboats. As of right now, we have access to
"model_player_per_class"for custom c / v models, which is helpful, as well as"item_class" "saxxy"for an all-encompassing Melee item-class, which also helps.It would be nice to have further support for so-called
"item_description_per_class","model_world_per_class", and"extra_wearable_per_class", respectively, preferably all functioning similarly to how the existing model_player_per_class works.