Still think you will have a lot of if/then logic with that approach BTT, which is something that is slow to manually update in GS (the slow scrolling and expression entries) when it is layered deep as

I was having to seperate things out from the destroy (among other things) even in 0.7.0 FMG!! You must have gotten very lucky to not have run up against it.

Yeah, the devs mentioned in a post somewhere that the rules of an actor on any given level in the rules/behavior section will be executed willy-nilly but most of the time from top down. Basically sta

Well, firstly, don't rely on behaviors to work from the top down...

First, you need to keep the invisible collision actor in the scrollable layer.

place the completed app. i threw mine on the desktop. double-click like any app and it opens. you have a choice of full-screen or quitting the app in the menu bar up top. no menus on the app window i

when I have preserve scene turned on for button 1, it seems like a lot of the rules in the scene just stop working when I return to it.

There was an Alan Partridge sound board that made it into the top 25 on the UK itunes.

Bug test level. click on green thrust button to thrust. When level starts, click green button. in 0.7.0 it goes up as expected. in 0.8.1 it will rotate left and not stop at -45. Use left/right arrows

One of the things that wasn't working was having the Destroy Behavior after some other Behaviors. The Destroy behavior always fired first and the game ignored the other Behaviors. I fixed it like this

JGary321 came up with this neat trick on using a Change Attribute Action for images: http://gamesalad.com/forums/topic.php?id=2939

game.PlayerRotation

So my make-shift solution was to have two separate actors and, when I needed to swap collision types, I would simple spawn a new actor and destroy the previous.

I won't get into why I needed this, but you see the point. You can make trigger actors that spawn on top of your recieving actor. The only rule you need in the trigger actor is:

Instead of spawning during gameplay, I would spawn ALL of the Actors as soon as the level starts - just keep them offscreen. The cannonballs could certainly be done like this, as well as the main ball

I love how on top of this you guys are with this already releasing a patch this soon!

So the actor (the button) sensing the press would set a game boolean attribute to "true" (i.e. call it "PlayerJumping"). Then the player actor could have a rule th

The way they do it in other programming languages (using Box2D) is to constantly destroy/respawn an actor of a different size.

Thanks, Mulcahy! Good luck to you as well, Hope F reaches the top!

Number 74 in the Top 100 Paid Arcade Games