Since the "Last Stand" Update the following weapons have skins:


I'm gonna show you how to make use of those skins in Hammer.

Add an "Weapon_*******_Spawn entity to your map.
Set both the Skin and weaponskin setting to the same number.


Only exception is the original skin.
That would be skin 0, but weaponskin -1. Not sure why, that's just how it is.

"Skin" is the worldmodel skin
"Weaponskin" is the viewmodel skin.
If the numbers don't match (except 0 and -1) your worldmodel and viewmodel will have different skins.

Say you have an entity which picks the skin, either a logic_case, a button or a trigger.
Unfortunately the "weaponskin" I/O setting does not exist like it does for "skin".

First give your weapon spawn entity a name, so that another entity can reference and modify it.


In in the Output section of your button, relay or whatever, add the output "skin" with the number of the skin you want and "AddOutput" with "weaponskin X" where X is the number of skin you want.

You can use this system to also just add your own weapon modification that has X amounts of skins, or replace existing skins with your own textures
Say you port a CS:GO map with 30 skins for the AWP, it would be possible.
Of course the modified weapon model or texture must be shipped with the campaign.
Using a custom model will force that weapon onto anyone, no matter what weapon mod they have installed. That's a bad idea to do.

Here's some info on how to ship content with your campaign, while only having that content being used on your campaign maps.

https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=1769855780