Score should be a global variable you created as I said in my first reaction.

This should work:

Create one sheet with the zoom/rotate events, right click on another event sheet and choose include event sheet, that way all the events on the zoom/rotate event sheet will be included. (They will stay on their own sheet ofcourse)

You could either add a

• system every x seconds condition

or

give the enemy timer behaviour and create a timer for waittime between bullets.

then create an event

on timer

if player is within distance

-spawn bullet

-start timer

Add a condition

system compare two values : round(abs(player.y-StartY))>Score

Add a condition to the compare event.

system for each enemy

Congrats! You are now more experienced than many of us who haven't created any video tutorials yet!

My recommendation would be to explain why you do certain things, like I don't think you explained why you use the 16:9 aspect ratio.

Overall, great video, I'd watch more. As you publish more and get more experience, the videos will only get even better!

Thanks, I guess I was being too self-critical..

Will take care of that explaining my decisions part.

Why are you using such an old version?

My example was saved in the last official release..

I see a whole lot of inefficient programming, repeating the same conditions.

For instance:

The last three events all start with for each damagesource. Wouldn't it be easier to combine these?

This is one way

no you write in the first one:

distance(enemy.x,enemy.y,player.x,enemy.y)

and in the second one the number of pixels distance you'd like.

I used enemy.y because I thought you only wanted the horizontal distance (x)

If you use player.y it will be like a circle arond the enemy.

For each enemy

system compare two values : distance(enemy.x,enemy.y,player.x,enemy.y) < 100

• enemy shoot