that's a good idea but I think before that, a debug system need urgently be made for large projects.

Guif0DA what do you mean? have objects on runtime added to the family?

not aware of anything that was in c1 and not in c2 dealing with families

I mean the problem from the first post in the topic, the random creation of sprites inside family if u select to create the family. in C1 it was possible to control that so you could select exactly the object from a family u would want to by selecting create family.

Unfortunaly this hasn't been implemented in C2 I had the same problem too. Let's hope someday they listen us and let us decide what will be spawned inside the family on creation like it was possible in C1.

I don't think it's as obvious as you say. If the edges of two objects are at exactly the same position, do they overlap? It depends on where you say the object ends - does it end just before its edges, or does it include its edges? Unfortunately we can't change it, mainly because the Platform behavior heavily depends on this.

I understand that for reasons you know better than anyone it can't be changed but I'm just adding my point of view, if an object with the size 20x20 is located in the coordinate 0,0 and another object with the same size 20x20 located in coordinate 20,0 then they are side by side, they are touching each other, it's like touching a finger with another one, they do not overlap, but if the second object is located in coordinate 0,19 then it's already overlapping by 1 pixel.

You said you can't change it, but can you make a new condition that 'truly' act if an object overlap another one and keep the old condition the way it is right now and maybe change his name?

I really have no idea if that would be hard to make, maybe add in the future that feature? I think this would be very useful for more possibilities in a easier way.

Thanks

Closing, this is by design. (Please also follow the bug report guidelines and provide a .capx with every report; if I didn't immediately know this was by design, I'd have still closed it without investigating for failing to follow the report guidelines)

Hey Ashley thanks for the reply, I'll start to follow the guidelines in the future.. about the subject:

But the object isn't overlapping, that's the name of the condition, it's supposed to active while overlapping. If you don't want to fix because of design choice u could change the function name or a better idea, change it's currently name to something different(like is in touch with another object for example) and make a real overlap condition.

Make 2 objects with 64x64 and with collision box around the whole area for example and add an event that when one overlap the other one they will be destroyed.

This event is triggering even when they are side to side with each other... like one is on coordinate 0,64 and the other one is 0,128 and still the event is triggering while from what I understand to make it trigger the object location should be 'inside' the other object.

ThunderZ

I really liked the graphic style

I use alot the MoveTO... it's very useful

Meloo

Your game looks cool, but in my opinion it's too hard lol not sure if that was the intention.

Woww.. some nice stuffs u did here! Nice animations.. made on flash? looks very professional =D

The intention is to economize the number of events making a WASD movement right? If that's the case then it's a good thing for users with the free edition

Continuing.. improving the pathfinding behavior with more options. It can get some new tools like specify how much an object move before changing his direction.. this would be VERY useful on games that are GRID BASED like FF3 For SNES... so the object would move like in a CHESS table, respecting the tiles.