Before ActorA starts moving, grab his pos.X, for example into a new attribute called self.StartX. Then constrain scene.scores to his current (pox.X - StartX) * 10 (or whatever multiple gives you the k

change attribute

i'm not sure what you mean by access and reference an attribute's value . you can't access anything on the users's device remotely. but you can anticipate user's input and build responses preemptively

Thanks for the response @ultima! I am using the Save / Load attributes correctly in both the first and new versions. So with that being said, would I be able to access and reference an attribute's val

as long as you use save/load feature you have to assign a save key to the values. and they'll be on the device. I find it easier to save all the attribute to the table and saving the table.. no messy

Ok, so I'm working on an update to one of our apps in which I am referencing the value of an attribute created and stored in the first version of the app. When the user updates the app on their device

(Quote)

Yes and no. If you do Timer every random(1,6), it will calculate the random number ONCE and then use that for the timer value (e.g. every 2 seconds). If you actually want something to happen at a ra

Constrain attribute self.TimeLeft (index) to 10-self.Time

I did try to make an attribute, change game.attribute to 10-self.time

Make an integer attribute, lets call it LeftOrRight.

I set up X,Y attributes for each actor (i.e. actor position x, actor position y). Attributes are real. Do this for all of your actors. I then created dummy actors which serve as camera transitioners.

Make a self attribute inside your actor named Timer and set it to zero. NEXT create a Timer Attribute that says every 1 sec run to completion (WITH) a change change attribute inside that says Change A

You could do something like if ball collides with slingshot change attribute slingshot y velocity to 0.

make a chainattack global attribute

Example: Everytime i defeat enemy, and i defeat the next one within 2 second, i want to create a "chain attack" attribute. And every time i defeat another enemy within 2 second from

(Quote)

and with the combination of model detecting attribute (like tshirt said devide=iphone5/4/ipad/ipad mini/kindle/nook etc) we can easily manage how things will move around instead of building one file

Rule if attribute (Devices/Screen/Size/Width or Height (depends on your game orientation)) is 480 (old iPhone):

true or false. And will definitely try out using constrain attributes when I get the chance.