I have three puzzle actors on the stage (each with a unique number 1-3) and three match actors (each with a unique number 1-3). When I select all the puzzle pieces individually (just relocating them …

I been here almost a year and I never fully understood the real purpose on each attribute. I almost all the time use interger and in a few occasions I use other like boolean and real but only because

Make a Real game attribute called snapto

3.instead of gravity make an accelerate down attribute in the player actor.

Make a Real game attribute called snapto

create a game boolean attribute called spinning

Create an integer attribute called Level (0)

Hi SAMman, make a game integer attribute, call it Level. On each level, put an actor outside of the playing area and in it, a Rule: Change attribute Level To Level + 1

Change Attribute: differenceAngle To: (( differenceAngle +180)%360)-180

Hey I have the same problem! Been working on a project and all of a sudden, "Change Scene" in a rule (with attribute condition) doesn't work anymore except if used within a timer. Ho

I made an example on how to constrain the position of an actor to the angle of a second actor with an (modifiable) offset using cos and sin.

The train is moving very smoothly because I'm not using the move to attribute.

I've found that interpolates can put a dent in the frame rate if used while loads of stuff is going on. For optimisation reasons, in general it seems like the best behaviour to use is change attribute

Thanks - I've enjoyed your game! I did notice that the checkmark on level 3 doesn't show up after you leave the app and return (like the save/load attribute for level 3 is missing)

Create an index/integer attribute called zero. Give it a value of 0.

I would do it like this. In the single grape have 2 attributes, one called points (set that to 10)and one called hitCount (set that to 0)

You could use the same actor if you wanted. Have a self attribute called points. Have that set to 10 and the image set as the single grape. Then whenever you want to replace it change attribute points

No you need to put the change attribute in your moving actor not the reset button.

use save/load attribute to save your money

I would try just using a reset scene instead of changing the scene back to the same scene. Unless your retry button is actually in a pause scene. Then you have to use the change like you have. Also tr