Default temporary engine effects (HighlightFlash, OneShotAudio from footsteps) to world's __temp slot

[JackTheFoxOtter]

Is your feature request related to a problem? Please describe.

There are various non-persistent effects that are created by the engine, which currently spawn on the root slot of the world by default. The main ones I'm currently concerned are HighlightFlash slots from using FlashHighlightHierarchy node, and the OneShotAudio slots which are for example created by the new footstep system.

This can be a severe annoyance when inspecting the world root in the scene inspector, and make it very hard to select individual slots.

Describe the solution you'd like

I'd like those temporary effects to default to the world's __temp slot instead of the world root.

Describe alternatives you've considered

Manually changing where those effects get parented. That works for the footstep system, but it doesn't work for the FlashHighlightHierarchy node. Generally I'm mainly concerned about the default behavior with this issue though, since I believe the default shouldn't be parenting temporary effects to the root slot of the world, for the aforementioned inspector usability reasons.

Additional Context

No response

Requesters

No response

[shiftyscales]

I think part of your underlying issue could be solved by just having better UI/UX in the inspector itself. #563

E.g.:

• Preventing newly created slots from immediately being added in-line with existing slots in the hierarchy (thereby not inadvertently scrolling / moving the list while the user is trying to work on it)
• Deleted slots could be faded / struckthrough but still visually remain in the hierarchy temporarily until the inspector is refreshed
• We could separate out/sort non-persistent slots separately from persistent ones
• Not requiring a double click to be on the exact same slot to select it or having alternate ways of easily selecting a slot (this could also be useful as an accessibility tweak for users that have difficulty in keeping their hand still / precisely on their target slot)

Being able to specify a slot / space for the visuals to be parented would still be useful- but it doesn't resolve the underlying issue in of itself, as there are a lot of potential sources where slots can be generated / deleted at inopportune times causing difficulty in selecting slots, etc. as you highlighted.

E.g. even just having other users working in the same hierarchy at the same time.