@tutyses It's not that it doesn't detect the collision. It's that you're expecting it to only detect the collision on the top layer or the first enemy to that position, or something along those lines

You have enemies stacked on top of each other. The bullet is going to collide with multiple enemies because it physically overlaps those enemies simultaneously. Not really sure how you can avoid tha

Would the best approach be to just create a GIANT square actor, put him on the furthest layer on the back. Then create separate actors for each smaller square as place holders to spawn the actors?

I flip the scene and made the zombies slow down but when I destroy them and respawn they don't reset, how can I reset the speed to the actors?

(Quote)

I have an ipad game and I check the screen size and if it is an iPhone 5 size, I change the size and location of the actors. I dont want a top or bottom black bar.

yes.. when in preview.. on the top left corner.. u'll see a dropdown with a list of devices.. select your intended device.

The bullet has the behavior to destroy itself when it contacts an enemy.

It's all about sliming the code. Finding ways to build out your code around central attributes and/or events instead of just adding layer after layer. The only way to accomplish this is to layout the

I wish they would create a behavior or some way to control the draw order of actors so we don't need to do the alpha/layer trick. It's so limiting.

The fact that it works on older OS is a cool feature, but I don't think it will ever achieve a top spot on the priority list.

Is it possible to layer actors so that using collision would react to the actor on the top layer giving the impression that some actors are In the distance and won't rect to colliding with another act

help adapting it for bullets). Have the bullet destroy itself after it has traveled 100 pixels. If the bullet collides with an enemy, tell the player actor to stop moving and begin firing.

You just need to have two actors, one that is already on a layer behind the obstacle, one that is on a layer in front of the obstacle . . . . when you need the actor to go 'behind' the obstacle make

Here is the same thing with the collision points even more spaced out, hopefully you can see that you don't really need them to be that close for a curved collision surface - obviously in the actual g

four game level attributes to get their cues for destroy, counting misses and hits, image display, spawning associated balls et... This means things will scan and respond faster. Designing this type

- Place his outer leg at a lower layer from his shirt/body.

I'm sure this has come up before but can't find anything on it. Let's say I have a top down game with a number of player and enemy instances (think all-out warfare, where they're all heading towards

I've forgotten this one and couldn't find the answer in the cookbook, but I know this is a really easy question... what do the little blue circles (one solid overlapping an outlined one) at the top r

(Quote)