The video was not meant to be a copy of your project, it was just an illustration of how quick and easy it is to constrain multiple 'child' actors to 'parent' actors, ignore the method I am using it i

Change Attribute self.timeStamp to game.Time

If you destroy an actor, it removes it from the scene. At that point, the actor won't run any of its rules or do anything. You might consider hiding it instead (Change Attribute self.Color.Alpha to

Make a text game attribute called game.nextImage. Use these behaviors in the spawner actor:

constrain self.position.X to:

What !! Why explain something that you know doesn't work !? Why not just use attributes ?

the hitbox) = number of actors which need to be constrained to as a collision shape

(Quote)

Game salad and Yosemite don't work too well together. I've found larger projects work worse than small ones, and it seems that multiple use of the attribute browser slows things down as well

Yeah that was a try to explain something, let me try it again: I have an actor called actor1 and it's several times in the scene. But cause of my limitation to be just able to constrain one hitbox to

Make a game attribute, let's call it X.

(Quote)

(Quote)

I can post a list of the vender Id and product ids later to night. At some point I would like to put in an device attribute for the friendly name of the face buttons. Feel free to put in a feature re

.....when attribute game.pageNumber=4

To prototype it use a timer that says every X seconds change attribute row1 to random(1,7)

change attribute game.pagenumber to game.pagenumber +1

Game.Attribute.X

So i have one actor that spawns the other actors in every x seconds. But instead of a number I have an attribute in the box. That attributes number is set to 4 integer. When X time has passed that num

You'll need to adjust the attribute values to spawn the pipes in a different orientation but hopefully since you'll already be familiar with the software by then, you'll know how to do that.