ozxybox
commented
3 months ago Marked as low priority, as this behavior can be replicated via instances or prefabs. Marked as size medium, as this would require adding new custom UI (which hasn't been ported to Qt yet for the ent props) and integration with the map compilers (as we wouldnt want this to be done at runtime). Potential wontfix?
Which component should be improved?
Other
Describe your suggestion
In the context of following suggestions: https://github.com/ChaosInitiative/Portal-2-Community-Edition/issues/807 https://github.com/ChaosInitiative/Portal-2-Community-Edition/issues/808 https://github.com/ChaosInitiative/Portal-2-Community-Edition/issues/809 https://github.com/ChaosInitiative/Portal-2-Community-Edition/issues/810
A config system where each config file contains custom values for each entity keyvalue that has anything to do with the customization of a relevant entity class, like the ones mentioned above - paths to custom VFX materials, sounds, colors, particle systems names etc. The configs would then be picked up by the entity in hammer and hammer should be able to save current entity settings to a config. This would make it possible to apply complex configurations by simply picking one from a list in hammer, instead of having to copy-paste an already configured entity around from one of your maps or set it up manually again.
These configs would be stored somewhere in the scripts/ folder and custom maps would be allowed to pack their own unique configs, that take priority over the in game ones (unless they're trying to replace a default P2 config).