collect a coin and MENU JUMP turns into GAME OVER

Hi guys,
EDIT: problem; all menu-jump turned into game-over.
the world does change, but it uploads the game-over UI, every single time.

 

get this... if the character goes straight to the menu-jump, all good.
if the character collect an action/coin with particles, and then hit the menu-jump, it jumps to game-over!

 

@shlomyone could you take a screen shot of all your menu jumps, and event observers... I'd like to see where they are placed in your ui and mind maps...

 

the menu-jumps are spread within the worlds.
there's only 1 event observer (set as game-over), and it's placed in the UI, one UI to all worlds.

 

there is a bug where if an enemy hits the menu jump, it triggers it... be sure to keep it out of the way... without screenshots, don't know if that's your issue..

https://www.buildbox.com/forum/index.php?threads/enemy-contact-with-menu-jump.2033/

 

that's not the case.
the game is built with multiple worlds, when the character jumps back and forth between them.
so far so good, all works fine.

however, and yes, as weird as it sounds - that what's going on:
if the character picks an action/coin with particles effect, and then hits the menu jump,
it does jump to the world intended, but it also opens the game-over UI.

yes, it need to be read twice...

 

@shlomyone
It's best if you can send an example BBDOC to support@buildbox.com so we can look at the exact configuration you are using.

 

sent.

 

what's the point...

this went just as any support-ticket went so far:
1/ send email to support
2/ only after about 48 hours someone contact back saying "I will look into it"
3/ if you're lucky, you avoid a question from support, which comes usually after 48H as well, so 3 questioms = 3x48Hours take in mind.
4/ finally you get the usual answer: "don't know what it is, let's wait for build2 (3, 4 and now 5) it might solve it"

 

We do use the information you guys send, it is very valuable in making sure an issue gets resolved. I checked this yesterday and moved it to testing, it is no longer a factor in our latest development builds. So it should be OK in the BETA5 release.