So i've been wrestling with power ups some more today. One of my proposed ideas has had to be modified as i could get the PU to do what i wanted but it then didn't detect collisions ... This was no go

thats a nice technique you have as well. What orientation is that based on and do you just change the project to iphone version in the device list and the attribute or is there more you do to tweak th

To fix this, you can use an attribute to store the target size... like self.targetX

Create an attribute.

Based on the advice from other threads I've tried to avoid behaviors like Constrain (only 1, maybe 2 uses of this per level) and Collide (though I still use overlap/collide checks on all my enemies an

have the bounce actor have a on collision rule that looked for collision with the trampoline actor, and this then stopped the actor by setting it's speeds (x and y) to 0, and at the same time switch i

represents a gradual change, unlike the change attribute behavior which is instant. You can get a great jumping effect by using its "ease out" feature (to simulate the peak of the j

I have been using gamesalad now for 8 months, and this is the only time I have encountered a problem that I could not solve myself or from the forums on this website. I have watched most of the vidoe

thats a nice technique you have as well. What orientation is that based on and do you just change the project to iphone version in the device list and the attribute or is there more you do to tweak th

use a replacement animation the trampoline, or constrain it temporally to positions that match the frames of the bouncing surface of the trampoline, then switch back visible with a new speed/directio

You spawn the new weapon as an actor when enemy is dead at the desired position. When your character collides with it change character image to with weapon or constrain the weapon position to your cha

Magic Scaling has a big if rule that surrounds four change attributes.

You would use a rule instead of a group and have a boolean attribute.

what you want to do is have an attribute (boolean) called check.

Although I don't need to change this, the 'Constrain distance from center' math as I understand it is, you finding the square root of the X/Y axis and applying that to the center dot? Or just the cent

Is it possible to have a game attribute that would turn on / off - the "moveable" physics attribute within an actor?

But wait, the customers who already bought the game would also have to buy the IAP purchase for the game they already bought! Can this be solved with this: release an update with an attribute set to t

But wait, the customers who already bought the game would also have to buy the IAP purchase for the game they already bought! Can this be solved with this: release an update with an attribute set to t

Can I save all of my games attributes (I currently have about 100) to a single key or do you have to save and load every attribute from a unique key?

Game.Number = attribute