@Bryan just move to layer behaviours, one for each layer, each with a different layer selected: [image: 622a0bdf-34b8-4190-9233-4b558d235fe7.PNG]

@Bryan put all the objects in a tag (including object detecting the collisions), use a loop to count the number of objects in the tag (subtract 1 to exclude self), if number of objects colliding is equal to number of objects in tag except self ( can't collide with self), then the object is currently colliding with all objects in the tag. This is shown in the first screenshot: [image: 3de1e38b-093d-404c-b211-2ae2d2a6dbaa.JPG] To detect whether the object has ever collided with each object instead of detecting whether the object is colliding with all at the same time is similar, but the object detecting the collision is instead given a unique ID based on a global variable (so you can have multiple detecting objects that don't interfere with each other). A dynamic attribute is applied to all objects in the tag that it collides with so it only counts each object once. This is shown in the second screenshot: [image: 6e09fcf6-9f85-4df7-bfcd-14a2fc040430.JPG] The behaviours in both screenshots should work with spawned object and multiple detectors too, but if you don't have this they can be simplified down a bit (you don't need to count objects if you know how many there are and don't need and ID if there is only one object anyway. EDIT: to clarify, "set attribute" is the global variable, with a value equal to "ID (Add Values)", and "set attribute2" is a dynamic attribute with a value of 1 and the key "combine text".

Saw that and addressed his question. We've actually had the pricing page changed for a while now, it's just not live until the next update goes out.

@Jack8680 @T-Studios thanks

@Evolution why not? It's at a fixed angle, if you set the z layers right it should work with a single graphic per cube, right?

@Jack8680 I don't know yet. We don't want to add too many extra features for the first version since it will just end up taking longer to get out.

@iTap-Development That sounds nice.

@Jack8680 Thanks, it's working perfectly 👍

@Hamed ok, thanks for the help!

@Lupo HyperPad isn't GamePress. It was rewritten from scratch. Certain changes were made for performance reason, and other changes for usability.

Yeah I know I'm in all my file I have no other files.

Interesting. If you want it to reflect off objects you could set the velocity when it spawns, then put all the objects you want to reflect off in a tag and then use the collided behaviour with the tag selected and either multiply the x velocity by -1 and set to that. Or use collided on left, set velocityX to positive value; collided on right, set velocityX to negative value.

Hi Aries, Best thing to do is fill out the personal support form. It'll be automatically forwarded to Hamed, rather than wait for Hamed to see this post. The forum should be used for general questions that the community can help with.

@iTap-Development I would recommend Swift: it is more current, and it is easier to learn. Swift is also a lot like Javascript - and that is something.

@Aidan-Oxley if you give a project a name that already exists you get a popup asking if you want to overwrite.

@Murtaza ok thanks! 😆

How are you making your item box? Are you making it spawn an object? Maybe it's spawning it self and it's causing too many to spawn resulting in lag. Or maybe the graphics are too large. More details on how your project is created would help.

Hi Wazk Mobile, This sounds like a really good idea! I hope you get someone who wants to work with you, however my team is working on massive games that we would rather search for a publisher who could go without the 'ad's' and 'splash texts'. Maybe in a few months time when our project is a bit more developed, maybe we could show you and you could consider not having the splash screen or anything else? If we work with you in the future we look forward to it. Cheers, Ash