(Aside from the know leak culprits like spawn and timers) Are you guys finding that more issues are caused by heavy actors or too many actors on screen?

So...its a tap tard (a side project). Basically a paint by number. Tap on screen...spawn a dot of color...make a picture with a bunch of dots. After about 10 minutes and about 100 actors later (that

Managed to get actors (bad guys) to spawn at random locations along the top of the screen and move to a single point! Guess just goes to show how simple GS is to use! Very excited now.

you could destroy the original balloon, and spawn an "animated" actor balloon that flies away.

No easy way to do that, you can put the actor in the front/back only when it spawn!

difference from others. So how to make your own unique ringtone for your incoming calls, clock alarms, clock timer becomes a really important thing.

When touch is pressed, destroy this actor and spawn actor XXX.

A better way is to utilize the amazing accelerometers and touch interface which is unique to these devices.

its quick and dirty...but maybe it will help spawn some more refinement.

I agree it's certainly better to be (almost) unique/original where possible, but I draw the line at making all my graphics from scratch - I just can't do it. Possibly in the future when I have some mo

The second will allow more unique collision physics and expand games beyond circles and squares.

Make the spawn timer (10,9,8...) also a variable that dynamically reduces by 1.

spawn actor: actor1

200,000 unique vistors? or do you mean hits?

200,000 unique vistors? or do you mean hits?

Goodluck polygame!, im working on my third game at this moment, doubt id get anywhere near 4 days, after the first game i made i learnt some new tricks and the same with the second, learnt something

if attr. "sum3" < "2" (2 means he pressed 3 times with 1second intervals etc.") spawn actor "fail"

Does anyone know if it's possible to spawn an actor based on how quickly and number of times a button is pressed? For example: If 3 quick taps of a button result in failure but 3 slow taps of the but

I have a Google Alert for "Nesen Probe". That's one advantage of giving your app a unique name. I Googled the name (and a few others) before submission and found there were absolutel

To save in a loop...where as the loop counts...an integer counts with it and assigns the unique name to the memory slot...