try editing the density of the bullet based on fire power and see how the collisions react

Change attribute:

Second, when I apply the "otherwise" "change attribute" player - motion - linear y and x for the up and down rules it does not change anything. When I press up or d

Set 2 global attributes act x and act y interger. In main actor make it change attribute act x to main actors position x and the same for y. Make a second actor that is constrained to act x +100 and

Use an invisible actor and have that actor controlling the camera. Then use constrain attribute on that actor, and constrain it to the main characters X and Y position, with a +200 on the X position,

constrain linear x motion to 0

Constrain self.rotation to ( game.Time *4)+%360

you can make a self attribute called stop or something and have it set to 0.

( that the the mouse can click on or touch ) is still its original size. It appears the image increased NOT the attribute area.

It is true. The collisions are set for circle or rectangle.

I change the initial Y position to position y and after 0.1 seconds constrain y position to it. And it actually works! Sure,eventually the player is going to sink, but that will take ages.

well you could do as i posted above, and then keep changing the 4 score attribute to you 4 highest scores everytime you play. so itll give you your new average everytime

Use the attribute method I mentioned. (Image)

Frazzle, I'm curious how you finally got it to work- did you use the Save Attribute feature? I'm having the same problem with my platforms, even with density at 40,000 and a Constrain to Y after 0.1 s

the star? I ask this because if does not fit the collisions would not work well, no?

a rule when attribute device accelerometer x >0.5 move up

if you had 4 scores and you wanted the average of them, you would have a attribute for each score and have it like so:

I just want to keep track of the players average score. Would I need a "times played" attribute for it to divide by? Or how would you fellas go about it?

2. I tried doing something like this with the save attribute behaviour but it never worked (probably because i don't know how it works itself) but this seems foolproof.

they are on this platform. I try to do it with collisions, but if i put blocks on each other, they dont collide all, so I cant do this way... Can somebody help me, please?