The problem you have is that you keep biting off more than you can chew. We keep telling you to start with the basics, and every time you come back saying you'll start by making an engine, because you know some of the language's syntax.
I didn't get to the point where i can spot vulnerabilities like these until years after i started programming. I started small, failed at what i was doing, learned why i failed and how to do better and succeeded.
Based on your responses here you can't handle failure very well, and your response is to bite off more than you can chew again a few days later.
You really need to start with the basics. Even if that means learning how to write if statements again, it's how you start with learning any programming language.
If you want to make an engine you should start by looking at and using existing engines, preferably in the language that you're intending to make your own with.
Once you have a strong grasp of the syntax of the language and experience with one or more engines you'll have enough knowledge to start making an engine. You'll still fail at first, but you'll be able to learn from your mistakes, instead of just throwing your arms up and saying "i can't even understand words like what you are spewing out".
It'll take time, but if you really want to do this you'll get there eventually. How long it takes depends on how much time you spend on it, as well as how motivated you are and how much you already know.
If you have a problem you just can't fix you can always ask for help, and if it's too stressful you can take a step back and come back later. Giving up at the first sign of trouble won't get you anywhere.