Stop Shipping Fest Demos Without a Player-Visible Build Label - 2026 Opinion

A player posts in Discord: “Menu crash after the patch.” You ask for logs. They send a screenshot with no version string. You promoted three depots this week. Your BUILD_RECEIPT knows fest-demo-2026-10-rc6—the player’s binary does not.

October 2026 fest volume turns support into archaeology. Teams that file beautiful receipt JSON internally but ship silent UIs waste the entire observability stack: crash symbolicate evenings, refund correlation playbooks, and Deck log listicles all assume someone can say which build failed.

This Opinion & Hot Takes piece makes a narrow claim: every fest_public demo must show a player-visible build_label that matches BUILD_RECEIPT and your promotion log—not only Steam’s opaque buildid, not only CI job numbers, not only a wiki page players never open.

Non-repetition note: Developer console opinion covers debug surfaces; Ren'Py seven-day label freeze covers VN classification discipline; GX multi-channel resource covers HTML5 dual-upload receipts. This URL owns why the label must be visible to players on fest demos.

Who this opinion is for

Why this matters now (October 2026)

1. Multi-promote fest weeks — Founder time-box worksheet assumes hotfix depots; without visible labels, support cannot keep pace.
2. Playtest vs fest_public isolation — Playtest scope playbook fails when players cannot prove which surface they installed.
3. Refund and crash correlation — Refund dashboard rows key on build_label; player reports without labels become unmergeable noise.
4. Stream and clip culture — OBS overlays and highlight reels need readable labels; VO reel safe zones already treat build_label as a first-class overlay element.
5. Publisher diligence — Q4 telemetry expectations (planned sibling) assume players and partners can reference the same build string.

Direct answer: Show build_label in credits, title footer, or hold-to-view debug panel on fest_public; file visible_build_label_receipt_v1.json before promotion; fail smoke if UI string ≠ BUILD_RECEIPT.

The opinion in one paragraph

Retail fest discipline means the person playing your demo can answer “what build is this?” without opening Steam client properties, without joining a developer-only Discord, and without guessing from file dates. Internal-only build_id discipline is necessary but insufficient—if the label is not on screen (or behind one obvious, documented gesture), you have outsourced correlation to support volunteers during your highest-traffic week. That is not indie charm; it is operational debt you chose to ship.

What counts as “player-visible”

Minimum bar: A player following your fest FAQ can report build_label=fest-demo-2026-10-rc6 in one screenshot.

Beginner path — one evening label

Success check: A non-dev friend reads the label aloud from a photo you did not stage.

Developer path — gates V1–V6

Optional seventh check: label visible in Wednesday smoke screenshot attachment.

visible_build_label_receipt_v1.json

{
  "schema": "visible_build_label_receipt_v1",
  "build_label": "fest-demo-2026-10-rc6",
  "surface": "fest_public",
  "display": {
    "location": "credits_footer",
    "gesture_required": false,
    "font_min_pt": 9,
    "screenshot_path": "release-evidence/ops/visible-label-rc6.png"
  },
  "parity": {
    "build_receipt_match": true,
    "upload_log_match": true,
    "steam_buildid": "21457823",
    "steam_buildid_maps_to_label": true
  },
  "privacy": {
    "contains_user_id": false,
    "contains_machine_id": false,
    "exceptions_documented": []
  },
  "gates": {
    "V1_visible_on_cold_install": true,
    "V2_matches_build_receipt": true,
    "V3_matches_upload_log": true,
    "V4_steam_buildid_mapped": true,
    "V5_privacy_ok": true,
    "V6_receipt_committed": true
  },
  "promotion_allowed": true
}

Store under release-evidence/ops/ beside BUILD_RECEIPT. Link path in optional BUILD_RECEIPT column visible_build_label_receipt_path.

Single source of truth (do not fork strings)

CI / local build
    │
    ├─► generated_build_label.h (or .gd, .cs)
    │         │
    │         ├─► in-game UI Text
    │         ├─► BUILD_RECEIPT.json
    │         └─► upload_log.csv
    │
    └─► steamcmd / Steamworks promote notes (human copy)

Anti-pattern: Artist types version in credits while engineer updates JSON manually—classic rc5 UI with rc6 receipt.

Engine sketches (illustrative)

Full engine chapters belong in guides; this opinion only demands one generator, many consumers.

Privacy exceptions (when not to show raw ids)

Never put in visible label: Steam account id, email, hardware serial, playtest invite codes, internal employee names.

