RANT - No Private Variables in Blueprint Classes in your BP Packages

Dear Blueprints Marketplace Vendors,

Please do not specify Blueprint Class Variables ‘Private’ in your BP Packages. I cannot SET these variables in Child BP Classes to extend for my own purposes. If you released a package with Private Variables, please release update removing the private specifier.

Sincere Thanks in Advance

TechLord

PS: Please stop putting Game Logic in the GUI UMG Blueprints

[FONT=courier new]###End Of Rant

If there’s a private field, there must be a public Get/Set function.
If class is designed to be extended then those fields should be “Protected” instead of “Private”, yep.

And what if the intent is that you shouldnt change those variables? Since those may be needed for the internal logic.