Another way to do this is to have three separate actors that each choose a random color value and then change a game attribute or table cell value to that chosen value. When the main character collid

Create an index attribute called start_y

On second thought, I think it is better if we don't destroy the "power button" at all. Just stop it from working and counting down (-1, -2, -3 etc.) when it's press once attribute =

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