-
-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Gibson Bell edited this page Aug 14, 2026
·
3 revisions
QBSheet is an electronic scoresheet for quiz bowl. It runs in a web browser. It works offline.
A room can score a complete game from one QBJ file. The room does not need an account, a database, or a network connection.
QBSheet reads and writes QBJ files. QBSheet also connects to tournament control software with QBTCP.
| Your role | Read this page |
|---|---|
| You score games in a room | Start here |
| You run a tournament and you hand out files | Score a game from a file |
| You run tournament control software | Score a connected game |
| You prepare Chromebooks before an event | Prepare a device |
| You lost a game and you want it back | Recovery and backups |
| You write other quiz bowl software | QBTCP for implementers |
| You host the application | Install and host |
| You change the code | Develop and contribute |
- Files are QBJ. One format holds an assignment, a result, and a mid-game backup.
- The network is QBTCP. QBTCP is the live conversation between a scoresheet and tournament control software.
- The device keeps the game. The browser writes every scored question to local storage first. A lost network connection does not stop the scoresheet.
- QBSheet does not calculate tournament standings. Tournament control software does that.
- QBSheet does not guess a scoring format. If the file does not give the rules, QBSheet asks you.
- QBSheet does not send a game to any server other than the tournament control server that you type in. There is no analytics code and no telemetry code.
- QBSheet does not delete your local copy of a game because a server accepted it.
QBSheet is available under the GNU Affero General Public Licence, version 3 or later. QBSheet comes
from the first-party scorer in YellowFruit and Fruity. The NOTICE.md file in the repository
records that history.
QBSheet · AGPL-3.0-or-later · The specifications in
docs/ are normative. This wiki is a guide.
Report a security problem with
SECURITY.md. Do not open a public issue
for a security problem.