Make a command for the actor that says, when touch is released, change attribute, Self.Physics.Movable to False

every 0 seconds (not to completion), change attribute self.rotate to VectorToAngle(game.mouse.positionX-self.position.X, game.mouse.position.Y-self.Position.Y). What am I doing wrong? Specific rules w

I was going to try to transition over to tables as much as possible, but a rule cannot refer to a cell value for a condition. I know you can update an attribute with a cell value by change attribute,

(Quote)

If you must use tableCellValue in your rule conditions make a game attribute called ConstantZero which equals 0. When game.ConstantZero = (other expression)-tableCellValue()...

Keeping the UI in a non scrollable layer will keep it from scrolling, and a simple modification will also keep it from zooming. Something like constrain self.width to camera.width and self.height to c

So yes, you could constrain eye actors to the frog with an offset value for where they need to appear (within the sockets). As far as the movement, I'm not sure... I played around with it a bit but c

I probably won't be able to help with the velocity issue... hopefully someone else has an idea. I have noticed that at high velocity, actors tend to skip over collisions (e.g. with "walls&am

happen at >= 350) it *sometimes* detects collisions but doesn't arc at all, it just keeps "floating" up at that velocity. I can't really figure out how to resolve this issue.

Timers negatively affect performance more than attribute rules.

You cannot grab the cell from a table in a rule, currently. When you need to do is constrain or grab the value of the table and put that into another game attribute. Then reference that attribute in y

Im doing a large item database in a table and i need to use a column text attribute in a rule condition, but i dont know how.

That'll take too long. Can I make separate eyes and constrain them to the frog somehow? The eye sockets are currently part of the frog picture.

What is the disadvantage of using timers instead of the self.time attribute?

I removed every actor attribute that was bogus. So far no crashing at all. Thank you alot. Now I have a problem with the sound. When you exit the game and return after a long period if time sometimes

I seen a few GS demos that make me believe it can be done (i.e. constrain fun, orbit demo), I just don't know where to start.

im trying to use their template for table collisions... with the fancy building levels and blah blah blah... cept i want to do a grid for 64x64... but I cant seem to get it to work?

Sorry, I was just illustrating that you could use a scene attribute, but a game attribute works fine (e.g. a boolean called game.LevelCompleted, initially set to false).

it will say touch count = 1, but the changing attributes will be for touch #2.

-->constrain self.position x to game.mouse position x