This isn't really a bug so much as "this is confusing and if we can come up with a better solution let's do that"
The example is that I selected a target for a TeleportEffect which got ../../Markups/TeleportDest that was the correct relative path based on the current node. But when we passed the configured effect chain into the scene's subtree the relative path breaks since we change nesting levels but keep the same ../../.
For the time being I'm just going to rewrite TeleportEffect to extract targets via path.find("Markers/") and resolve via cur_level parameter.
But generally this speaks to a concern about anything we have that uses relative paths in the scene tree.
This isn't really a bug so much as "this is confusing and if we can come up with a better solution let's do that"
The example is that I selected a target for a TeleportEffect which got
../../Markups/TeleportDestthat was the correct relative path based on the current node. But when we passed the configured effect chain into the scene's subtree the relative path breaks since we change nesting levels but keep the same../../.For the time being I'm just going to rewrite TeleportEffect to extract targets via
path.find("Markers/")and resolve viacur_levelparameter.But generally this speaks to a concern about anything we have that uses relative paths in the scene tree.