3. I'd interpolate the fuel as a game.attribute. It will slowly go down over time (Interpolate: game.fuel from 100 to 0 over 120 seconds, etc.)

using real attribute does the same thing... :-(

then you can have one more rule when attribute self position x is = or greater then 512 or when actor collides with base (any condition valid)

Im having an issue with displaying my scores. When I create a single actor to display multiple high scores, numbers that are 1 million and higher are displayed in scientific notation (ie. 1.0e+06). If

ok thanks, so when it reaches five do i have to set the attribute back to zero or is there another way to keep it counting because i was hoping to use the same attribute for for many coins collected.

3. I'd interpolate the fuel as a game.attribute. It will slowly go down over time (Interpolate: game.fuel from 100 to 0 over 120 seconds, etc.)

Sorry I mean what do you mean by LOAD into an attribute?

Hi jonmulcahy. I'm really stumped on what you mean about overriding the high score. What do you mean by save into an attribute?

place the enemies in the game but off screen, maybe above the gameplay area. when your attribute reaches 5, just MOVE them into the game.

I have an attribute which goes up every time a coin is collected. and then when it reaches a multiple of 5 to place a enemy actor on the screen, but i've heard using the spawn actor uses up memory.

Hi All I have an issue. I have constrained 1 actor to another. it works just fine till the camera starts to move around the background then the 2nd actor takes off and the constrain loses its position

1. Create some variables or in GameSalad's case, Attributes. In an actor create the following (Real) attributes:

that when it collides with green it has a change attribute of linear velocity x and y of certain values you want. The red actor should also have an accelerate 270 degrees at about speed 300 to simula

do I need to apply this behavior. Why is this attribute important.. Once we understand why, then the ideal Cookbook solution should challenge us to solve controlled problems on our own.

there is a change attribute behavior, and you can use that to do almost anything, even changing your current actor with some fancy programming. If you post what you're trying to accomplish, it'll be e

For example let's say that when the wave increase it also increase the speed of the enemy. I think you can use a mathematical formula using the wave number to achieve that: Change attribute self.Linea

there is a change attribute behavior, and you can use that to do almost anything, even changing your current actor with some fancy programming. If you post what you're trying to accomplish, it'll be e

if you make cando a real attribute equal to 100 then this would spawn every 100 seconds from the start of your game..

Maybe I can save attribute time.weather (first time is = to game.time) and allow the next change only if, after loading time.weather, rule sees that actual time.weather>game.time+100

It's not this, I just want that an attribute can change only after some time elapsed, and not each time you press a button, as example.