I was adding a custom enum to my pawn. I was able to use PIE a number of times but suddenly the editor crashed.
If I tried to re-open my project the editor crashed again. In order to get the editor to start again I had to move/rename my default editor map and click on not to reopen assets.
And now the fun part:
If I tried to open any Blueprints with a reference to my enum the editor crashes again, but if I open the enum first everything is fine until I restart the editor.
LogEnum:Warning: Enum Text EKaoriGameUnitType::NewEnumerator0 for Enum EKaoriGameUnitType failed to resolve to any value
LogEnum:Warning: Enum Text EKaoriGameUnitType::NewEnumerator1 for Enum EKaoriGameUnitType failed to resolve to any value
LogEnum:Warning: Enum Text EKaoriGameUnitType::NewEnumerator2 for Enum EKaoriGameUnitType failed to resolve to any value
LogEnum:Warning: Enum Text EKaoriGameUnitType::NewEnumerator3 for Enum EKaoriGameUnitType failed to resolve to any value
So I created a new enum and used the replace reference on delete function to replace the old enum with the new one but that didn’t work.
LogBlueprint:Error: [compiler] Error Default value 'NewEnumerator2' for UnitType is invalid: 'Expected a valid unsigned number for a byte property'
LogBlueprint:Error: [compiler] Error Default value 'NewEnumerator1' for UnitType is invalid: 'Expected a valid unsigned number for a byte property'
I had to delete EVERY variable and input or output from functions of this enum type in order to get my project running again.
A recovery feature that lets you easily identify which assets are causing the error with a way to correct corrupted blueprints would be nice rather than just crashing the editor
