I’d like to propose a complete rework to the Volumes object in condos.
Currently, to define multiple different properties to associate with one specific area requires a distinct volume for each of these property types - sound volume, location name, post processing effects, etc. This can quickly lead to stacking many volumes all on top of the same area, and it becomes very tedious to edit them as more get added to the same area.
Instead, I propose one single type of volume that you can assign properties to - either via tabs in its object properties, or connections (by including a new type of I/O object that can apply properties to areas remotely).
For example: You build a room and add a location volume defining its boundaries. You add a name to it (this and other basic things would probably be built into the volume’s object properties, with a toggle to not apply a name to that volume), and to give it post processing, you place a new “Post Processing I/O” object somewhere in the map, edit its connections, and add a connection to apply it to that location volume - as well as any other volumes you want those particular properties applied to (applying the properties via connections in this way would allow users to make “templates” within maps, to apply to several areas at once without having to redefine all the same attributes each time), then you can do the same with new I/O objects for the other properties - sound, sky, etc.
I think this would be a more elegant solution to the current system, which can be very unwieldy when editing large maps.