In The Unofficial GameSalad Textbook, I wrote about "The poor man's debug". It's a crude — but effective — way to see attribute data. I decided to expand on that. I turned it into a

Use something like...overlaps or collides with wall change attribute self.Motion.Linear Velocity.X to -self.Motion.Linear Velocity.X

--Change (or Constrain) Attribute [exp] self.Position.X To:

Collisions with other actors could be a problem now I think of it... hm.

I'm not sure what you mean by behind the screen but in the spawn attribute there is a layer order option where you can choose to spawn in front or behind the layer or actor (the one who initiates the

Maybe try particle effects using the particle attribute.

Yeah, pretty easy to constrain it to one point, check out tshirtbooth's health bar video and it'll help you out.

Make two real game attributes, name then playerX, and playerY(or whateverX and Y)

Use a attribute and all you need is one actor

Create a text attribute ( I think )

like Game.attribute.

Surely you have a rule that says when ABC happens change attribute. Can't you just add a display text behaviour in that rule? If for some reason not...

@rob2: that would be great, however for simple animation you can use GS behaviors like interpolate, timers and change attribute (and of course animate) to achieve very nice results.

is there a way to check if an attribute has been changed?

the way I tried to accomplish this is I made an attribute called spawnrate. and then made a rule that every 30 seconds spawnrate will decrement. and made another timer that "every spawnrate s

just stick in an attribute that is something like isAlive = true, when the mask actor hits the enemy have it to change attribute isAlive to false. then inside your visible character actor, have it kil

We then constrain the bigger actor to the smaller mask actor and use the small mask actor as the collision.

To retain the non rectangular edges of these illustrations, I'm using the png format with transparency and it works nicely. However it does mean that sometimes the transparent edge makes collisions oc

change attribute self.tapcount to self.tapcount +1

When attribute tapcount=2