In brief

A shared control must affect every attached game, not just the screen currently open. Hangar routes breaks and reality checks through one protection service, while deposit limits use a guard on the shared cashier.

What you’ll take away

  • A reality check pauses new bets and auto bet until acknowledged.
  • A break blocks new bets and demo deposits; it is different from settling an existing round.
  • Guest protections live in browser storage and are not an externally enforced exclusion service.

Put the control above the game

Hangar creates one Responsible service and attaches the Updraft, Minefield, Dice Duel and Plinko engines to it. Each attached engine receives a block reason. The same service also guards deposits through the shared cashier. This gives a cross-game setting one place to be applied.

The key evaluation question is behavioral: can switching games bypass a block? A disabled button on one game’s interface is insufficient if another engine can still accept a stake. Test the engine’s action as well as the appearance of its controls.

Distinguish a reminder from a blocking check

The default reality-check interval is 15 minutes; the interface also offers 30 and 60 minutes. When the check opens, it reports elapsed session time, amounts wagered and the session result. New bets and auto bet pause until the visitor acknowledges the check.

The platform updates the protection service before advancing the games each frame. That order matters when a browser tab returns from the background: a check that became due should apply before an automatic action can resume. A reminder that displays after another bet has already started would have different behavior.

Follow the limit change and the break

Lowering a daily demo-deposit limit applies immediately. Raising it waits 24 hours. A pending increase is distinct from the currently effective limit, so an interface should make both states understandable. A break blocks new bets and deposits until the break expires.

Blocking a new stake is not the same as cancelling a previously accepted round. For example, an active Minefield round can still be finished. Test the transition into the blocked state with both an idle game and an already-open round; the intended treatment should be explicit.

Document what a local setting cannot enforce

Guest settings are stored in the browser. Clearing site data or using another browser can bypass that local state. Signed-in settings are synchronized to the account, but the demo’s protection and game logic still runs in the client. The presence of a setting does not establish tamper-resistant server enforcement.

These controls illustrate product behavior. They do not demonstrate integration with an external self-exclusion register or establish compliance with a particular jurisdiction. The responsible-gaming page explains the demo limits and links to independent support information.

Sources & scope

Prepared from the Hangar project’s implementation and documentation. Source links point to the inspected revision, so the examples remain traceable as the project changes. These notes describe a software demo, not a certified real-money service.