If its still not working I would try to find a different way to reduce the touch is pressed rules down you just a change attribute.

At the minute when touch is pressed after 0.3 seconds I.A.P restore item action takes place and changes full game attribute.

So you have all of your unpause rules firing prior to the attribute changes. And your other rules negates the rule before the rest of it can run.

touches the goal, is that where I put the change attribute for sceneToGoTo and the save attribute? It would just be best if you told me exactly what I need to do step by step.

Is the circle a single actor/instance in a set position? If so, just use actual position values in your rules (When attribute self.position.X>300 ... [move right], etc.).

You can't reference a scene by name or number, but you can set up rules based on the value of an attribute: When game.sceneToGoTo is 2 --> Change Scene [level 2 scene name]

Ive tried it as an baked app too, yes. Happens easier there i tought. The platform is using move to behavior and the character uses change self motion linear x +- what ever. But i need friction on bot

Yes as @tatiang said, however If you want to have it (saved) so next time you run the game it will show which scene the player reached, you should also add a save attribute to @tatiang process or use

Here's what I do: each time I change the scene, I add a behavior above the Change Scene behavior that says Change Attribute game.currentScene [a text attribute] to [and then I type in the name of the

If you have a winding path, then the enemy that has been on the screen the longest is closest to the exit. Figure out how long it takes for an enemy to complete the path and then set each enemy's com

I don't see how this would prevent you from using tables. The idea is that you do a Change Attribute self.income (or game.income) to tableCellValue(tableName, row, col) where row is the city number a

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

It could be that it's 2AM for me right now, but I'm not quite understanding the method to your madness...and I really wish I did. My app will end up having several hundred attributes unless I could r

Hi

You can use either tables or save attribute, lets go with an easy way of saving,

I've tried using the interpolate behavior to say: after 0.3 seconds, if self.height = 25, interpolate over 1.121 seconds to 30, if self.height = 30, change attribute self.height to 25

I got a universal build template on the marketplace that will deal with the pause scene problem. Just make sure the check off the game.use_pause attribute to true

there is no interpolating happening while the collisions are supposed to be occurring. Actors cannot collide with each other during interpolation of size or position.

Just going off a hunch, you would want to set/change an attribute to ____ when it is pressed AND it is at the 2 second mark.

I would use a separate attribute in the object, and only allow your code that moves the object along with the touch location to occur if that attribute is true. Set it to false when the object has be