Change Attribute : game.wormcounterrandom To random ( 1 , 164 )

This can be true if they're next to each other, too. I've found the best thing to do is to have an invisible actor at the bottom and constrain both the main image and the shadow image to that invisibl

(Quote)

I have no problem with constrains.

Has anybody notice that the constrain is "slow" , like constrain a shadow to the player and move the player around the shadow is behind

(Quote)

Check in your Projects scene attribute, autorotate

Is there a reason you are constraining your actors speed?

Also note you don't need that rule in the otherwise section. All you need is the change attribute this is why it was getting stuck. Touch is released is a permanent condition once executed unlike pres

Attribute "LeftButtonPressed" = true

2 game attributes Right and left booleans

(Quote)

@hamzawesome Create an integer game attribute , call it Switch , In your touch actor create this rule

. . . . or, if the first value in the mod calculation is an attribute (let's call it X) and [i]needs[/i] to be 1,2,3,4 and 5 then . . .

Put all those behaviors that are in the rule above in a for .3 second timer, with run to completion checked, as the rule is cutting off as soon as you change game.highscore as then that changes game.s

You need to cut off the constrain when the collide happens or that change attribute will only change the velocity for 300 this of a second or one code cycle before the constrain fires again. You need

Just test it with a substitute attribute to replace your scene attribute and modify it with the keyboard input.

Constrain Self.Color.red of actor to tableCellValue(Table1, something, 1)

What happens with that setup? Probably the constrain and change attribute conflict. Also, the timer set up won't work the way you want-I don;t think it will revert back after the time is up.

(Quote)