Actually you can bypass the end attribute and just do when touch is released change attribute timeTotal to game.time - timeStart.

Create a real attribute called timeStart, one called timeEnd and one called timeTotal then when touch is pressed change attribute timeStart to game.time then when touch is released change attribute ti

:-) yes tshirtbooth I like your tutorials but I don't know where I can place the change attribute level to attribute level+1!!!

What I did do that worked (Just for futures sake to help others) I set up a self attribute called touch. When touch is = 0, then every 2-6 seconds, change velocity to whatever.

When object is hit set a global attribute to change

circle around your image. Polygon and irregular collisions are next fall according to the GS roadmap.

The rules you listed that attribute shouldn't have anything to do with it. so it sounds like you have some rules crossed somewhere.

Nothing is wrong with your art, as of now GS will only do circular and rectangular collisions. Your collision is probably set to rectangular so that's why theres a huge box around it.

You need to add a change attribute to make game.dead ≠ 0

You need to add a change attribute to make game.dead ≠ 0

Change Attribute

Boolean Attributes, let's call it "item"

to 0. If it's equal to 0, change the opacity attribute to 0, otherwise, change the opacity attribute to 1. Basically, it should show the starting score (0000) but when the player gets hits, the sco

it is an integer, I have the first 0 with a divider attribute at 10000, second 0 at 1000, third 0 at 100 and fourth 0 at 10 just like tshirtbooth explained on the video. so the integer is working but

The attribute you create for the score keeping needs to be an "integer" so it can do both positive and negative numbers.

planet follows actors co-ordinates via another global attribute constrained to the actors x/y positions +displacement. the background would need to scroll as well to complete the effect. add a half mo

You need to use global attributes, make 1 global attribute that is an integer, have the actor that you want to be the "trigger" set up with a rule that adds 1 to the integer.

Make a interger attribute called triggeron and set it to 0. Have a rule when actor overlaps with the trigger actor you have, change attribute triggeron to 1

You really don't need a timer, you just need a simple rule in the actor that subtracts from the health attribute when it collides with the bullet.

make 2 real attribute gotox and gotoy (call them whatver you want, those are just my examples)