I have always found it a little over the top - like it is a miracle actually achieving a publish!

Bow Assassin is back in the top 100 games for Amazon! Check it out today and help get it into the top 100 overall (it's at 115 right now!) Thanks again to everyone who has contributed to it's success

Keep in mind GS is a 2d engine. so if your talking top down then yes its very doable but if your thinking more 3D well it can be faked but its going to be much more difficult for a beginner. Take the

Timing is everything! The bomb countdown stops when you touch it. But can you time your throw to have the bomb blow up when over the stars?

I can't agree more. It's a great feature but it's far from top of the important features that we need.

destroy item 1

ok that didnt work can you help this is what it says on one of the items it says when actor collides with ball destroy actor and change attribute: game.Brick to Game.Brick+1 its the same thing with ot

"Revert to prototype" on the top left of the rule editor. If that doesn't work, let me know.

2.when i drag an actor into the scene in the midle and i press preview it is in the top corner or just another place.

then it is a topSideHit … Otherwise: when < … it is bottomHit

is there a way to detect where the collision on the actor occured, so if I have a square box in the centre, if another actor hits it I can detect whether it was hit from top, bottom, left or right?

Is there a way to get my actor to follow a rolling path (from top to bottom of the scene)?

--- you could put a Destroy behaviour once the actor is off-screen but the actor will be destroyed automatically anyway once past a certain distance from the screen.

the game contain 10 actors , when the game start , the first actor will be dropped for you , if you finished from the first actor , it should destroy him and drop the second actor and so on .

Another alternative is to have a boolean switch. Interpolate only when "true". When you switch the boolean to false, you can then manipulate the actor (i.e. destroy).

Rule: When Mouse Button is Down --> Destroy

I also use a Notes actor that is just a yellow square that I place at the top of the actors pane and fill with Note behaviors that are more general in nature (e.g. credits, version details, outstandin

and then just have the animations dropped on top (easier working with collisions)? Or is it better to have the the bulk of the behaviors on the actor with the animations with the collision area const

I noticed that when there is an interpolate behavior, it wont be possible to destroy the actor before the interpolate achieve it's value. Is this a problem?

what's really funny is that, months later, only space is in the top ten (Image)