and attribute game.bg is true

you better use attributes such as self.positionX or any other constant to make rules like this,(exemple : if self.positionX = 160 ----> "score stuff") lives and that kin

Change attribute high score to score

constrain X and Y to:

You could be hitting the enemy and loosing 2 lives simultaneously going below 0. Are you loading the attribute?

If I have a circle actor, and another actor collides with it, is there anyway to work out what the angle is on the circle of the collision?

A constrain behavior will try to run at 60 times a second. Compare that to a .2 timer which will only update 5 times a second. The slower the timer, (and .2 is very slow in computer time) the less w

second loop (all the precision necessary) or a Constrain Attribute? I'm trying to perfect the behavior of my enemy spawn points, and registering the despawning of enemies is the current task. There i

One tip for building AI and objects. If you move the enemy by controlling the velocity x and Y to keep collisions intact they can find their way around objects. My AI in puck it chases the puck right

* On next collision, increment collisions by 1, and reset steps taken to 0, then accelerate toward the X value of the destination.

In the second video where is displays the number of stars, simply add a behavior: constrain self.image to "Stars_"..(Attribute for stars here)..".png"

Create a game attribute of "PlayerJumping", then play around with that. So, say, if the player is not touching the platform, change "PlayerJumping" to true. Then, i

I have 8 items you can buy. When a player buy an item a boolean attribute change

skin color, etc.). You would then change or constrain the actor(s)' images to image files that match that value. So for example, if you choose hair style #1, you might change the hair actor's self.

So alpha is changing when an animation fires? If that's the case it could be a bug. Also could be that you have a bad rule that is firing a change attribute when you don't want it to. Send a bug repor

Be sure to return the attribute value to 0.

first, you need to create a pair of Global attributes to constrain to the X and Y coordinates of the player. These are crucial for making weapons that stay attached to the player.

Rather than constrain, i prefer to put it on an every timer or Self.time% loop. I find this way i can control the speed of updating, and sometimes thats very valuable for the behavior patterns that ta

@crestwoodgames' suggestion should do the trick for you. It may, depending on how you need to use it, be possible to avoid the constrain if you can put the value on the left of the expression. So for

I think there is a way to work around this. Maybe if you used a self attribute and constrained it to the table value. Then, use that self attribute in your rule.