if you are going to do a table cell - 1 deal you have to make a game.tablecell attribute and set that as your row or column in the expression. you will also nee to add a change attribute somewhere tha

hey thanks a bunch...it worked...but i didnt use the game.activeActor attribute. at the end where you said to put inside the actor "myiD = game.activeActor" i put myiD = game.actorIn

Constrain its X position to AAA*sin(self.Time*BBB)+CCC

I can't afford to stay and my next game design just suffers tremendously without certain things like proper collisions. My last game became such a hassle to maintain due to all problems with the creat

To keep track of the, use the Timer behavior to do Every 1 second --> Change Attribute game.elapsedTime (an integer) to game.elapsedTime+1.

http://gshelper.com/shop/advanced-game-functions/constrain-to-mouse-and-keep-collision-gamesalad/

Change.Attribute: game.score = game.score - 20

Change.Attribute : game.Score = game.Score - (Whatever you want)

im not really sure, but i would go about trying maybe making an attribute that is = to the timer...

Although RThurman's method is nice and accurate, it looks like the distanceToMouse constraint is killing the FPS, the blocks become very jerky.

Oh sorry. I should have mentioned that you will need to make a self attribute called "distanceToMouse" (or whatever you want to call it). It probably should be a "real&

move (or constrain) invisible actor to mouse.x and mouse.y

I don't follow you 100%, I can't find a self attribute distanceToMouse?

Constrain Attribute: self.distanceToMouse To: magnitude (game.mousePosition.x - self.Position.X,game.mousePosition.Y - self.Position.Y)

hmm, am I right thinking to get that to work I would need to define an area where the player can tap (with an invisible actor), add a boolean attribute to game for either tap or not tap, then for the

As for the problem of dynamic level building I figured a way to do would be to have the character do an initial pathfinding calculation, and then have an attribute that triggers a new path calculation

Game attributes:

Create an Attribute SpyCarPosX.Attribute.

Yeah it's called linearveloctiy x and linear velocity y its a self attribute in each actor.

I can constrain the two actors together, it's the un-constraining I can't get my head around... Probably simple stuff, but I'm pretty new to this... and it's late...