Sorry, but I'm a bit of a purist when it comes to tutorials. I like others to try and achieve as high a standard as possible when making them - like I try to.
When reading a tutorial, I don't think you should be able to find spelling mistakes. Yours is a Word document which has a spell checker, so there should be no excuses.
A tutorial should be easily readable by everyone. Older readers (like me) will find all capital letters very hard to read as it reduces the white space - as well as being interpreted as shouting on the internet:
Presentation is a vital part of a tutorial. Unfortunately your lines of code and capital descriptions seem to merge into a tangled mess.
And, as your readers are learning, you shouldn't teach them bad programming habits. Code snippets need to be presented properly with correct indentation so they are as readable as possible.
DB is a procedural programming language. Therefore the last thing you should be doing is telling newcomers to use Goto. What's wrong with doing it properly using only procedures and functions?
Anyone who doesn't know how to do that shouldn't really be writing 'tutorials'...
Also, when you can you should make clear the difference between integer and float variables. Although DB is quite easy going and allows you to say things like:
Scale Object 1,38000,15000,500000
..in a tutorial you should go by the book. If the help files say a parameter is a float then you should use a float:
Scale Object 1,38000.0,15000.0,500000.0
Likewise with variables:
slidex#=0
should be
slidex#=0.0
Yes I know it's not important and it does work when you assign an integer value to a float variable, but as it's a tutorial, you should do it the way the documentation says.
Your code also needs to make sense and it's not good to put something that raises questions for the reader! What does this do?...
for mapsize=-1000 to 1400
next mapsize
that this doesn't:
mapsize=1400
With Set Camera To Follow, you say that for the Smooth and Collision parameters you "always just use 1". Why?
Surely this is what your reader is going to ask right?
So, my comments are constructive criticism intended only in helping you improve what you have done already. I'm not saying it's crap - far from it - just that you should tidy it up a bit so it's as good as it could be.
TDK_Man
