To do this, you will need a boolean attribute that checks for collisions. True if the actor collides with a higher layered actor, and False otherwise.

Create two new Boolean attributes called button 1 and 2

Change Attribute ChooseValue to tableCellValue(game.YourTable, game.YourColNum,random(1,5))

So now I've changed my mind, and agree with you that it'd be useful to have the ability to call up a sound using a text attribute. :-)

But I can clearly see a system using the Expression Editor that would have just a few simple Play Sound rules, that then piece together the filename using Attributes to bring my game to life easily an

And then have an attribute that tracks which story element the player is up to, such as "StoryIntroNum".

Design the actor and design the sword separately and attach/constrain it to the actor.

Would it be possible to add some kind of "draw order" for the actors? Not some trick where you put the same actor on two different layers - but an actual attribute that lets an acto

-Make a Player Y real attribute and constrain it to your players Y coordinates

Change Attribute self.myRow to tableRowCount(tableName)

Change Attribute: myLimit To: 12

hello, i am trying to detect instance that his something in the scene so i can hide it and increase score later, this instances are spawning while the game play, i tried to create a game attribute, an

(Quote)

Enter a value into attribute AAA, this will be our percentage.

Also an automated mouse offset so that when you click on an object to move it (using constrain to mouse position on touch) the position on the object you click on is where it is dragged from (rather t

I'm assuming the "Lifedegenerate" is a game attribute that I should create? And if so, what type (integer, boolean, etc.). The reason I ask is because I tried naming the specific rul

- .self attributes absent in a new actor to which code is copied created automatically like someone said

do you have any attribute that requests to change the image within the actor ?

Constrain X to 36.5*sin( game.Time *150)+200

nope, I use the normal attribute way