Multi-channel VERSION parity

Teams shipping Steam + itch + GX must show the same build_label on every fest_public channel or prefix channel explicitly:

Mismatch without suffix is worse than no label—players cross-compare channels and call fraud.

Pair with 14 GX multi-channel tools and itch WASM smoke tutorial.

Support workflow (Discord template)

Thanks for the report. Please send:
1) Screenshot of the build label (Credits → bottom line, or hold Select for Build Info)
2) Platform (Windows / Deck / Linux)
3) What happened in one sentence

Do not send save files until we confirm build_label.

Pin template during fest week. Train moderators: no triage without label.

Pairing with observability receipts

Without V1–V2, downstream receipts become internal fiction.

vs developer console (complementary opinions)

You can show label in a non-cheating debug panel; you cannot hide label while leaving giveGold() callable.

vs menu FPS cap opinion

Menu FPS cap addresses hardware trust signals. Visible label addresses support correlation. Ship both—label text in corner does not excuse 400 FPS menus.

Wednesday smoke extension (producers)

Add to weekly smoke checklist:

• [ ] Screenshot includes readable build_label
• [ ] Label matches BUILD_RECEIPT row for candidate promote
• [ ] visible_build_label_receipt_v1.json updated or promotion_allowed: false

Ten extra minutes beats forty-eight hours of Discord guessing.

Seven failure modes (composite patterns)

Proof table (promote week)

Working dev — jq parity check

LABEL_UI="fest-demo-2026-10-rc6"
LABEL_RECEIPT=$(jq -r .build_label release-evidence/ops/BUILD_RECEIPT.json)
test "$LABEL_UI" = "$LABEL_RECEIPT" && echo OK || echo MISMATCH

Run in CI after packaging step, before steamcmd.

Publisher one-liner

Fest_public builds display build_label matching our BUILD_RECEIPT and upload log; visible_build_label_receipt_v1.json is in the evidence folder.

Attach screenshot. Pair with Q3 diligence packets when asked for ops maturity.

Hour theft audit (support leads)

Steamworks note (not a metadata checklist)

18 Steamworks resources cover depot promotion and SteamPipe—this opinion does not duplicate branch naming checklists. It adds: after promote succeeds, verify the installed binary shows the label you logged.

Counterarguments (and answers)

Opinions are for tradeoffs you already made unconsciously—this one chooses support truth over aesthetic minimalism.

Localization and accessibility

Accessibility is not optional for a string that prevents mis-triage.

CI wiring (working dev, minimal)

1. Generate build_label.txt in build job from git describe + fest branch.
2. Embed into game via pre-build step (engine-specific).
3. Copy same file into BUILD_RECEIPT.json generation script.
4. Assert post-build: parse packaged UI screenshot OCR optional; minimum: read exported version.txt beside binary.
5. Block promote if visible_build_label_receipt_v1.json missing from artifact upload.

