Hey there,
Yes, there is an experience bug here where when you change the children, the index gets reset to 0, and the name displayed will not match the internal name of the enum. The primary design is that child graphs are intended to import properties from the parent or from sibling graphs. For each child graph that is setup, it’s best to setup the variable in the parent, export it, and then import it on the children.
[Image Removed]
I’ve logged a bug for this case, and I will also suggest some potential warnings or validations. In terms of what is the future intention here, this particular version of this case is interesting because you’re adjusting the enum list and basically blocking what is available for that body type case. Depending on your setup needs, I would suggest that you allow all options, but block those that are available in your UX for that particular character based on external data. However, hopefully, with the UX fix, you’ll be able to detect and read it through the customizable graph if necessary.
Dustin