You can have a Boolean Rule to set to true when he gets his power up, then have an attribute check to see if its true or not then make the change.

i think you can just create some attributes and store the values there mate.............then create a rule to change attribute position to the attribute values maybe?

Change Attribute:

After the button is pressed and the original bullet flies across the screen I want a new bullet to spawn at the original position and use the same attribute like the rotation and stuff...

just try a change attribute, game.score to (game.Score+game.BonusPoints) . if you are just adding a couple values I don't see the benefit of using interpolate

Its not completely Broke. The issues seem to stem from either a touch is released rule or A rule the has a boolean attribute as a condition.

Yes but there are so many games out their that have a constrain rule. And I don't see no mouse. Thank you for replying.

@ryan walls dont work because the constrain to mouse will overide the collide.

when attribute textdata= 1

Thanks you so much Jbsitedesign it worked for me took a while to know where to put the attribute and also what happens when I click the box under attributes where the Is Shot boolean attribute was mad

Basically I made a game attribute (integer) which I called 'Page #' and set the default # to '1'. Then I made back/forward buttons (actors) on my page to cycle through the pages. When you click the ba

I think this is because there is a maximum minus x position you can push an actor off screen before it get destroyed and/or disappears forever. You can solve your problem by having a rule that says if

You have to constrain the actor position X to :

When i constrain my actor X position to the game.mouse.position.X, its based on 1024 and not 3000... So when i click on my actor and my camera is on X=2500, my actor disapear on position between 0 and

in X and Y but I could make same thing without constrains using spawn actor behavior to spawn actors that looks like smoke. Tell me what method is the best method in terms of optimization.

for the determining of if the object is last I would try putting in a game attribute integer set at zero and each actor has rules in that add 1 to that integer then taking game attribute integer numbe

I have set some objects to constrain to the mouse position with some offset. When I move the mouse towards the left, the object would go off screen (this is what I wanted it to do) but in the preview

just add a game attribute with a name like PressedColor. When a button is pressed it can set Game.PressedColor to whatever value you want. Then your caller can monitor Game.PressedColor to see what

add a boolean attribute to your ammo objects.....SOmething like, Is Shot and set its default value to false....put your down accel inside a rule that only activates if Is Shot = True. When your ready

I have 3 boolean Game attributes Puddle Go, Puddle 2 Go, and Puddle 3 Go