into the actor sparks - if game shoot = 0 - constrain self position y to 0.

https://forums.gamesalad.com/discussion/comment/614411#Comment_614411

you don't need physics body editor to make custom collisions. depending on how complex the number of polygons in your custom shape are, and how much time you want to take, you can write your own .json

I'm trying to save an attribute (number of presses) without using a table. I only have to save the one number, so I was hoping the save attribute command might be simple. The number is a game level 'r

I'm making a range of image slide shows that function only on touch, and I'm being lazy by using the animate function (since I have 16 of them and over 100 images across them all). But the slowest it

Use a Game Level Boolean Attribute that starts a False. When the Real floor is pressed change that Attribute too True. Have the invisible floor watch that attribute and when it becomes True, destroy i

I've seen the formulas for moving actors up and down to accommodate for overscan in landscape view. I'd rather just build my actors closer to the center to begin with. My actors are buttons that you

* Version your games in an attribute and make sure to send that version with the Load Table From Network request.

I think you should be able to save your current scene number to an Attribute. Then instead of using Resent Scene from the pause scene, use a Change Scene Behavior and for the scene to change too use A

http://forums.gamesalad.com/discussion/comment/614210#Comment_614210

have an actor that you place first on the lowest layer. unlock it. and you can change the camera size from there using change attribute.

when you use change attribute, in the box where you select the attribute, go:

https://forums.gamesalad.com/discussion/comment/210289#Comment_210289

Like the tutorial, I created an actor called "Pair" it has two attributes "WhichPair" and "WhichImage", the "WhichPair" is set 1

I've always assumed, but never actually tested, that custom collisions work the same way:

gs does some weird stuff sometimes. in my current project i have display actors that constrain to a relative size and position to adjust for zoom. they work perfect on every scene except one where the

In the example used for the video the player is stationary during the attach so there is no need to constrain the hit box. It just pops up for the 3-4 frames of the animation and goes away.

ive done the constrain as well. they all go to the same place. the buttons get there slightly quicker. i may need to dowht @jamie_c suggests but now its like a pebble in my shoe. lol. i just feel it s

if that's the case, you could use two global attributes. one that records the single spawned draggable icon value (eg. spawnedIcon), and one that records the value of the icon that the draggable actor

you need to constrain hit-box to PL1 position?