I feel your pain Toby. Some of the missed collisions on my table make a mockery of the paths the ball is supposed to take.

Constrain D to max(self.x,D)

In that case I would make a boolean game attribute let's call it "going_left" to indicate whether the player is going right or left. And when they hit the portal (or the jacket) the

Done - sadly the collisions etc and performance in HTML are not great. Some collisions not happening and animations not looping. (Image)

Then create an attribute and give it a value of 1.

@wayneh001 Does the Project Attribute tools work with the current version of GS? And if so, can you automatically rearrange all of your attributes alphabetically, or do you have to do it manually?

Say you want to do it by the number of attempts. Track that with an integer attribute (TRIES, for example) and have something like this:

Ever since i joined gamesalad which was a year ago all iv seen was improvement. They added custom collisions , custom fonts , html5 publishing , improved the loading time , improved performance, steam

1: Constrain your platform's y movement to a fixed height so it doesn't fall. For example, if your platform's y position = 150, then put in the platform:

basic collisions (granted there is now an option to create collision data in an external tool and import into GS but simply ignoring transparency on png files like lots of programs still isn't an avai

(Quote)

@yoaprz actor attribute

Is the attribute a game attribute, scene attribute, or actor attribute? Thanks

Constrain height to 100 * sin( game.Time * 200) + Your overall Y height

I can't remember if the spawn behaviour allows attributes yet and don't have GS on this machine. If it does, you only need the first half of this. If it doesn't a quick and dirty way of doing it would

Hey, I've got an actor that changes height based on attributes in the game. I have fixed the y position so that the actor's 'bottom' stays fixed whilst the top goes up and down. (constrain y to y + he

you could constrain two actors - one on the front and one from behind the assassin. If player collides with either of those two constrained actors, death.

If you actor does not rely on game level attributes, you can just drag it from one project to the other - on a Mac. Harder to do so on Windows. If it relies on game attributes, you need to go through

change attribute game.points to game.points +2 (I guess my question is where should I put the add points part in the rules?

things are spawned on a timer set to a random attribute that chooses what gets spawned. I don't have a clue as to why, it didnt use to happen before. Does anyone have any ideas as to why, because the