all attribute changes must occur before the actor is destroyed.

So quite why they're of no use in collisions is not too clear.

I have an actor with boolean attributes set to false by default , then they go to true by touch , then destroy, then actor "manager" spawn the same actor just destroyed, BUT

I'm still working out the logic but how would I constrain movement to within a scene. I do not want the actor to go out of the scene but halt when the edge reaches the left or right edge of a scene.

Change Attribute --

If you want to give your actor 'lives', make a variable (look at the actor's attributes on the left hand side, under its image).

If I remember correctly, I have an attribute called game.timestart. This is equivalent to game.capturedtime.

He has 2 'real' attributes StartCaptureTime and CapturedTime

1. create two game level attributes called playerx and playery

then you could just add non-visible actors for collisions and place them in the scene on top of the areas where the walls, etc. are located in the image. So long as there are no layers in your game

Just use one big image! this way you can get better collisions and its better to have one big image, than 15 small!

Hey Chicop, I assume you are creating a new integer attribute to keep track of your items.

It's fairly tricky if you are constraining something to touch. I used this:

(1) using the tile function under graphics attribute; (2) using the replicate function; or (3) individually placing the multiple identical actor instances. Any one of the options will result in the

A black or glitched out screen in the game previewer generally means that there is some logic in your game that is left open. For instance, this can happen on any rule that points to an attribute whi

First off click on what button? Is this a button in your game? If so check the rules around that button see if anything is off or missing like an empty attribute. Is this running in the desktop viewer

First off click on what button? Is this a button in your game? If so check the rules around that button see if anything is off or missing like an empty attribute. Is this running in the desktop viewer

You can save game progress with the Load/Save attribute behaviors.

You can save game progress with the Load/Save attribute behaviors.

you could use an Index attribute type (positive only integer value). that would save a bit of memory instead of using a regular integer.