This will generate a random number between 1 and 100. This expression can be used wherever a number can be used. For example, you can have an actor rotate to a random angle using Rotate to Angle and

And whaddayaknow, it works OK. So in place of the Display Text you'd have a boolean change attribute (or a text one as above so you know which block is in which slot).

Constrain Attribute:

Note: I needed a Self.TouchCounter attribute in addition to the ones above so 6 attributes in total. You can drag more of the Actor1 in the scene and just click to change the color and it will work wi

So I have an interpolate feature that takes a game.attribute from 50 -> 500 over 5 minutes.

could you not use just 5 attributes?

I'm wondering what is the simplest way to code up a rule that differentiates the same actor from each other once they are spawned? I was thinking maybe assigning an ID and saving the attribute, but n

i have three control methods in my game. hot zones, tilt and onscreen controls. when a user clicks on what control they way, it sets my controls attribute to 1 2 or 3.

I see, I misunderstood (again ;-) Presumably you're using something like a boolean attribute called self.DragandDrop? I guess you might be, if it's based on the GS template.

set up both sets of controls but have them dependant on a boolean game attribute that is changed by the player in a menu screen or in the playing scene- which ever you want. Both styles of control can

Don't think so, but I assume you could just make an attribute, and a rule to attach the numbers to your scene names.

Now create your "see-saw". in see-saw create 2 integer attributes called X and Y.

you can make a self attribute called intermove or something. then change intermove to self positionx-400 or something

You need to constrain both the X and the Y positions to exactly what it tells you to. Make sure you used sin for y and not cos.

If they aren't starting and stopping you might be ok with move, which is less expensive than constrain. My experience with move has been that things can act a bit funny if they are starting and stopp

Constrain is expensive and I've found move to be a bit unpredictable without constraints. You might want to try interpolate. Just use 2 interpolates if you're changing both x and y coordinates.

Change attribute self.color.Red to X, self.color.green to X, self.color.blue to X (Depending on which color you want to change it to).

Today I was testing my new game on the viewer (both 92). In this game I have just one actor, without any rules (with one custom attribute), and I use instances in the scenes. Also I have about 30 or 4

Having my object actors and invisible collision constrained to one another which will allow me to uncheck movable on either one?

,and just one more thing, when set that rule the platform moved down after changing the attribute to 600, it was on movable but i dont have gravity on it and no accelerate, so i just uncheck the mova