How to stop guests from exiting a VR game on Meta Quest and Pico

It happens on every VR floor: five minutes into a session the guest presses a button on the controller, the game disappears and they start browsing the headset menu. Some open the store, some the browser, some accidentally reset the play boundary. The operator is busy with another headset and the queue is waiting. Here is why headsets allow this, what they offer to prevent it, and what actually works in a venue.

Why the headset lets guests out

Meta Quest (formerly Oculus Quest) and Pico headsets are made for home use. The owner is expected to decide what to run, so the button that returns to the system menu works from any game, at any moment, with one press. The standard firmware has no venue mode: the maker assumes the headset belongs to one person, not to a stream of strangers.

For a venue that creates three separate problems, and it helps not to lump them together:

• The guest loses session time. They exit, get lost in the menu, call for help — and the minutes they paid for run out.
• The guest changes the headset. A reset boundary, a different language, altered brightness or audio — and the next guest inherits the mess.
• The guest reaches the store and the account. The worst case: one-click purchases, signing in to a personal account, installing apps you never approved.

What the headset offers on its own

Built-in tools solve part of the problem. It is worth knowing exactly which part.

Turn these on — they close off money and personal data. But none of them answers the real question: how do you keep a guest inside the game they paid for?

Headset makers also run business programs and business editions of their hardware, some of which include a single-app, or "kiosk", mode. That can suit a trade-show stand running one demo all day. A venue is different: the guest changes every half hour and so does the game, and you still need paid sessions and a timer. Programme terms and availability also vary by region and change over time, so check the current situation with the maker. We compare those options in detail in kiosk mode on Pico 4 and Meta Quest.

What not to do

Search for this problem and you will find advice to root the headset, install custom firmware or replace the system launcher. For a venue these are bad trades:

• Rooting and custom firmware can void the warranty. Venue headsets run for hours every day; repairs are a matter of when, not if, and you want them covered.
• Updates stop working properly. Modified headsets either will not update or lose their setup when they do, and the fleet drifts apart.
• Third-party launchers clash with other apps. A replacement shell typically relies on system permissions that other apps also need, and after an update things start freezing for no visible reason.

What works in a venue

The practical answer is not to block the menu button — the system will not let you — but to make leaving the game pointless. The moment a guest exits, a splash screen appears on top of the system menu and stays there until the session is resumed. The guest sees your venue's screen, not the store.

To do that, the software on the headset needs to:

• notice what is on screen within seconds, not on a once-a-minute check;
• cover system screens — library, settings, store — not only other games;
• return the guest to the paid game without the operator walking over;
• accept an operator override code for the rare case when a guest really must exit;
• refuse to launch any game at all when no session has been paid for.

Floor habits that help

Software does the heavy lifting, but a few habits reduce exits in the first place:

• A 20-second briefing. Show the guest which buttons the game uses and which one to leave alone.
• Hand over a running game. Launch the game before the headset goes on, so the first thing the guest sees is the game, not the home screen.
• Check the boundary between guests. A quick look after each session catches a reset boundary before it confuses the next player.
• Keep accounts locked down anyway. A purchase PIN costs nothing and closes the most expensive mistake.

How UnitVR handles it

In UnitVR a headset will not launch games unless a session has been started for it from the operator panel. If the guest leaves the game, a splash screen with your venue's branding appears over the system menu; only the operator's override code removes it. This works on Pico 4, Meta Quest 2, Meta Quest 3 and Meta Quest 3S without rooting or custom firmware. More on the features page, or start the free 7-day trial from pricing.

Summary

• The headset's own settings cannot stop a guest leaving the game — that is by design.
• Purchase PINs and parental controls are worth enabling, but they protect money and age limits, not the session.
• Rooting, custom firmware and replacement launchers cause more trouble than they solve.
• What works: a splash screen over the menu, automatic return to the game and no launch without payment.

For the full list of what venue software should cover, see VR arcade management software: what it should do and how to choose.