Which component should be improved?
Other
Describe your suggestion
Right now, both game_sounds_manifest.txt and soundscapes_manifest.txt have a wildcard feature present by default in their files, to allow workshop addons to easily include their own game sounds/soundscapes, without having to pack them into .bsp directories or replace files directly. It would be a nice addition to extend this wildcard feature to surfaceproperties_manifest.txt to allow addons to insert their own custom surface properties for custom assets.
Two immediate use cases of this for me would be my EverythingPBR addon and Source 2 Footsteps addon: new surface properties in EverythingPBR would allow for a wider variety of footstep/physics sounds on my new assets to enhance immersion, and new surface properties in Source 2 Footsteps would allow directly porting Source 2's surface properties, instead of replicating them with sound replacements.
Which component should be improved?
Other
Describe your suggestion
Right now, both game_sounds_manifest.txt and soundscapes_manifest.txt have a wildcard feature present by default in their files, to allow workshop addons to easily include their own game sounds/soundscapes, without having to pack them into .bsp directories or replace files directly. It would be a nice addition to extend this wildcard feature to surfaceproperties_manifest.txt to allow addons to insert their own custom surface properties for custom assets.
Two immediate use cases of this for me would be my EverythingPBR addon and Source 2 Footsteps addon: new surface properties in EverythingPBR would allow for a wider variety of footstep/physics sounds on my new assets to enhance immersion, and new surface properties in Source 2 Footsteps would allow directly porting Source 2's surface properties, instead of replicating them with sound replacements.