Pair with GitHub Actions cache bust tutorial (planned backlog #13) for “green CI, wrong label” class failures.

Unity evening sketch (beginner)

1. Create Assets/Resources/BuildLabel.txt from CI.
2. TextMeshPro in credits reads Resources.Load<TextAsset>("BuildLabel").text.
3. Export Windows demo; open *_Data folder—confirm file baked.
4. Add visible_build_label bool to BUILD_RECEIPT template.

Godot evening sketch (beginner)

1. Autoload BuildInfo.gd reads res://build_label.txt.
2. Label node visible = true on credits scene.
3. Export preset stamps file via export_presets.cfg hook or shell copy pre-export.
4. Run Godot save isolation preflight cousin—different surface, same receipt culture.

Ren'Py and VN teams

VN demos already show config.version on some title screens—opinion requires that string equal BUILD_RECEIPT and survive translation freeze. Do not rename config.version mid-fest without bumping receipt and UI in same promote. Full freeze discipline: seven-day Ren'Py challenge.

Construct / NW.js teams

Export version.txt next to .exe; load at boot into DOM Text object. Verify packaged path, not preview. Pair NW.js console opinion—label in DOM is fine; devtools are not.

Extended pattern — refund screenshot without label

Composite support arc (no invented metrics):

1. Player refunds citing “crash after update”
2. Refund row lacks build_label join
3. Team searches Steam comments for version hints
4. Engineer finds three active depots
5. Symbolicate run uses wrong symbols
6. Hotfix ships to wrong branch
7. Social post claims “lazy devs”

One visible string collapses steps 2–5 into a ten-minute correlation. That is why refund playbook assumes labels exist on both sides of the join.

Extended pattern — playtest leak

1. Playtest invite build shares marketing name with fest demo
2. Streamer installs wrong depot
3. Bug report references feature not in fest scope
4. Team reproduces on internal branch
5. Fest demo “unfixed” narrative spreads

Prefix labels: playtest-… vs fest-demo-…. Isolation playbook plus visible label makes mistakes legible.

BUILD_RECEIPT template columns (optional)

Add to your template JSON schema comments:

"build_label": "fest-demo-2026-10-rc6",
"visible_build_label_receipt_path": "release-evidence/ops/visible_build_label_receipt_v1.json",
"visible_label_location": "credits_footer"

Document in top-20 hub row 8b cousin row if you maintain a living index table.

Facilitator README row (playtest ops)

Add to facilitator doc (pairs 18 playtest tools):

Async playtest without label is anecdote, not data.

Key takeaways

• Fest_public demos must show player-visible build_label.
• Label must match BUILD_RECEIPT and upload log (V2–V3).
• File visible_build_label_receipt_v1.json before promote (V6).
• Credits footer is the beginner-default surface.
• Privacy exceptions are allowed but must be documented (V5).
• Multi-channel labels need suffix discipline or exact parity.
• Discord template should require label screenshot first.
• Pairs crash symbolicate and refund correlation.
• Distinct from dev console and Ren'Py freeze challenge.
• Extend Wednesday smoke with label screenshot.
• Single generator for UI + receipts—never dual-entry.
• Steam buildid maps in receipt (V4) for engineer audits.
• October 2026 multi-promote weeks make hidden labels unaffordable.
• Founder time-box assumes support hours—labels reduce waste.
• promotion_allowed: false when gates fail—do not hope players guess.

FAQ

Is Steam’s buildid enough?
No for player support—most players never open client build properties. Engineers may log buildid in receipt V4 in addition to visible label.

Semver in store page vs fest label?
Store semver can differ; fest label should encode fest branch identity (fest-demo-2026-10-rc6).

Hide label behind secret key combo?
Allowed only if FAQ documents gesture and moderators train players—default to credits visibility.

Does label replace BUILD_RECEIPT?
No—receipt is authoritative; UI is the player-facing mirror.

Anti-cheat concerns?
Use non-guessable suffix if needed; still visible, not security through obscurity.

HTML5 demos?
Show label on boot splash or pause menu; pair GX/itch receipts.

What if label overlaps HUD?
Move to credits—not an excuse to omit.

Internal playtest builds?
May use playtest- prefix in label; never promote playtest label to fest_public without changing string.

Streamer hides HUD?
Burn-in label in OBS setup or require pause-menu label—document in facilitator README.

Publisher wants only semver?
Provide semver and fest build_label in diligence zip README.

Can we rotate label nightly during fest?
Yes—each promote updates UI, receipt, and moderator pin in the same commit. Never rotate receipt without promote.

Month-before-fest adoption ladder

Evidence folder layout

release-evidence/
  ops/
    BUILD_RECEIPT.json
    upload_log.csv
    visible_build_label_receipt_v1.json
    visible-label-rc6.png
    fest-week-capacity-2026.md   # optional, pairs time-box worksheet

Keep ops receipts together so Thursday row review finds label proof in one glance.

Moderator escalation tree

Player report arrives
    │
    ├─ Screenshot shows build_label? ──NO──► Reply with template (ask credits photo)
    │
    YES
    │
    ├─ Label matches current BUILD_RECEIPT promote candidate? ──NO──► Ask reinstall / verify branch
    │
    YES
    │
    └─ Route to engineering with label + platform + one-line repro

Escalation without label is deferred, not ignored—protects engineers from false repro on wrong depot.

Streamer and press kit note

Press kits should include where the label lives (“bottom-right credits, 9pt monospace”). Reviewers are players; they will not read your Notion ops doc. If you burn in label for capture, match in-game string exactly—highlight reel typography already warns against covering the label with waveform thumbs.

Relationship to planned backlog siblings

Shipping this opinion early makes later cluster rows cheaper—you stop debating whether players can name the build.

Conclusion

Observability without a visible build string is a filing cabinet players cannot open.

Show the label. Match the receipt. File visible_build_label_receipt_v1.json. Train Discord to ask once.

Next reads: BUILD_RECEIPT beginner pipeline, Crash symbolicate evening, Wednesday demo smoke, Top-20 evidence receipts.