destroy all incoming meteors before they touch down and destroy the Earth! But watch out! Your ammunition is limited, your time is running out, and your swipes are limited, so do not waste any bullet

I personally just think this would be an interesting idea to have it so that instead of having a static image spin for your custom loading wheel, you would have a custom loading image which could be a

If you update to the Android Studio you no longer have platform-tools - the Android Studio application now seems to be the current system.

Thank you So much to everyone for the support and especially the Gamesalad team For the great Software.

He might be able to help you out.

fails for some reason. And yes I made sure I downloaded the latest SDK before I published but still got the same error

I just wanted to say, for anyone else that finds this thread in the future, I used this method to make it so that I could spawn enemies that were chained together.

I am pretty new to game development, however I really would like to publish one. I have downloaded a VERY simple app template that I really like similar to Flappy Birds. I am looking for some assistan

I'm going ahead to make another update with some of my newer and yet-to-be-presented works:

Maybe you are running an older version of android? Also have you updated your android SDK before you published? It's good to make sure it's current before you publish an app for distribution.

(Quote)

(Quote)

Well I read that even though that has changed some cellphones are still not able to download apps over 50 MB, specially older generation phones. I guess that explains why I could download it in a tabl

I unlock already unlocked actors, that's how unlocky I am.

The self-constrain is another interesting way to do this. Hmm...

That's petty much how I always use it ! (Image)

I like that idea, @Socks, except if you need to reference the value from other actors.

Now you have a little clock that accumulates 1°/sec, it's easy to read, easy to stop, restart, reverse, speed up, slow down (and so on . . . )

Say you need 4 "Screens". Just create a Massive Scene (say 2 x 2) and move the camera when you need to go to a different "Screen" to show the area that has been nav

The device clock and the attributes game.Time, scene.Time, and self.Time are like real time. They don't stop. At least until someone builds a time machine. Because it's built-in, it's an easy thing