Hey guys, I'm using TSB's ConstrainToMouse template found here: http://gshelper.com/?p=377 for picking up and dropping objects. It's awesome except that it doesnt work if my camera origin is elsewhere

So to your example , logically , we first need to know where the "parent" position is , and THEN constrain the "child" to this position , meaning , the "pa

When you group together a bunch of objects (using constrain) some elements can be 'laggy'' - so that when you drag your monster around his hat (a separate but constrained object) can lag behind.

"Hey Tynan , First , know that constrain (and interpolate) are overriding the collide behavior ."

Mmmmm . . . just tuned off constrain rotation on the red handle and it's colliding with the lilac block (but of course the rotation is then screwed up).

First , know that constrain (and interpolate) are overriding the collide behavior .

I have tried to find similar problems here but couldn't find a solution. I have an actor that simply needs to stay "under the finger" at all times, but as the screen scrolls the act…

I'm having an actor spawn. Is there a way I can have that "change attribute" be done on a prototype? or on the one being spawn? because its a command that spawns it...is there a way

> Current scene > layers > layer that actor is in > the actor > its attribute you want to change

Can an actor change attribute of another actor without going thru a game attribute?

if player collides with moving ledge constrain player's self motion X to 150 to move right -150 to move left(or whatever speed your ledge moves at)

(when colliding vertically their Y maintains an offset constraint to the wall surface … (horizontally, their X is constrained to wallCeiling)

make a game Index Attribute

FryingBacon has a great idea. But instead of adding the two attributes, you can try making each attribute a prime number and use multiplication. (Multiplying prime numbers results in a unique number

--Change Attribute to False

I am tring to change a boolean attribute to true when an actor is pressed and false when released.

Why not have two rules? I don't know if you could put a plus sign between them. So say rule if attribute game A + game b = 6 then.

The dungeon is created from a number of images that tile together and are either visible or invisible based on an attribute generated by the players position. Depending which are on or off it can look

- create game level attributes for each independent bee (bee1, bee2, etc.)

make an attribute integer type: correctStringCount