Is it possible to make it so that any newly created blueprint functions are private/protected by default?
Considering c++ by default does this. I was wondering if it’s possible to enforce this on the blueprint side to enforce better practices?
Newly created variables would be another thing I would consider doing this to.
Tell me if you think this is a horrible idea and why.
I think it’s a great idea, with automatic getter and setter functions optionally generated.
That said I don’t think it’s likely to happen, nor const functions/parameters. Not because there’s any specific resistance against them but rather because of priority.
the marketplace plugin “blueprint assist” has project settings to enable these features. Also can generate getter/setters as well.
This plugin is pretty amazing, thank you so much for the recommendation!
I agree that this seems super useful. Thank you for the suggestion. Will look into it.