extra space you just created) and use two change attribute behaviors at the top of the background actor's rules to change self.position.x and self.position.y to whatever they should be (e.g. the cent

Since the blocks are made up of smaller blocks, you can create custom collision boxes and then constrain them to the shape that you created it for. Once a shape come on screen, the custom collision bo

Let's say you want to constrain the slime to an x value between 200 and 280. Constrain attribute self.position.x to max(200,min(self.position.x,280)).

Every time you collect a star change an attribute to that attribute+1 and then you could say that if attribute=1 then show 1 star and two star spots, if attribute=2 then show 2 stars and 1 spot, and i

collide, i make "health -1" attribute until "health =0" and then actor A destroyed and it did.

forgot you could make rules include more than one attribute.... This is what happens when you try and work while sick as a dog... Im sorry for wasting your time haha

-Create a boolean attribute (set to false). now make a timer that says after 30 sec change attribute to true.

is that with the method I am currently using the attribute that is controlling this on/off changes from 0 to 1 and then back to 0 with the %2 trick(@tshirtbooth) however this means that one mode is s

Perhaps I should have made it clearer, though. I thought you could turn self.graphics flip horizontally to - ___ and that would work like how it does for other attribute types. (Might be angle?)

Edit the actor's prototype and add an integer attribute called self.location. Then double-click on each actor on the scene and change each actor's self.digit value to 1, then 2, then 3, then 4 in o

the main actor from falling. Instead, use a constrain value on your actors.Y Position so that there is no friction/jittering.

You need a new game integer attribute added - I've called it MaxLevels - which is the maximum amount of levels in your game put in as its value. You need this to stop from advancing past your last lev

If its a sound each indivudual block will make then I would put it in the block itself. have a self attribute called sound and then place a change attbribute at the top of your rule list in the block

thanks for the reply, but what is the max levels attribute?

@tenrdrmer what about when you have a lives attribute.. can you tell me the formula for that

“rule:"touch" "pressed"; attribute:"first blank" is "true"——change attribute "first blank num"to 5”

Change attribute game.levelselect to game.levelselect - 1

after days spent trying to resolve this "bug" (with the intense help of MotherHoose), I think this is exactly how GS is meant to work with collisions...Obviously that's just my opini

You have an "index" attribute for the level number right ?

You store the number between 1 to 100 into an attribute and then you have rules to compare this attribute, if attribute is 1, then use table 1, otherwise if....