anyway, looks good. like the "bouncyness" of the collisions...

- Reference a image from a table list of images in place of a animation or a change image. You can even set up some self attributes to count up with some logic and constrain the row/col value to them.

That straightforward enough: make a scene boolean attribute and called it ShotDone.

Change attribute scene.Toggle to true

You have to unlock an instance of an actor to access the camera attributes. Or any scene attribute for that matter

That straightforward enough: make a scene boolean attribute and called it ShotDone.

No, there's not much can go wrong with a straightforward Change attribute of a boolean...I doubt it's that.

I've followed your instructions to the "T." The only thing I can think of is the very last line where I'm changing the attribute of the boolean back to false could be messed up.

Is there any way I can constrain the ball actor's speed? It moves in a straight line, at different angles, so how would I go about doing that?

Change attribute scene.Toggle to true

OK, if that's what you're after, make an integer attribute called CountDown, its value set to 20, as an example. (All figures will have to be adjusted depending on the rate increase and start interval

You can create an integer attribute called HowManySeconds and set it to 2, for example.

Yes basically, reset levels etc does not change any attributes, you have to manually do this. So when your game over screen is prompted, I assume you have a game attribute for this?

I'm not entirely sure on tables, but I'm pretty sure the basic idea is that a table is just another way of representing data where each box in the table is basically an attribute in your project. Thi

It looks to me like in your code since the move is in a rule based on actor location, as soon as your actor starts to move, it can't anymore. You'll probably need to make an attribute switching on an

to do everything through the GUI! Changing an attribute on an actor is a five click, eight second process in some cases - whereas if I had an editable text file open, I could make the same change in

I made the constrain rotation only take effect if the thumb stick's X position is + or - 50 from the base, so it kind of locks the angle unless you drag the stick out, while this doesn't all together

Maybe you could create puzzle pieces that 'lock' onto a simple grid? So, you could have an attribute that when pieceA is at 250x, 250y it stops moving. Just thinking out loud...

Add a integer attribute called eg. SPEED. Change this attribute from 150 to 400 and after 10 sec back to 150.

I have done a simple test and I used to LOCAL text attributes (Text From Table and Text To Table) and two rules.