If attribute is not 8

you can make 2 attributes tapX and tapY

I want to build a puzzle game where the player taps on one actor and then on a second. On the second tap the first actor moves to the location of the second and a boolean attribute decides wether it's

Yeah use the method in the video with a little tweak, so when you leave the current scene to go to the next change a game real attribute lets call it lastpositionY to self.position.Y and when you go t

maybe to many constrain attributed or something oh we'll I'll figure a new game out

everything works well from the table except the Save attribute key and gamecenter ids

well do you know the X value? is it stored in an accessible attribute?

Interpolate for president! :-) (With Constrain as his sidekick...)

Collisions dont occur when interpolating ... interpolate was one of the best behaviours GS bought us!

Yeah but it's not even picking up collisions.

I'm wondering if the post and view leadership board rule supports text attribute in the argument so i can set it to be anything i want in game?

of course that would Rule would only trigger a game attribute

need a gameAttribute Index type to tell which spawner to spawn and when

It's the same old constrain issue where the "constrained" actor needs to be above "constrained to" actor in the layer stack.

make an actor and a attribute, int 0

you could make a attribute called lastDirection

when self. direction =4 move 270 degrees related to scene. but i would like to exclude the attribute from the direction is coming. say if direction is 0, then to choose a random from 2,3,4

suggest that you use a gameAttribute Index type directionsFlow = 0

(when born/spawned) Change attribute: self.motion.linear.y to 100

I would create a game attribute (type angle) called game.HeroAngle (or something like that). Then I would constrain the hero's self.rotation to game.HeroAngle