You individualise colour in the same way that you individualise any other attribute, If you want a particular instance to be green (while all the others are yellow) then simply unlock the actor and ch

I'll have to look at the code but I think no for the case of color. What matters to the engine is if the attribute is overridden (unlocked, not reverted) from the prototype or not. When you drag an ac

@Socks, @TaoOfSalad, does the color attribute not fall in the category of self.attributes and its values SHOULD be independent of the prototype?

Great game! As a side note, Id change the collisions a bit. Right now, the vampires can hit the character and they could still be a great distance away

It's just simple global (game level) attributes.

Gotcha. I guess the hard part is passing the information to the obstacle and getting the collisions right?

To stop people from constantly taping "Power-Hit" button, I had the "power-hit" button destroyed when attribute = 0. It worked great, but now I've decided to add an

(Quote)

I am trying to write a simple behavior for an enemy type. I want them to move back and forth with the speed and distance of movement determined by an attribute. I got that part working. However, I als

Create an integer attribute called game.lastScore and set it to 0.

* If attribute = 50

Basically for anyone else having the same problem, both sets of rules were satisfied by the same instruction which was when pressed complete their action.. when pressed once, the actor would change to

I think there should be a very simple solution but I cant seem to solve it. Basically (to its simplest explanation) I have an actor attribute (an integer set to 2 called actor "life"

Change Attribute self.image to "Image"..game.number

I made an Attribute (3, integer) and called it "Power-Up." So basically you have 3 strong hits to start your game.

-- and my golf game works this way -- you just constrain the number of meters to the hammer's (self.position.X-self.position.StartingX)/[some factor]. So if the hammer has traveled from x=100 to x=7

generate a random number to an attribute

I have multiple balls on screen and i want all of them to move a certain direction when my fly actor touches any of them, so i made a attribute touch and whenever fly touches any ball, it sets the to

4 attributes. Start x and start y. Then constrain x and constrain y. You can then. During game play use constrain attributes for self.x and self.y.......player dies the two options are restart. Move

Make a detector actor and constrain him to the player actor with one pixel overlap at the bottom.