I’ve noticed an annoying pattern over the last few updates of UStructs no longer being UStructs. (As in, they’re just structs, which can’t be UProperties or parameters in UFunctions).
This causes an annoying chain of having to either replace the old UStructs with functionally identical custom UStructs, or hiding UProperties and UFunctions from blueprint.
While this isn’t usually a big deal, in 4.17, there have been some of these that just make no sense. For instance, FComponentReference’s main job appears to be a way to expose a way for one component to reference another in a way that can be set in the editor. But as of 4.17, this isn’t a UStruct any more, which means the editor can’t see it, so what’s the point?
Does anyone know what’s going on with this? Having to work around or replace the functionality of these UStructs to be able to expose them to the editor again is actually accounting for the majority of the time I spend updating engine versions, and it seems like it’s getting worse every release.