That's pretty bloody far in, for any button to STILL not be recognised properly / fully. I'll test using TOUCH game/device attribute rules tomorrow, to see what my visual limits test goes out to, so

prec(attribute.a/attribute.b,5)

i have 2 attributes and wanna display them as text...

make an attribute in the actor:

You have two actors, a Controller and a Detector, also make yourself three attributes (real) for the Controller, StartX, StartY and Angle.

Make 'Game' attribute, call it 'MOVE' (or whatever you like), then make a new actor to control the movement of all the other actors, let's call this new actor 'Move Controller'.

(Quote)

when ATTRIBUTE: ROUNDEDGAMECLOCK = ROUNDEDGAMECLOCK+1

(Quote)

Change attribute game.nextQuestionRow to random(1,100)+100*(game.difficulty-1)

9-Constrain sounds ..

Add Game attribute. “Raise walll”

    Change attribute game.input (text) to game.input..self.value

I increase the size of the chamber using an attribute of scene size of chamber but I have an actor who works as punctuation and want that this actor preserves his size I put it in another layer in ord

Link updates. Should fix issues with scene attribute references in unlocked instances:

@adent42 As an aside, every attribute field seems to flicker on and off when you mouse is hovered over it..

@adent42 Update. Games works fine until this actor is opened and then it is broken. ie The rules is happily in the actor and behaving as expected until it is opened, then the attribute field becomes d

My first thought was to make a new integer attribute for the enemy actor, name it for instance self.heart and simply give it -1 each hit, and destroy it when it reach 0. But the problem now is this, s

You won't be using constrains for this, though. A simple change attribute is enough. Constrains are only for things where you need to check if the actor is in the correct place every single frame. Unl

Game attributes