How viable is it to use Slate for cross-scene workflows? I have no fear of any scripting needed to achieve it, but since I haven’t bought the asset yet, I don’t know how well it will behave in that sense. The API Documentation has this SetGroupActorOfName method, which I believe is enough for my needs;

I’d probably just create some sort of global identification at editor-time for gameobjects to be targeted by these cross-scene references, and dynamically attach them to any Cutscenes that need them at runtime when the cutscene starts.

A particular limitation I can see with this workflow is that I don’t know if Slate is capable of working with cross-scene references in editor-time the same way Timeline does, which is to say, allowing you to *pretend it works* when creating the tracks and their bindings (for example by dragging a gameobject from one scene into a Timeline in another), which does work as expected in-memory, with the references dying during serialization. This matters because of the drag-to-timeline use case, as I expect the sequence to exist in a separate scene from the start.

If it doesn’t work the same way Timeline does in this sense, are there any *secret* internal APIs (that I could hack into via Reflection) that would allow me to hijack the behaviour for this dragging a gameobject from another scene into the sequencer so I can bypass it somehow? And would doing that even work? Like, would you still be able to add tracks to groups with “invalid” references such as these the normal way (with the context menu displaying what’s available within that object?