Wow that main menu is very clever..
and yes you have made a good TUTORIAL.
I will ask my firend to read this too, snice I understand it anyway. See now Newbi friendy this is.
But Im impressed by your main menu

--
now that I have posted on your come and post on mine [link]

I had to portray the tutorial in the menu, because like a website, people are impressed in the first few seconds. If they aren't impressed, they normally leave. Thanks by the way. I'm trying to improve it to an acceptable state.

Tag for later. Will definitely help for the game I'm trying to make, since I need some advanced hitTest tutorial. So far, it looks great, but I need to sleep. XD

~WolfAkela (Newgrounds)

--
DMC3:SE Veteran ~Comboing since 2005

I IMed you with most of my suggestions.

My main gripe is that your variable names aren't self explanatory and that indentation isn't shown which makes it hard to read.

--
SupaShaD: sometimes i think im too stealthy for my own good
Smurf: she ask "is it in yet?" again?

Proud to have made a stripper cry.

I read, updated and will be fixing the rest of the variable names and indentation in time. After those updates, if I a find an easier way to show lines (slightly different colors between even and odd lines?) then I will do that as well.

You've been a big help.

If there is something not covered here that you need done, you can reply or note me, and if I can do it myself I will add it up here, if it has to do with collision detection.

The green colour and bold font make it hard to read.

The indentation just needs to be preserved too.

--
SupaShaD: sometimes i think im too stealthy for my own good
Smurf: she ask "is it in yet?" again?

Proud to have made a stripper cry.

Hmmm...I have to say this is one of the finest tutorials I've seen. Easy to understand, good-looking yet it it covers so much.
Two things I don't understand:
1)Why is the quality forced to low?
2) One thing that was left unclear....what is while, what does it do and why would you keep making the _y bigger when it was already bigger than 500?

--
~critique-club member.

Good questions. Whiles will be updated in the next update, but I'll explain that here too.

while loops check for if what is in the brackets is true, and it doesn't stop the loop until it returns false, so nothing else happens in the span of the while loop, which is why if you made a loop that would never return false, it would freeze.

The reason it was making the _y too big all the time, was because we were checking if it was at the highest pixel, to push it out 1 more pixel, so every time, it would gain around 1 yS, and then be pushed out again, and repeat the process.

The fix was to push it until it was the pixel under the highest, so that the yS would still be decreased to 0, but it wouldn't push it out.

_quality = "LOW".... uhhh... I like sharp pixels and stuff. Makes the font easier to read to me, and that way there's no anti-aliasing. Personal preference really.