velocity.x,I created a change attribute that sets self.image to main actor attack ( boolean attribute I created under "game").

I didn't read this carefully enough last time. You're changing a text attribute (self.Image) to the value of a boolean attribute (0/1)? That doesn't make much sense to me unless you're using two ima

My game uses a score system so every second adds 1 onto the score attribute.

This will result in possible endless loops. I would go with a numerical attribute. So when touch is pressed Change Attribute game.NumericalTF = 1-game.NumericalTF

Thanks for your suggestion. I tried it and I happen to get a "0". I assume this means there is something wrong with my attribute or the rule I made for both actor and enemy? Please c

(Quote)

I've been able to achieve this by having an attribute that is updated with a +1 everytime an actor spawns. So when the attribute hits zero it then sends the new wave out. However, while this works 99

Constrain width to AAA*sin(game.time*BBB)+CCC

When touch is pressed, change attribute- height to height+ (2*game.targetscore)/heightrequire

I have this actor that increases in height each time a button is pressed. However i want the actor to be constrained to the bottom of the scene. I have noticed that gamesalad handles increase height/w

- Create a game attribute (integer, index, or real) to keep a score between scenes (most likely you'll use an integer).

I have an integer attribute called direction. 1 is right and 0 is left.

what is the difference if i setup the mod attribute to 0.02 or 0.05...does this affects the countdown? I apologize for my questions, i a not a programmer and probably i will never be, and if gamesala

I am trying to replace all timers of my game, but i got problem, i need to start a countdown after 1 second, so i need for 60seconds to remove 1 from an attribute that controls a replicate behavior. T

More simple? No, no and no. It's much, much harder. But again, if you need to have collide rules, then that's your only option. If you don't need to worry about collisions, then definitely use @RT

-Create Keyboard Actors (1 for each letter), with a Custom Attribute that holds a unique letter

If those buttons essentially do the same thing and only differ by say, having a different value for an Attribute, then you might want to read up on the Actor Prototype concept of GS. This'll save you

constrain self.Distance to magnitude( self.Position.X - game.TELEPORTERX , self.Position.Y - game.TELEPORTERY )

For a future reference if you want it to turn back to false if pressed again (not sure what your using it for) You create a rule when touch is pressed then throw another another rule in there that say

@uptimistik That's interesting. I've had mixed results. I just created a test project and set the actor's Move speed to 5000 and set "walls" to destroy if colliding with it and onl