So i found a new issue related to rules and tables. Since addressing a zero row/column causes freezes et.. I always wrap my rules that need attribute values to address a row/column in a rule saying do

What you can do is make a game-level attribute (type = real) and call it something like "OK2TapTime"

maybe add game attribute called last_time, and an attribute called next_time

Create a Boolean attribute and set it to true.

@http_gamesalad, I think I've found the issue. In your Star actor you have a couple of Timers with Interpolate Behaviors that are changing the size of the star. Interpolate Behaviors work outside the

If a rule or behaviour references an attribute that isn't copied over - game and scene attributes - it will just lead to a pop-up (on Mac at least) informing you of the broken attributes and then it w

@Armelline Do any of their rules that reference an attribute get a broken link like "invalid attribute". I would think this would happen if I drag the actors before the game attribut

* Any actors you drag into the new projects will only remain valid with non-editable game attribute and self attribute references. So if you have a change attribute that points to a game attribute, th

Not sure what 'shrink [the] camera' would mean in this context, shrinking the camera tracking area only applies to using the Control Camera behaviour and shrinking the actual camera would just zoom in

So shrink camera as small as possible and just constrain it to actors x how ever much I need. I think I gotcha.

Constrain camera origin X to self.X - (some value)

(Quote)

Just change the y position constrain attribute behavior:

Set a game boolean attribute AdsRemoved.

You don't want to be using "move to" for the task. Jus use the "change attribute" behaviour it will do it that quick, you won't see it move.

If you're only needing to detect the touch inside of the actor, and the release of that touch, then just putting the false change attribute in the otherwise should work fine.

(Quote)

If I am following you correctly, you could create an attribute that stores the time when the game should start allowing taps again. (Lets call it OK2TapTime.)

If attribute timer is less than 2...and taps are greater than 2...

Constrain camera origin X to whatever is controlling the camera's X - half the camera's X size