* Loading the Saved attribute was good. My error there was that I had the saved key within an expression for some reason. So I removed the key from there and retyped it and now it saves it fine!

Sorry, I meant self.NextColumn... anyway, just an integer attribute that you increase after each spawn and then once you reach 4, you reset to 1 to start with the first column of another randomly sele

Your change attribute behaviour has to go inside the timer.

@Socks i fixed the text display bug by changing the attribute to an integer , here are the rules http://gyazo.com/9fa48a4d95f84a12d2042b19bc381623

--Change Attribute: game.Distance to game.Distance+1.

You could use Loop over Table and loop over the columns or you could just spawn an actor and then increase an attribute such as self.NextRow to self.NextRow+1 and use that in place of the column value

--Change Attribute: game.Distance to game.Distance+1.

3)Actor three uses one constrain behavior (along with the huge equation).

change attribute self.SpawnTime=game.Time+10Rule: if self.SpawnTime<game.Time then spawn Enemy change attribute self.SpawnTime=game.Time+random(4,8)end if

I would think about a solution where the player, walls and object are individual actors and how they would behave when they interact with each other. Perhaps use a rule that changes an attribute when

Create an integer game attribute called Distance.

StartTime and Mod1 are both real attributes I made, StartTime is at 0 and Mod1 is at 0.05.

Game attributes are not reset by a Reset Scene behavior. You have to do this manually using one or more Change Attribute behaviors just prior to the Reset Scene or Change Scene behavior.

If you use any Save Attribute behaviors, then you need matching Load Attribute behaviors with the same key names.

either you are missing to reset some attribute or you are saving or loading very many attributes in one go and you have a change scene behavior just after the saving/loading (in the latter case you co

@Socks‌ Based on my screenshot, didn't I already set in the original size of 96 x 124.32 in the Attributes box on the left, within the drop down size?

Edit: you will need edit the upload button to include your own score attribute.

for that. One thing I would try is to change or constrain the x (or y) position when the ball actor stops. You can snap it to a grid by doing Change (or Constrain) Attribute self.Position.X to roun

The PC creator does not have this option so you'll have to do what we use to do: create an attribute and change it to the table Cell Value. Since this new attribute now holds the table value you wante

But you can create an attribute that stores your tableValue and use that attribute in the rule.