Plugin development handcuffs

Not to beat a dead horse, but how is it that UMaterialParameterCollection and UMaterialParameterCollectionInstance are MinimalAPI? It’s closed-off (only available in blueprints) basic classes like these that are kind of maddening. It’s hard to imagine that someone hasn’t mentioned or requested the exporting of these classes’ methods for use in c++ at least in passing. Requiring that developers request the opening of these methods is highly problematic - which leads to another item to add to my previous post’s list…

  1. We pull Unreal’s codebase from GitHub and disperse through perforce so when someone comes across a MinimalAPI gate they simply make the change within the perforce database - then when we next pull from Unreal (based on when 3rdParty middleware has also been updated) we have to go back through and reintegrate all the MinimalAPI related changes. At that point, we are already scrambling to get everything back up and running and have no time to research, separate, and request changes through GitHub.