>This is for programmers only:
I think this comes from people who try to learn programming while making games. If you can’t identify an error from a stacktrace or you are afraid to look into the engine’s source code or you are not able to use google to find an answer to your problem or you are not willing to change engine versions to get that feature that you want or you can’t be descriptive when writing questions or you are not willing to “read this tutorial first, then ask questions on google and then on actual people” state of mind or…i could go on… it’s nobody’s problem that you can’t get the hang of the engine.
Don’t expect this piece of software to be tolerant of your general lack of knowledge on the fields of: CS , physics, math (&geometry) , graphics , audio. Heck, I’ve seen people not willing to learn to speak english but still want to be into gamedev efficiently! If you want to learn to make games with an engine you should already know how to speak english ,write some code and know math.
</rant>
I know you get frustrated because the engine is “unstable” or your pak size on android is big or steam doesnt work in a packaged build or some random issue. Small parameters that most of the people probably ignore can cause a lot of problems but these parameters are what separates the pros from the noobs. You need to learn things from the ground up and there are plenty of resources to do that. I’d recommend thenewboston.com’s intro videos to programming and then some game making with a high-level wrapper for graphics and physics. After that , math for game developers playlist on youtube and ALL khan academy math classes. ALL OF THEM. If you don’t udnerstand something from a random video google it, find it and learn it. Then you can safely transition to the engine side.