UText3DComponent's Text property access: UE 5.3 broke BP setters. UE 5.6 unneccessarily broke compatibility and incorrectly removed BP getters.

Class UText3DComponent from the "Text 3D" plugin contains a "FText Text" member which must be set through a SetText() function to correctly update the component's internal state.

Up to UE 5.2, "Text" was a public member exported as BlueprintReadWrite, and "SetText()" was a public function exported as BlueprintCallable and marked as the BlueprintSetter for the Text property. This was properly encapsulated in BP but not in C++.

CL 25942929 on june/23 made "Text" a protected member, improving encapsulation in C++. However, it also dropped the BlueprintSetter specifier and marked SetText() as deprecated. It included a non-BP-exported GetText() function and added the Setter and Getter specifiers for the Text property, maybe under the impression that they would serve the same purpose as BlueprintSetter and BlueprintGetter. Unfortunately, this broke encapsulation on BP, allowing users to bypass SetText() and set the Text property directly.

CL 40963239 on march/25 rightfully undeprecated function SetText(). However, it also dropped the BlueprintReadWrite specifier from the Text property and did not add BlueprintGetter or BlueprintSetter. This unneccessarily broke compatibility with existing blueprint code that used to get/set the property, and actually made it impossible for blueprint code to get the property value. This is still the current state in the latest source version.

The suggested fix is to export GetText() with the BlueprintGetter and SetSext() with the BlueprintSetter specifier, and also add BlueprintGetter=GetText and BlueprintSetter=SetText to the Text property.

Note: Other properties also suffer from missing BP getters and/or setters

The problem is quickly and easily verifiable by inspecting the header code. Alternatively, the missing getter can be verified by adding a Text3DComponent to a blueprint and attempting to access its Text property. The compatibility break can be verified by adding a Text3DComponent to a blueprint in UE 5.5 and using direct set/get nodes on its Text property, then migrating the project to UE 5.6 and observing the failure to compile the BP.