Frequently asked questions

Open the Join page and enter the six-character game code and a name, or scan the QR code shown by the host. Players do not need accounts. If the QR link points to localhost, the host must configure Game:PublicBaseUrl with an address reachable from player devices.

Yes, when the host opens late joining with the lock control. A new player appears as pending until the host approves them. A returning player may also require approval before becoming active again.

The first player to join opens the first round. A correct answer transfers the choice to that player; incorrect answers or a question with no correct answer do not. The host may select a player manually or randomly. Later rounds begin with the weakest player according to the game standings rules.

The buzzer may open automatically or when the host activates it. The first accepted press pauses the shared buzzer timer and starts the answering player's timer. After an incorrect answer, the buzzer reopens for eligible players and the shared timer continues from its remaining time.

Only the player who selected the question answers it. The player announces a wager and the host enters it before revealing the question. The minimum is 5 points; the maximum is the greater of that player's score and the highest question value on the current board. A correct answer adds the wager and an incorrect answer subtracts it.

Eligible players privately submit a wager and then an answer from their devices. The minimum wager is 5 and the maximum is the greater of 1,000 and the player's score. Negative-score players participate by default unless the host disables this setting. Wagers and answers stay private until the relevant phase is locked.

Yes. Open Answer history during the game to change the player, correctness, or score value, add a missing record, or delete an erroneous record. The previous score contribution is reversed and the corrected result is applied consistently.

The reconnect token restores the same player and the server sends the current game state again. During a running game, the host may need to approve the returning connection. Reloading does not create a second score entry for the same player.

Players can choose a built-in avatar, upload a picture, or enable a webcam. When the webcam is unavailable, the selected picture or avatar is used as a fallback. Avatar and picture preferences are stored in that browser by normalized player name and restored for later games on the same device.

Global settings are persistent defaults for future games. Creating a lobby copies those values into an independent game snapshot. The host may customize that lobby before starting without changing the global defaults; once the game starts, its settings are locked.

Yes. Completed games are stored in SQLite with players, final scores, regular questions, and recorded answer results. The host can review them from Game history. Deleting a quiz archives its definition so existing history remains available.

Quizzes, active games, and completed history belong to the authenticated host who created or launched them. Other host accounts cannot access that data. Player join and gameplay pages remain available without player accounts.