Constrain self.size.width to magnitude(self.position.X-game.centerX,self.position.Y-game.centerY)/10+game.minimumWidth

I just wanted to know if anyone had any support for the claim that "Change Attribute" is more reliable / less of a strain on the processor (or some other advantage) . . . than &

Try constrain image instead of change image. Change image doesn't seem to work reliably for swapping an image. Also, you don't need the image extension in the name, so if the graphic is called &qu

7. Instead of using the "Change Image" behavior, use "Change Attribute" and change the self.Image to the desired image's name.(Quote)

It's very easy, everything is controlled by the two constrains of the 'More Weirdness' actor.

The logic overall seems fine. One question though. What function are you using in the Expression Editor to add 1 to your integer attribute? If you're just typing in (without quotation marks) &q

Then make the following behaviour: [Change Attribute / self.colour / alpha= 0] and cut and paste it into all your actors that need to be invisible when the game starts.

Hi, I'm having some issues with the custom attributes I'm creating...

Hi Natalie, basically you need two integer attributes, let's call them BoyScore and GirlScore. Two buttons on each scene, in the Rules each, put:

Change Attribute self.Motion.linearVelocity to 10000

Have you tried making an attribute that is TRUE at the random times you want it to be stopped and then adding a rule where only when that attribute is TRUE the object will move. Otherwise it wouldn't

- when hit change attribute (integer) "hit or not" to 2 (meaning he's hit)

(or cut and paste a [Change Attribute - Self.Pos Y to XXXX] into each of the floor actors)

A good way to do this using physics (interpolate and constrain are not physics) is have something like the following:

Create a table with the hit points for each scene listed in a row. Create an integer game attribute that defines the scene number (ex: 1, 2, 3).

This actor has an attribute called hits points,i want change (increase) the hit points attribute in each level of the game to make it harder.

Constrain HUD with camera zoom dont run fin under viewer xcode and gs, maybe its bad solution too.

Allright then i insert a code about constrain position x,y and self.rotation.

Change attribute B.position.x to A. position.x

and have an integer attribute, and if this attribute is 0 then set the actor to interpolate its self.position.x or y to point A and if the attribute is 1 set it to interpolate to point B.