a decimal then an integer is fine however for attribute like x and y coordinates and angles you need to use real. some ppl also use integers instead of Booleans and then just use 1 and 0 in place of

Btw how can I know which attribute to use in one project as I saw your video tutorial and you explain about them but do not tell which one is better to use regarding maybe the memmory saving. I ask be

As the title of the post says already, just would like to know where I can get INFO explaining about how to use the Attributes in GS creator as I do not understand them yet. (eg. Make an attribute &am

change attribute to attribute+50

I created an integer attribute that goes up 50 when in collides with the actor but every other time I hit that same actor it stays at 50. How do I fix the problem so it goes up 50 evey times it colli

Hi stimpers, very straightforward; create a boolean attribute called NextLevel, unchecked.

With the fire gun, I was using the wrong attribute. And meanwhile, 0.9.3 has been causing issues. It's taking longer than it should to track down these problems and eliminate them.

I am clueless on how to create a level system for my gamesalad game. My plan is to have several dozen levels starting off with only being able to play the 1st level at the beggining off the game and

I have a actor that has a fake constrain to the mouse when it is touched. I want to set it up so it collides with walls and other actors but instead it moves them. I tried changing the density and I p

• make boolean attributes Track1chosen, Track2chosen, etc

would be actually turned on by referencing an attribute value. These attributes would be set as on/off by touch to an actor or monitoring the position of a touch on the screen. It would be done this

you can still MAKE a self attribute though. Use the same block and give each one a self attribute number 1-9. then when actor collides and self attribte number =1 do this, if self attribute number =2

I don't think you can do that (ie: self refers just to the actor in which the rule is contained so the ball actor can't know the wall actor has a self.name). That is why Game attributes are used (ie:

other boxes do not push it down (you may have to constrain their y value if max speed doesn't work). Then have another rule for when it gets even farther below the camera origin (this all depends on

1. First have an actor and name it Block. Give it a self.attribute like "selfID" and set it to integer. You need a global attribute as well like "BlockCount" and se

* I constrain two Game attributes to the X and Y of the ball (ballTargetX and ballTargetY)

Hi, I need to do this:

(The current fix for this is to put a "Reset game" attribute on there, which was okay with the app I was doing, but not the best solution for most)

You could possibly be missing a rule or an attribute... it could literally be many different things... check all your rules in the title screen, and make sure they are filled in and there are no discr

Are there plans to fix the rule/attribute/self.image... ?? I just updated and opened my game project and its all messed up, 30 some rules broke because of this.