If you need it, try Corona. It's code--but lots of potential, especially for custom collisions.

I believe whats being done here is, the y value of the moving player is being tracked by a game attribute. And then for every tree there are to actors. on is in a layer above the player and one is in

Just to be clear I don't think we are getting pixel collisions. Just more shapes. http://gamesalad.com/corporate/roadmap/

You could have an overall boolean attribute called reset. Then in every single one of rules that could potentially mess up the rest process add when reset = false. So when you want to rest change rest

Ya, create a boolean attribute called "ActorName Alive" Make it true.

7) You can use the left/right arrow buttons to scroll the rock/paper/scissors completely off the screen. I think you should constrain it so that it cannot go off-screen.

No pixel collision yet, but it's coming. Right now, you're restricted to making custom shapes with squares and rectangles and circle collisions. If you can work something out by combining them togethe

Just replace change attribute with change image, or you could use change image and change self.image to the name of your image

No, this would be terrible for memory and take ages! What you need to do is randomise where and how often monsters appear etc. so random(1,100) when attribute=1 spawn or recycle monster. This is basic

create 2 game.attributes - real - call them collectiblesX and collectiblesY

Just setup at the top of all these objects you plan to spawn a change attribute for the x and y position to be random in a set range and place them in the scene off screen. it will give the same look

You can put in any amount for the health. Say, 100 instead of 10. And, as msones has stated, use a real attribute instead of an integer attribute.

For smaller then 1 health increments, make sure the attribute recording the boss's health is real, not an integer.

Create game attribute - game.spawn (integer)

Change attribute "Workaound attribute integer" to 1

Constrain Attribute: game.Y Position TO self.position.y

I'd like to constrain an animation to another actor's position.Y

Yeah, and integer would work. It could be a global attribute, or a self attribute. I'd suggest self, just to keep things clean--or if you have multiple characters.

just a general question, can i integrate attributes in a URL (Open URL Behavior).

im still having a hard time. do i need to add a integer attribute? or should i just change it in the rule?