Let say have four zeroes: 0000. And you get one point each time you score. The first 0 you have no rule. But in the second one, you can say: if attribute: game.Score > 9. Change attribute self.

I am using my own real variable instead of self.Time (under constrain attribute)for predefining the parabolic path(fixed starting point), and interpolating the variable to a final value (completes the

The problem was , that if you close the app(also from multitasking bar) and reopen it , its not loading the "coins" attribute ,

The best way is to set up 2 real attributes and constrain them to the main actors X and Y positions. Then in the second actor, constrain it's X and Y positions to the attributes with an offset to the

I'm doing it with "text" attribute type... seems work... i'll let you know

I want to constrain the position of Actor1 to Actor2, but can't find seem to browse to the Actor2's attributes when using the Expression Editor.

moving them - can we have a lock check box per attribute. that way i can select by clicking without risking having to reset size rotation and position each time.

probably yes... the only way i can think of (and it might be flawed, as i haven't tried it) would be to create a specific attribute for the previous digit then in the next one tell its alpha to be zer

okay … that 'stars' is one attribute you need the gameIndex to store

And then make an attribute called temp, index

Am i missing something? i just don't see how tables can help me here , i have 120 index attributes , and each 1 is referring to each level , so once the player finish level 1 , the "manager a

I, too, always used an Index attribute as a one-column array …

Display text for the attribute in the keyboard input (without any floor function) : 5.12346e+09

The attribute type is "real"

I need to create 42 index attributes for the "stars system" and another 42 index attributes for the "scoring system" and about 20 more for managing game stuff..

I am having an issue with creating an endless background. I understand the principles involved in having two separate images moving left to right and then changing their x attribute when they reach a

I am having an issue with creating an endless background. I understand the principles involved in having two separate images moving left to right and then changing their x attribute when they reach a

constrain attribute self.position.x to game.accelerometer.x*600

Hola. Es probable que haya una manera más fácil de hacer esto, y no sé si esto es lo que necesita exactamente, pero puede tener una regla que dice: "Cuando attribute.level a > 1 attrib

Can you show me the rule you put for the constrain ?