I’m not sure why that isn’t working for you. One thing you could try doing is putting a breakpoint inside FEnumEditorUtils::UpdateAfterPathsChanged and loading your blueprint that uses the enum. You should be able to see what names it’s expecting inside that function. You could also try using the long form of the names (eg “Enum_AI_CombatStates::NewEnumerator0”)