I’m not talking about how it could be implemented. This was meant as a suggestion of an improvement, a feature. I know how it works but what you are saying is to basically use hard coded default values and references. That is for many reasons very bad programing.
What I mean is maybe it would be convenient to allow setting default values in the editor for the c++ classes and I don’t mean changing the source code or the actual c++ classes in any way. Maybe that can be implemented by creating assets in the background for the classes you want to set defaults for or for all as you said, there are probably more ways of doing it also. As I said, using config isn’t an option for me but it is almost convenient compared to creating the whole c++ class hierarchy in blueprints. Creating the whole c++ class hierarchy in blueprints needs to be done at the moment to set default values in the editor for the classes, so the implementation you suggest wouldn’t be any worse than it already is today. The whole c++ class hierarchy must already be recreated in blueprints to set default values, just that it must happen manually.
Also I never understood why the c++ class hierarchy appers in Content Browser as it is now. You can’t really do anything with it plus that if you want to go through the project’s file hierarchy, why would you start the editor instead of using visual studio. Is it some sort of bookmark or shortcut system?