Hmm.. I understand what you mean, REDNSX. I remember being a newbie to Game Editor and I remember being very confused about the whole engine when I started.
A complete tutorial of making a simple game would be, (if everything is explained carefully) a good way to learn the basics of the program.
There is just one thing that could cause problems..
And it's that I've used Game Editor for a quite long time and I have evolved as a programmer
and when I would start making a tutorial, I would want to teach making the game the way I see to be the best. And now here comes a problem. It will easily get to be too difficult for new people and my code-centered style of making games could make them too confused to try to continue with Game Editor. The thing is that I don't want to teach people what I see is "wrong", or in other words, a bad way of making a game.
It's like there is two ways of using Game Editor.
The first being the way with the minimun amount of code and maximum amount of usage of the built-in functions.
And the second being the way with the maximum amount of things done through code, as it is easier to handle.
I wouldn't like to teach the first way because using it the game projects will turn to horrible messes... :/
I don't know if I am going to make this tutorial. At least I'll finish with the other ones first because this would take a lot time.