Firstly, please take the time to try to type properly. We can forgive some mistakes, but when a post that long (I'm specifically talking about reply #9) doesn't contain a single punctuation mark it makes it difficult to read and respond to properly.

I'm not asking all of the code just the process of how a engine should work like what files should be loaded and some of the math

[...]

just need to know the math and the syntax

You load whatever files you need. You use whatever maths is required for your game. The syntax will be the syntax of whatever programming language you are using. If you had more specific questions (i.e. "I'm trying to implement [some functionality] using [some programming language] and [some particular engine], here's what I've tried, what am I doing wrong?" or even "I'm trying to do [some specific task] with [some engine] and have no idea how to start, help!") we could help you, but at the moment these questions are just so broad and general that they're completely meaningless and impossible to answer.

The fact that you're asking this very clearly shows that you have not yet learned the basics properly, and if we give you code samples or random instructions on the usage of an engine it will not be helpful to you. You really should try actually making a simple 2d game -- just a game of Pong, with simple blocks and a circle for graphics so not having art isn't a concern -- but without using existing code.

Pong is a really simple game, but it contains a lot of the basics you'll need for a top-quality MMOG: a game loop, input handling, basic collision detection and response, etc. If you can't make Pong, you can't make your MMO. I know it sounds silly. I know it might not be exciting to make Pong. But honestly, if you can't do that, you aren't ready for the things you're asking for, and it'll just be a lot of technical gibberish you're unable to understand.

Start from the basics.

Try to make Pong. If you do it properly you'll actually have a much better understanding of what to do next. You can't just skip over this basic stuff because you think you would be able to do it if you tried -- by actually doing it you'll learn the answers to some of your questions, as well as having a better idea of what specific questions you should ask next.

I kinda know what you are asking for.

I think your assessment that your know a lot about programming is not quite right, though. You probably have a solid idea of the basics, which certainly is not nothing, but there is still a lot of big picture knowledge you need to learn.

Usually I would agree that learning to program / thinking like a programmer in general is more important than examples of how something is done.

But I didn't make any progress until I found a follow-along-tutorial that happened to explain the thoughts / reasoning behind the taken steps.

So I actually like your take on learning. I read "The First 20 Hours" (first20hours.com/?) and love the message:

You should only learn enough theory that you can start doing something right away (and before that you should know your goals ... more detailed than you have outlined them).

You need to break your goals down into chunks, as many others here have said here. Making smaller games will help you get that big picture knowledge.

Unfortunately I don't know of any tutorials that teach the reasoning ... and I don't know of any source code on Github that you could analyze.

Maybe somebody can point something out.

Maybe you can also prove that you have the big picture knowledge that we think you lack.

I think Nehe might still be a place with some info on 3D Graphics programming (http://nehe.gamedev.net/). The codebase was improved ... not sure if all links point to that codebase. Maybe somebody here has an opinion on the state of those resources?

Adams makes a bunch of good points and his answer is very honest and true. I would take that answer to heart and start learning because you have a lot of hard work ahead of you.

Writing code that someone else has already shown you is not programming.

Programming is writing your own code to solve your own unique challenges for your individual project.

I wanted to point out those 2 sentences because everyone tells me, and not just me, that you shouldn't reinvent the wheel, you shouldn't write what someone else already has written, to save time, and at some cases to save money.

How would you respond to this statement?

I wanted to point out those 2 sentences because everyone tells me, and not just me, that you shouldn't reinvent the wheel, you shouldn't write what someone else already has written, to save time, and at some cases to save money.
How would you respond to this statement?

I'm obviously not the person this was directed to, but if I might offer a response anyway...

There's a difference between getting things done and learning.

Reinventing the wheel is (usually) a bad idea when you're trying to get things done. You're spending time that doesn't need to be spent, and unless you spend a lot of time and effort and are very skilled will probably produce a lower-quality replacement for the existing functionality.

When you're learning however, it's an excellent idea to make your own version of things as a learning experience -- you can compare to a more professional solution to judge the quality of your work, and you'll learn from figuring out how to implement it yourself. You'll also end up with a better appreciation for the existing solutions.

You don't learn by cutting and pasting someone else's code samples -- you learn by writing your own. You will however still take advantage of existing libraries (rather than reinventing the wheel) such as SDL/SFML/Allegro, etc.

I wanted to point out those 2 sentences because everyone tells me, and not just me, that you shouldn't reinvent the wheel, you shouldn't write what someone else already has written, to save time, and at some cases to save money.
How would you respond to this statement?

I'm obviously not the person this was directed to, but if I might offer a response anyway...

There's a difference between getting things done and learning.

Reinventing the wheel is (usually) a bad idea when you're trying to get things done. You're spending time that doesn't need to be spent, and unless you spend a lot of time and effort and are very skilled will probably produce a lower-quality replacement for the existing functionality.

When you're learning however, it's an excellent idea to make your own version of things as a learning experience -- you can compare to a more professional solution to judge the quality of your work, and you'll learn from figuring out how to implement it yourself. You'll also end up with a better appreciation for the existing solutions.

You don't learn by cutting and pasting someone else's code samples -- you learn by writing your own. You will however still take advantage of existing libraries (rather than reinventing the wheel) such as SDL/SFML/Allegro, etc.

Thank you. That's what I wanted to hear. Those are exact my thoughts.