In my game, I have a set of achievements which, when the player completes them, trigger an attribute respective to them to change to a certain, permanent value. After this is complete, I further wrote

@tatiang @kolabo thanks fellas! I think I figured it out. I was using a change attribute to save a self attribute to true, which would change the image. Seems like its working now that I added a timer

- and your "self.Easy" attribute is getting a true or false from a row "self.Name" in the same table.

I guess I just don't see the purpose of moving everything to a separate table when you can use a row index (integer attribute) to know where to start and end your table data for that event. It seems

I have over 30 load and save attributes in my game and Load and saves work fine for me.

I have options set up in my air hockey game to enable the player to change the color of their paddles. I save the color change with the 'save attribute' function and turn all other colors to false and

Well, the process of constraining a transparent actor to display the value of an attribute is the same as constraining a health bar actor so I thought it might be useful.

The current nightly build (available to Pro members) has amazing new functionality which includes the ability to use a table expression on the left side of a rule condition and also allows setting an

in a table on the left attribute selected of constrain behavior.

And here it is, slightly differently (although very similar to @Socks version): a real attribute to hold your number called TempNum, and an integer attribute, let's call it FirstDec

12/10 = 1.2 [save this into an attribute - let's call it "X"]

Just from digging through this first demo I can see how constrain and interpolate are powerful tools...I really appreciate the help!

Just a note, I've also tried changing a game attributes once the first rotation is complete to trigger the second, but I face the same problem: it's executing the attribute change at the same time as

If you use an attribute for the number of copies in your replicate behavior then you would just have a separate rule that says When attribute = 0 --> change attribute self.color.alpha to 0. Al

Not sure what you mean. The replicate behavior can diminish its value if you plug in an attribute. See the attached project.

I get the idea. But my brain just can't wrap how I will incorporate that in the code making the actor rotating following touch. I already use a constrain self.rotation there.

(Quote)

While a video might be better if you are a visual learner, there isn't anything *more* to it than what I posted above. One attribute, one rule with a single behavior, and one additional behavior.

If you use 'constrain self.rotation to self.time*100' then the 'angle' is always increasing, so you never suffer from the 0°-crossover-issue.

(Quote)