For example I've finished whole projects without even making an attribute (let alone make a table), so it would be hilarious for someone to open one of my projects and realise "hey! it's just

changing the island1, island2 and island3 attribute to (random:1,17).

Like hesdeadjim said, you don't have to see this actor if you don't want, you can turn it's visibility off (in its Graphics attributes - uncheck the 'Visible' attribute).

shows, so I went ahead and used a pause game attribute. Hope this doesn't mess things up later?! It's still pausing the game, which it was intended to do, just at the very beginning and end of the le

Is that right? I found it extremely easy to do using a "pause game" attribute, which allows you to pause the game, bringing up an overlaying scene.

I constraint the X and Y of the Player as global game variables.

Another option: make an attribute 'VOL', select this in the expression window for the sound's volume. Then add an interpolation behaviour that interpolates VOL from 0 to 1.

I agree haha but sorry I'm not sure how that self last attribute works (Image)

If you just want to avoid 2 of the same colour in a row, throw in a "self.Last" attribute and update it to the current colour each time. When the next random colour is generated, com

Have you checked that your attribute "three-in-a-row" actually changes?

change attribute three-in-a-row to 1

Make an angle game attribute called game.direction. When the player presses a button to move in a certain direction, change the value of that attribute to match. For example, if the player presses a

@Trunks Kinda. There are invisible actors at work but they aren't (directly) handling the collisions. There are three tables used - one handles the tiles and the other two are used for randomly select

* Make another actor with a Display Text attribute.

I have my Game.Best attribute default set to 5000.

(Quote)

Sure. At the end of the first scene, change a game attribute for each value you want to continue to the next scene (e.g. Velocity, position, etc.). In the actor, change it's velocity and position to

For the 'stop moving forward' change attribute behaviour . . . looks like you are using the letter 'o' rather than the number 0.

Sure, just make a Boolean attribute call it pressed for example.

Like > when touch is on actor, it makes attribute X >> X+1