Message.exit is not triggered but message.enter == false work fine

[Asatte]

On the on_message function, I used message.exit for my previous projects. But, after updating to 1.10.1 (may not be the reason), exit is not triggered. After some try and fail figured using message.enter == false works as I want. Did something changed with the engine or is that the result of something else?

[britzl]

@Asatte

But, after updating to 1.10.1 (may not be the reason), exit is not triggered. After some try and fail figured using message.enter == false works as I want. Did something changed with the engine or is that the result of something else?

We did add Box2D 3 as an opt-in feature. Are you using the new version of Box2D? Could you please share a minimal project?

[Asatte]

Modified a simple project repeating the same behavior:
Collectibles.zip (110.6 KB)

[britzl]

@Asatte

On the on_message function, I used message.exit for my previous projects. But, after updating to 1.10.1 (may not be the reason), exit is not triggered. After some try and fail figured using message.enter == false works as I want. Did something changed with the engine or is that the result of something else?

Hold on, there’s never been a message.exit has there? It’s always been like this that message.enter == false means that there is no longer any overlap.

[Asatte]

Wait, you’re right. I cannot remember where did I see it but I’m sure I’ve seen message.exit (it’s also an autofill option on my project?) but when I tried to search for it again, I could not find it.
I guess this was a weird misunderstanding on my side. Thank you for pointing it out