Quasimodem
New member
Hello, I've recently updated my project to Unity 2018.3 and Behavior Designer 1.6.1. Most things seem to be working smoothly, however I'm seeing some worrying behavior with serialized fields within my tasks becoming unhooked after editing the prefab they refer to.
For example, I have a custom Spawn action that takes a prefab to spawn:
I can drag a prefab ("Down" in this case) into that field, no problem. However, as soon as I edit the "Down" prefab (via the new 2018 nested prefab editor), that field suddenly becomes unhooked! And not just in this one action, but all Spawn actions everywhere. No good!
A few observations:
For example, I have a custom Spawn action that takes a prefab to spawn:
I can drag a prefab ("Down" in this case) into that field, no problem. However, as soon as I edit the "Down" prefab (via the new 2018 nested prefab editor), that field suddenly becomes unhooked! And not just in this one action, but all Spawn actions everywhere. No good!
A few observations:
- I've verified that Down's guid hasn't changed (which as far as I understand is how serialized references work).
- Although the type of this field (in this case) is a SharedVariable<Entity>, it still becomes unhooked even if it's a normal Entity. However, if the field is of type GameObject, Transform, or other built-in Unity types, it correctly maintains its reference. There's nothing special I can see about Entity; it's just a regular-looking subclass of MonoBehaviour.