When Fire Stopped Firing
A mouse-input fix for the first alpha: fire and aim survive browser event handling, looking keeps working while you shoot, and failed mouse capture tells you how to retry.
You Pressed Fire. The Browser Had Other Plans.
The first alpha brought a mouse-input problem reproduced in Firefox: Babylon could cancel a pointer event, the browser would suppress the matching mouse event, and the game would lose fire or aim.
This release fixes that path and keeps button state consistent through button combinations, cancellation and focus recovery.
Keep Looking While You Shoot
The gameplay scene preserves the compatibility mouse events it needs, so holding a firing button no longer stops mouse-look.
Extra mouse buttons also stop falling through to the left-button fire binding. A side button should not become a trigger just because it was missing from the expected list.
Capture Failed? Say So.
Joining a match, changing a kit or resuming can all need the browser to capture the mouse again.
When that capture fails, the game now gives visible retry guidance instead of leaving an unhandled error behind. You get a way back into the match rather than a mouse that appears to have stopped listening.
It is a small release with a straightforward job: keep the controls under your fingers working.