Hello,
Thanks for reporting this. I was able to reproduce this problem. This appears to be happening when you swap the target SubTree reference when the SubTree Node in which you swap the reference is already *Running*.
I will of course need to fix that and add a failsafe check, but please avoid swapping the target SubTree reference (either manually or through variables) *while it is Running*, because it will result in unintended behavior until I fix this.
Thanks again for the report.
Join us on Discord: https://discord.gg/97q2Rjh
Login
Register
By registering on this website you agree to our Privacy Policy.