The projects above will stretch the project a little to fit the screen. Because of this, actors may be squished a little bit. An easy way to solve this is to put a change attribute behavior inside the

Though if you create a Real attribute to store the current game.Time(or self.Time) to subtract from the game.Time(or self.Time), then you can control the starting point of Time to 0, relative to when

If attribute level = 1

You're tempting fate by naming your attribute Death but I'll assume the bug also occurs for Love and other attribute names. =P

copy or copy of copy, without breaking the self attributes of all the other actors. Only deleting a self attribute that is in the actor and inherited by the copies, causes breakage in other actors.

Your image constrain animation could be such a calculation which would run perfect (if simplified) in the viewer, but not in the adhoc. But I have not tried yet.

My thinking was that if the constrain behaviour (using game.time) produced this:

Yeah it took a minute but i figured it out, i needed a scene actor that had all of my attributes for saving scores into my score table once the level was completed. Just like slowcut said a loading a

Change Attribute: self.color.Red to AAA

2) Add an attribute, let's call it 'Death'

The constrain behaviour has no absolute fixed amount of 'strain' it puts on the processor, using constrain behaviour to track game.time and self.time and device.clock.xxx doesn't seem to be particular

tableCellValue(your.table,"a"..number.attribute,column)

I think a lot of what is attractive about using floor( game.Time *30)%21 is that it eschews all these tables and attributes and timers and rules - and is a simple one line animation driver that can do

block's value as it was spawned (having a +1 attribute with that attribute becoming the row number). Couldn't think at the time how to do that with multiple columns! Still makes my head hurt, though

(Quote)

What @natzuur is getting at is that you have your spawned dynamite actor notify another unlocked actor on the scene via something like a boolean game attribute that gets changed when the dynamite acto

to a 1 column table (row=number of blocks attribute.).

if you are going to make an attribute I suggest it not be one you modify.

I do prefer using a counter attribute with a Timer behavior with 1/FPS for the every timer, or the mod+Rule condition trigger to increment the counter, because you can control the start and end of the

the actor acts in every way that it's self attribute is its own. But if I delete the self attribute from a copy, the other copies on the top level still have the self attribute visually but it break