Hello again!
I’ve been having a lot of success with the system so far, but now I’ve hit an odd issue. I tried to package my game yesterday and failed, and after some time looking through the crash log and getting feedback from Epic staff, it looks like this add-on is the source of the problem. (Or one of the sources, at any rate.)
Here’s the offending bit in the log:
UATHelper: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2016.10.13-14.22.12:035] 0]LogBlueprint:Error: [Compiler BPC_SchoolDio] Error This blueprint (self) is not a TRASHCLASS_BPC_Dialogue_1387, therefore ' self ' must have a connection. from Source: /Game/BlueprintDialogues/Blueprints/BPC_Sch
UATHelper: Packaging (Windows (64-bit)): oolDio.BPC_SchoolDio
I’m not sure what any of that means, but I have a hunch.
For a little while now I’ve run into a weird bug where, every time I open the project, the child components that inherit from BPC_Dialogue refuse to compile. That “BPC_SchoolDio” you see in the log is one of the children I made. All I need to do is open BPC_Dialogue and compile it, then compile the children, and bam, they work.
So, easily fixed in the editor, but how do I fix things for a packaged project?
If you’ve seen anything like this or know how to proceed, please let me know. Thanks for being a cool cat, Grogger.