A wireless controller can return to the browser with a different device index after reconnecting. This update prepares a visible Check controller control beside the movement lab so a player can check the devices the browser currently sees and open Wario’s existing controller chooser. The site-wide reconnect helper is being integrated in the lab’s custom-controller mode.
Keep the controls already in use
Wario uses its own Gamepad API input loop. The helper does not install an emulator input loop, clear controller profiles or trigger gameplay buttons. The existing device selection and saved mappings remain in place, along with RT/R2 switching between Wario and Torpedo. The local testing recorder’s LT/L2 behavior also remains part of the local build.
The public page integration is prepared as a small change around the game window. The gameplay, controller sampler and recorder-routing scripts stay unchanged. The release also prepares an HTML-only cache rule so a fresh visit can pick up a newly published player page without changing the handling of the preserved media.
What is still being verified
This note accompanies the local integration and coordinated release preparation. The checks cover the generated page hook, retained source scripts and preserved earlier journal entries. It does not claim that the shared helper has already been published or that a physical wireless disconnect-and-reconnect test has passed. The final hosted checks and controller test must be recorded with the coordinated deployment.