Okay, I understand what you're saying. You're talking about a difference of 0.4 pixels. I tested collisions with a bullet moving at speed 100 (slow) and the game.Time of the collisions for two actor

You'll need to post more of your rules. What is the rule condition for the death sequence? Which rules have anything to do with game.life? And I assume you mean change attribute game.life to game.l

Make a true/false attribute for each actor

If you mean only a certain amount of times, then make an integer attribute, let's call it Count.

Change attribute-game.life to -1

these actors another actor which will be constrained to the movement of the first spawned actor.

@Cluv thanks for the "log debug" hint, I'll definitely look into that. And I was worried that was the case for a constrain.

You can't constrain a table value using a Constrain Attribute command, but you can use a timer to effectively constrain table values. To do that, you would place a Change Table Value behavior inside

.....Change Attribute self.bulletTime (real) to self.Time

1.) You can use a "log debug" function next to your (I believe you are doing a) change attribute function to check when your attribute timing in the logic. You should put a few othe

So to explain more: the first and second rules: when touch is pressed and when game.touch... is false are common to both; so is the boolean attribute self.ruleID common except one is when false and on

If the first rule fires, it sets the rule1Done attribute to true and does the same to touchDelay. It also writes a Debug message to the window, saying basically, I fired.

When the user opens the app, save the current date to an attribute. (Device->Clock->Day/Hour/Minute/etc)

"If overlaps or collide with enemy" - change attribute.self.color.alpha to 0 - It might visually help you out (Image)

In this case, count is an attribute used as boolean. Got it to work after using timer to slow down the count. Thank you both.

If you're looking for a simple 'pong' kind of air hockey game, you would just have the AI goalie follow (constrain itself) the Y attribute of the puck. You might want to add some variation to the cons

I've been trying 'change attribute' function, and doing 'every 0.0blabla seconds' 'change attribute green to green*-1.03' ---something along these lines, its changing the color, but only once

@quantumsheep it could be anywhere in the list of parameters. It could even be in a couple of parameters. But game.YNM would be if you were to use an attribute to pass in the option text instead of ma

So if I'm understanding you correctly now Kevin, you're not actually updating an attribute called count, you were using the word "count" in the pseudocode sense, to mean a second?

Change Attribute Count to 1