Blueprint Dialogue System

[Cinebeast]

@Grogger;609328

Check the references of the three files in question (right click them in the content browser and hit the show references button). If the parent is aware of the child class (possibly even indirectly), you’ll have a circular reference. If this is the case, you can likely work around it by using interfaces or inheritable functions in the base class.

Okay, it looks like BPC_Dialogue is, in fact, aware of its children. I have no idea how, though. I don’t cast to them, I don’t have any variables referencing them, nothing.

@Grogger;609328

As for updating, ideally, you would never change the dialogue system files and instead only inherited from them. If you haven’t changed the base files, you can update by simply migrating over the new files, if you have then anything you’ve changed in the base files will likely be lost while updating (there’s no way around this AFAIK, BP assets can’t merge differences unfortunately).

You’re right, the transition was pretty smooth. Only thing that got overwritten was my custom UI, but it only took a few minutes to change it back to how I wanted it.