I noticed what I believe to be a bug with the condition "[Negated] Overlapping an object" in all recent builds of MMF2. I tried it in 253 and 254, but I'm not sure how long it has existed for. I only realised it on the weekend in Ludum Dare.
I have the condition:
"[Negated] Object A is overlapping Object B" > Set counter to 1.
If there are no instances of Object A or B then the event does not trigger, and the counter remains at 0.
If there are instances of both Object A and B, or the condition "Number of object A > 0 AND number of Object b > 0" then the event does trigger as expected, and the counter is set to 1.
My expected behaviour for when there are no instances of one of the objects, is that the event "[Negated] Overlapping an object" > Set counter to 1, should still set the counter to 1.
I can understand why this is happening, but I don't think it is intuitive and I don't think anyone would expect it to work this way.
Here is my simple example file that isolates the issue: Not overlapping unexpected behaviour.mfa