Hi guys. I'm having an odd issue with a constrained actor. The actor is constrained to my main movement actor which I use for collisions. I have some logic set up to detect direction based on self.mot

make an integer attribute (game.bullets) and make this 8 for example. When the gun is fired game.bullets = game.bullet-1.... Then say when game.bullets = 0, +(more).

--Change game.attribute to (game.attribute+1)%2

REAL value attribute, for example timer1 (to level 1) responds differently than "GS viewer", the early second increases very rapidly:

I then proceeded to make a rule that if the attribute equals 4, i will change the attribute to 0(using a change attribute), thus making it go back to the original white square. However it takes 5 cli

--Change game.attribute to (game.attribute+1)%2

I set up a rule that changes and updates a value, saves that value and then compares it against its new value in order to try and create a looping update, this didn't work. I kind of want a repeating

attribute game.Clock.Hour >= 14

I've been stuck for two days since I downloaded the app, trying to figure out how to constrain my actor to the mouse movement ~X(

- I also set up a an change attribute inside the actor with:

I think that there are good use cases for using tables with save/load and using attributes. If you are managing a big set of attributes which need to be loaded and saved together, go with a table. If

when i watched tshirtbooths video on collisions with walls i did everything i set my y gravity to 200 and do th collinon rules help my actor wont stop boncing

----Constrain Attribute: self.Image To: 1

I always forget about actor's attribute !

I then proceeded to make a rule that if the attribute equals 4, i will change the attribute to 0(using a change attribute), thus making it go back to the original white square. However it takes 5 cli

You can use the move to command but you will need to constrain the hero's X & Y position to a real attribute so the enemy knows where to go.

I believe the most efficient way of doing this is to use the new writable table functions. It will use up much less performance and can have a steady attribute (the parent's width) to match all new gr

actorAttribute … boolean type … done

-Attribute: game.A1 is false

Then in the actor use a constrain behavior: constrain image to "button"..game.a1