but they have to all have the same or different attribute (color, shape or number). So 3 tiles of 1 blue dot is a match but so would the same if they were all different shapes. It is based off a game

Just constrain a camera size actor with a hole in the centre.

@jay2dx By constraining the attribute to a value that changes each level, the condition for passing the next level continually changes. What I didn't mention is that you'd need a rule that says When

Ive been following this out of curiosity and please forgive me but i don't really understand this part, with automating the level change with constraining the points for next level, the code: &quo

is more efficient than magnitude, so you can constrain a screen sized / invisible actor to the camera (or make its layer non-scrollable) and then actors can check for collisions with this area (make

C, D, E, F, G, H, I, J and K are all just when attribute = 10 we probably wouldn't see much difference at all between nested and multi-conditional set ups.

And example of non-linear growth would be Constrain Attribute game.pointsForNextLevel to 100*pow(game.level,2):

* 1) intermediate/advanced

* When attribute.A is 100

(Quote)

Constrain (object.size) To 4*(100-(object.distance))

decide its order of execution? What strain is a constrain attribute really placing on it? Getting down to the nitty-gritty that would allow for really tight optimisation and deeper understanding of h

So i watched gshelper's video about choosing random attribute without repeat .

I'm a little confused with what you said? I've done the If Red Overlap actor Blue, I don't understand the " => attribute1(boolean)=true, otherwise false" and "=&g

In red actor: if red overlap actor blue => attribute1(boolean)=true, otherwise false

Hi; with this update, a key attribute in my game no longer updates on any event. It's simply a real attribute, called "KEY", that changes/increments when events happen - i.e. my spac

Make a boolean game attribute - let's call it DEATH !!!

Constrain planet's X to radius *cos (Controller's rotation)

constrain position.x to 100cos(self.timeself.speed)%360 + game.planetX and then the same for y (but with sin)

Personally I'd just constrain the image's x position to the compasses rotation, that way they cannot slip out of sync.