2. Make use of Boolean Attributes which work like True-False toggles

I assume you're trying to constrain an actor's position and thus why physics isn't working.

Looking at what you've got there isn't going to be a magic bullet E=MC2 type equation. You're going to have to break the things you want into blocks with a control function. So an attribute the when s

I am looking to create a sliding-like scale of difficulty (with increasing difficulty) as my game progresses by changing attributes such as an actor's size which affects the difficulty.

You can create a Boolean attribute "InsideScreen". This attribute will be set to true using a rule if the tank's self.position.x is above 0 and under your screen width. If that att

Well searching around I found out that constrain is not viewed as movement by the physics engine... So not sure where to go from here... o well.

attribute:

I have noticed that real attributes can not be larger than 6 digits in length. Is there a way around this???

Could it be as simple as setting up a game attribute called Direction. And when the player is going left change the value of direction to Left, and then change it to Right when the player is going rig

Change attribute game.changingvisible to true

Hello all,

Or constrain you (Image)

@Bananarchy Yep its a collision count! So I already have a set-up and working attribute which +1 to level every time the collision reaches a certain amount. The thing I want is to have a clever way o

to change the level when the collision count attribute meets a certian criteria?

Hey. Do you have an integar attribute called 'levelcount' that increases incrementally by 1 every time the level changes?

So I think what you are saying is to use timers and other different 'decide' like events to trigger my attribute changes? So what I need a specific way to achieve this with my situation: (trigger attr

I´m trying to make my actor to flicker after picking up an item. Using timers to switch its green color attribute on and off I have managed it to flicker, but when I try to embed these behaviors into

And have you tried deleting the app and reinstalling it, just incase an attribute or table has been curropted, although this is unlikely to happen with a first install.

1. Have a game attribute called total coins and add to that after every run i.e. game.total coins = game.total coins + game.coins collected this run. Be sure to save the attribute at the end of each r

Create a real attribute stating the Y position of the Main actor. Eg. Main.Actor.Y. Which assume its always moving up?