Creating a new Blueprint validator inheriting from EditorValidatorBase will not work until you reboot the editor

Development Pipeline & Plugins
, ,
1

If you create a BP validator it will not function until you reboot the editor.

I believe this is because BP validators are only loaded in UEditorValidatorSubsystem::RegisterBlueprintValidators() which is called only via UEditorValidatorSubsystem::Initialize(FSubsystemCollectionBase& Collection).

Would be great if BP validators were added to the validation system on creation to save content creators from thinking their validator isn’t working to only have it ‘just work’ after a reboot.

2

Steps to Reproduce

  • Open editor & right click in content browser click “Editor Utilities-> Editor Utility Blueprint” & set parent class to EditorValidatorBase.cpp
  • Just set return true on the can validate functions & in the ValidateLoadedAsset function return Invalid
  • Then save an asset & notice that the validator will not run
  • Reboot the editor, it now works
3

Hello [mention removed]​

Thank you for reporting this issue.

I have some good news: While testing this against every UE5 version, I noticed that they fixed it in the main branch of Perforce (5.6).

Immediately after creating the EditorUtilityBlueprint from an EditorValidatorBase and saving, we can see the BP registered as an Enabled Validator:

[Image Removed]This issue will be fixed in the next release!

All the best,

[mention removed]​

4

Still doesn’t work without reboot for me in 5.8.1 if I create it as a regular Blueprint, which I know I probably shouldn’t do in the first place, but some other classes like Editor Utility Actor or Editor Utility Object are getting automatically converted to Editor Utility Blueprints if I do so, yet Editor Validators and some other classes (EU Widgets, EU Tasks) are not. This isn’t a huge problem, but it is somewhat inconsistent.