Turns out we couldn't just destroy an MMCC child entity and read in its serialized counterpart (as discovered here - https://github.com/bryanedds/Nu/releases/tag/v13.2.1). This resulted in the MMCC initialize event handlers in being destroyed unrecoverably. So for now, only MMCC parent entities can be serialized. Hopefully we can figure out how to make these two systems play together more seamlessly in the future.
EDIT: and most importantly, let's also make sure that supporting this is actually what we want. There are some nice advantages to the current implementation this issue attempts to change.
Turns out we couldn't just destroy an MMCC child entity and read in its serialized counterpart (as discovered here - https://github.com/bryanedds/Nu/releases/tag/v13.2.1). This resulted in the MMCC initialize event handlers in being destroyed unrecoverably. So for now, only MMCC parent entities can be serialized. Hopefully we can figure out how to make these two systems play together more seamlessly in the future.
EDIT: and most importantly, let's also make sure that supporting this is actually what we want. There are some nice advantages to the current implementation this issue attempts to change.