Dynamic Gameplay Effects being deprecated?

Development Programming & Scripting C++
,
1

Is Epic beginning to deprecate creating Gameplay Effects dynamically at runtime?

I ask because I recently the compiler is complaining about the line: Effect->StackingType = EGameplayEffectStackingType::AggregateBySource;

'UGameplayEffect::StackingType': Stacking Type will be made private, Please use GetStackingType. - Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.

Obviously it’s not unusual for Epic to move member variables to the private section in engine code and implement public Setters/Getters.

The problem is the public setter is defined like this in GameplayEffect.h

#if WITH_EDITOR
void UGameplayEffect::SetStackingType(EGameplayEffectStackingType InType)
{
    PRAGMA_DISABLE_DEPRECATION_WARNINGS
    StackingType = InType;
    PRAGMA_ENABLE_DEPRECATION_WARNINGS
}
#endif

So, EditorOnly for some reason.

Why doesn’t Epic want people changing the stacking type in C++?