(Quote)

You are trying to make the purchase before the purchase table has had time to fill. You need to put the buy behaviour in a condition that checks that the callback attribute for the purchase table fill

Also, will this work for my restore button or do I need to add the CallBack attribute and request purchase data behavior there also?

The most important thing to me and i expect many people, is having the ability to create scenery actors i.e. platform / level elements that have proper collisions! this will make many games a lot more

I think if your adding polygon collisions... then it would be counter-productive NOT to have it changeable on a per frame basis. Per-frame would mean that accurate collision can be used for things lik

@quinn221 When I had this problem I deleted the save and load attribute and re did it , it worked , + you have to reset the game to check if it works on GS viewer , dont exit the viewer everything w

Q1 which is better on performance? to have rotate behavior which forces the actor to be moveable , or constrain the rotation and switch moveable off ? ( 5 to 10 actors, 48x48 32 bit image )

Here is what I have going on. When my Hero collides with flag pole I have have 3 save attribute to

@quinn221 You have a save attribute and a load attribute , both behaviors are linked to each other

You can use Save Attribute, Load Attribute behaviours.

I'm trying to use this method for a game but the collision for the attaching parts doesn't register collision when moving at greater speed. Any way of increasing collision detection?

Can some one tell me how to set a path find attribute or tell me of any tutorial please need help.

actually generating geometry it cannot detect collisions, so it doesn't matter whether the target actor is touching one of the dots or one of the spaces as neither will trigger a collision detection

(Quote)

Change attribute > self.Graphics.Flip Horizontally > True

A powerup attribute (boolean) that changes to true when the counter reaches 1000 points.

Is there an attribute that is part of the rule conditions that you posted above that is getting changed shortly after the scene starts? You may just have to turn off rules one by one until you find t

change attribute game.PlayMusic :to: not(game.PlayMusic)

You could simplify this somewhat, lose a few rules and attributes by just changing the music level directly.

Make a global Index attribute, called Music On/Off