7-Day Unity Addressables Invalid Key Audit Challenge Before Fest Content Update - 2026

Your Tuesday PR moved UI prefabs into a fest-cut Addressables group. Editor Play Mode still looks fine. The installed demo shows UI_START_BUTTON on the title screen—and the console spam says InvalidKeyException. Localization was exported from Weblate yesterday. Nobody audited keys before the strip.

October 2026 teams run localization + Addressables strip in the same week as Steam fest promotion. String Tables empty in player build is the fix article when tables never shipped. Invalid Key at runtime is the triage checklist when one load fails. This Challenges & Community Hooks sprint is the seven-day audit you run before the content-update PR merges—so invalid keys never reach fest_public.

Non-repetition note: Recent Blog-Create passes shipped Deck log export listicle and crash symbolicate tutorial—this is the first Addressables invalid-key challenge URL, not a metadata checklist or Ren'Py freeze.

Why this matters now (October 2026)

1. Strip PRs remove groups to hit depot size—keys in code often reference assets that left the catalog.

2. Weblate export ≠ Addressables catalog — PO clean while LocalizedString still points at renamed entries.

3. Editor lies — Play Mode reads project assets; player builds read built catalogs only.

4. Store-demo mismatch — localized capsules with English-or-key gameplay trigger refund language.

5. BUILD_RECEIPT culture — Wednesday smoke needs addressables_key_audit_ok beside string_table rows.

6. AI-assisted refactors — Copilot and batch find-replace rename prefab paths without updating Addressables addresses; grep catches drift only if you run K1 after every tooling merge.

7. Parallel depots — Playtest branch still includes tables while fest_public strips them; facilitators test the wrong SKU unless build_label is on screen and receipts diff groups per depot.

Direct answer: Seven weekday gates (K1–K7); artifacts under release-evidence/unity/addressables-audit-week/; file addressables_key_audit_receipt_v1.json; hashtag #AddressablesKeyAudit2026 for community accountability; no fest content-update promotion until K7 passes.

Who this is for

Engines: Unity 6.x LTS with Addressables + optional Localization package.
Time: ~35–50 minutes per weekday (~5 hours total). Weekends: review logs only.

Challenge vs help articles (format ladder)

Run the challenge the week before merge; open help when a single gate fails in production.

Before you start — readiness checklist

• [ ] release-evidence/unity/addressables-audit-week/ exists
• [ ] Addressables package installed; Build → New Build → Default Build Script succeeds once
• [ ] One Development Build or fest player build from current main
• [ ] build_label on title screen matches BUILD_RECEIPT
• [ ] List of Addressables groups tagged fest_strip_candidate vs must_ship
• [ ] No gameplay feature work during audit week—keys and catalogs only
• [ ] Playtest form captures build_label + first screenshot of main menu text

Rules of the challenge

1. One owner signs each weekday log (gateK_pass).
2. Fail stops the day—do not start K4 if K3 catalog hash drifted unexplained.
3. Renamed address after K2 → restart from K1.
4. Installed build proof required on K6—Editor-only passes do not count.
5. Pair promotion with Thursday row review.
6. Friday Block 5: addressables_key_audit_pass Y/N.

Challenge calendar at a glance

Beginner path (read this first)

1. Monday — Export a list of every string your C# passes to Addressables.Load* (spreadsheet OK).
2. Tuesday — Build Addressables content; save catalog hash to a text file.
3. Wednesday — Write which groups move to remote/strip in the fest PR.
4. Thursday — Build player; open Build Report; search StringTable, your UI addresses.
5. Friday — Play golden path 10 minutes; save Player.log excerpt.
6. Weekend — Rest; verify folders.
7. Next Monday — Install Steam/playtest build; photograph main menu per locale.
8. Next Tuesday — File receipt JSON; set BUILD_RECEIPT boolean.

Do not rename addresses to “fix” keys without updating code—K1 restarts.

Developer path (fest content-update stack)

1. Automate K1 with grep -R "Addressables.Load" Assets/ → CSV.
2. CI step: fail PR if addressables_key_audit_receipt_v1.json missing on fest-content label.
3. Crosswalk keys against Localization_Local group from string table help.
4. Join invalid_key_count to refund dashboard store-copy tags.
5. Forward FMOD strip help when audio keys fail same PR.

Gate K1 — Runtime key inventory (Monday)

Goal: No mystery strings in load calls.

Steps

1. Search project:

grep -RIn "Addressables\.Load" Assets/ --include="*.cs" > release-evidence/unity/addressables-audit-week/k1_load_calls.txt
grep -RIn "AssetReference" Assets/ --include="*.cs" >> release-evidence/unity/addressables-audit-week/k1_load_calls.txt

2. For each hit, extract literal key or document AssetReference GUID target.
3. Build address_inventory_v1.json:

{
  "schema": "address_inventory_v1",
  "build_label": "fest-demo-2026-10-rc4",
  "keys": [
    { "key": "UI/MainMenu", "source": "MenuController.cs:42", "type": "address" },
    { "key": "LocaleIcons", "source": "LocalizationBootstrap.cs:18", "type": "label" }
  ],
  "orphan_literals": []
}

Pass K1: orphan_literals empty OR each orphan has ticket id.

Fail signals: Hard-coded path strings; duplicate keys pointing at different assets; keys containing stale OldFest prefix.

Gate K2 — Catalog fingerprint (Tuesday)

Goal: Know the catalog you are about to mutate.

Steps

1. Addressables → Build → New Build → Default Build Script.
2. Record Library/com.unity.addressables/.../catalog.json hash:

Get-FileHash ".\Library\com.unity.addressables\aa\Windows\catalog.json" -Algorithm SHA256 |
  Format-List

3. Save to catalog_build_fingerprint.txt with UTC timestamp and build_label.

Pass K2: Hash file exists; matches CI artifact if you use cloud builds.

Gate K3 — Group move plan (Wednesday)

Goal: Document strip before engineers move assets.

group_move_plan.md template

# Fest content strip — Addressables group plan

## Must ship (never strip)
- Localization_Local — String Tables + Shared Table Data
- Boot — Bootstrap prefabs

## Strip / remote candidates
- FestOptional — marketing textures (remote OK)

## Keys at risk
| Key | From group | To group | Owner |
|-----|------------|----------|-------|
| UI/HUD | Default | FestOptional | REJECT — move blocked |

Pass K3: Producer sign-off; no String Table in strip column.

Pair: Weblate freeze help for TMS—this gate is engine groups.

Gate K4 — Build Report enumeration (Thursday)

Goal: Prove assets exist in player data after simulated strip.

Steps

1. Apply group moves on a branch (not main yet).
2. Build Player with Build Report enabled.
3. Export search hits to build_report_key_hits.csv:

Pass K4: Every key from K1 inventory has a matching row In player data = Yes.

Fail: Zero StringTable rows → stop; read string table help before continuing challenge.

Gate K5 — Runtime load smoke (Friday)

Goal: Ten-minute golden path with clean logs.

Steps

1. Install Thursday’s player build.
2. Delete prior Player.log.
3. Play: boot → main menu → first gameplay scene → open settings → return.
4. Grep log:

Select-String -Path "$env:USERPROFILE\AppData\LocalLow\*\*\Player.log" -Pattern "InvalidKey|Invalid key"

Pass K5: Zero matches during golden path.

If matches: Open Invalid Key help; fix; restart K4.

Gate K6 — Installed build locale proof (Monday week 2)

Goal: Visual proof for each shipped locale.

Steps

1. Install candidate from Steam/playtest depot.
2. Screenshot main menu for en, plus each fest locale (e.g. ja, zh-Hans).
3. File locale_screenshots_manifest.json with paths and build_label.

Pass K6: No raw UI_* visible; fonts readable (pixel font pass separate).

Gate K7 — Receipt and BUILD_RECEIPT (Tuesday week 2)

addressables_key_audit_receipt_v1.json

{
  "schema": "addressables_key_audit_receipt_v1",
  "build_label": "fest-demo-2026-10-rc4",
  "catalog_fingerprint_sha256": "abc123…",
  "gates": {
    "K1_inventory_complete": true,
    "K2_catalog_fingerprint": true,
    "K3_group_move_signed": true,
    "K4_build_report_hits": true,
    "K5_runtime_smoke_clean": true,
    "K6_locale_screenshots": true,
    "K7_receipt_archived": true
  },
  "invalid_key_count_golden_path": 0,
  "localization_tables_in_player_build": true,
  "promotion_allowed": true,
  "human_signoff": { "role": "engineer", "utc": "2026-06-03T18:00:00Z" }
}

BUILD_RECEIPT columns

"addressables_key_audit_ok": true,
"addressables_key_audit_receipt_path": "release-evidence/unity/addressables-audit-week/addressables_key_audit_receipt_v1.json",
"string_table_receipt_path": "release-evidence/unity/string_table_receipt_v1.json"

Diff on Thursday row review.

Community hook — #AddressablesKeyAudit2026

Post weekday progress (optional):

Day 3 #AddressablesKeyAudit2026 — group move plan signed; zero String Tables in strip column. build_label: fest-demo-2026-10-rc4

Rules: Post evidence filenames, not entire catalogs; no secrets.

PowerShell: inventory diff (K1 vs catalog)

$inventory = Get-Content "address_inventory_v1.json" | ConvertFrom-Json
# Compare against exported catalog keys from Addressables Analyze tool
# Flag keys in inventory missing from catalog

Unity Analyze → Check for Duplicate Addresses runs Monday after inventory export.

Bash: CI promotion gate (sketch)

#!/usr/bin/env bash
set -euo pipefail
RECEIPT="${1:?addressables_key_audit_receipt_v1.json}"
jq -e '
  .schema == "addressables_key_audit_receipt_v1"
  and .promotion_allowed == true
  and .invalid_key_count_golden_path == 0
  and .localization_tables_in_player_build == true
' "$RECEIPT"
echo "addressables_key_audit: OK"

Gate K1 deep dive — key types beginners confuse

Exercise: Open Addressables → Groups, select your menu prefab, copy Address column exactly into address_inventory_v1.json—compare to C# literal character-for-character.

Gate K4 deep dive — Build Report search terms

Run these searches in Build Report after player build:

Export CSV columns: name, type, size, addressables_group, included_in_player_build.

Gate K5 deep dive — golden path script

Read aloud while logging:

1. Cold start (delete Player.log).
2. Press any required “click to start” for audio.
3. Navigate main menu → new game / continue.
4. Reach first interactive gameplay (not credits).
5. Open pause/settings if exists.
6. Return to menu; quit application.

Duration: 8–12 minutes. Longer sessions hide lazy-loaded keys that fail hour two—add optional K5b row in receipt for “first dungeon load” if your demo needs it.

Localization crosswalk (K3 + K4)

18 localization tools support TMS; this challenge proves engine inclusion.

Promotion week integration

Incident response when K5 fails mid-fest

Do not rename keys in panic without K1 update—players on old catalogs double-break.

Facilitator / QA CSV columns

Add to playtest spreadsheet:

Evidence folder layout

release-evidence/unity/addressables-audit-week/
  README.md
  address_inventory_v1.json
  catalog_build_fingerprint.txt
  group_move_plan.md
  build_report_key_hits.csv
  runtime_load_smoke.log
  locale_screenshots_manifest.json
  2026-05-27_gateK1.log
  …
  addressables_key_audit_receipt_v1.json

Common mistakes

1. Passing Editor Play Mode only — K6 fails later.
2. Fixing keys in code without catalog rebuild — K2 fingerprint stale.
3. Stripping Shared Table Data — empty tables; not always InvalidKey—both fail fest.
4. Using asset file paths as keys — Addressables wants addresses, not Assets/... strings.
5. Skipping K3 sign-off — engineers move groups Friday night.
6. Confusing with Invalid Key help — help is triage; challenge is calendar.
7. Promoting on Weblate green alone — TMS does not rebuild catalogs.

Worked example (composite pattern)

No invented studio metrics—typical October fest strip week pattern.

Key takeaways

1. Invalid keys spike when fest strip and localization land same week.
2. Seven gates beat one panic grep before upload.
3. addressables_key_audit_receipt_v1.json wires audits to BUILD_RECEIPT.
4. Build Report is the truth machine—not the Editor.
5. Help articles fix failures; this challenge prevents them.
6. #AddressablesKeyAudit2026 optional accountability.
7. Pair string table help when K4 shows zero tables.
8. Pair Deck logs when crashes differ per platform.
9. Wednesday smoke runs on same build_label as K7.
10. Forward blog #4 when Proton silent-audio differs from key errors.
11. Cloud CI fingerprints must match local K2—or promotion lies about catalog state.
12. Audit week bans feature scope; typos in tables OK, new routes are not.

Unity 6.6 / Localization package notes (2026)

Smart Strings and Addressables-driven collections increase strip risk:

• Collections often land in Default group—easy to mark remote by mistake.
• LocalizedString references use table entry IDs—renaming entries without rebuild mimics InvalidKey.
• Pseudo-localization in Editor masks missing tables until K6 screenshots.

Developer habit: Create Localization_Local group on project day one; never add it to fest strip spreadsheets. Mirror Unity 6 Localization_Local preflight before first strip PR.

Addressables Analyze checklist (Monday afternoon)

Run in Editor after K1 inventory:

Size strip PR review rubric (for producers)

Reject PRs that:

• Move any asset referenced in K1 without updating inventory
• Place String Tables outside must_ship groups
• Change addresses without catalog_fingerprint update in PR description
• Skip addressables_key_audit_receipt_v1.json attachment on BUILD_RECEIPT

Approve PRs that:

• Include K4 CSV diff in review comment
• List invalid_key_count_golden_path: 0 from receipt
• Link playtest screenshots for non-English locales

Comparison to other engine freezes

Same release-evidence culture—different artifact names.

Partner diligence sentence

“Fest builds include addressables_key_audit_receipt_v1.json with seven-gate proof, Build Report enumeration for String Tables, and zero InvalidKey events on golden-path Player.log for build_label ….”

Attach audit-week zip beside top-20 receipts hub index row.

Standing engineering standup (30 seconds)

1. Catalog fingerprint changed?
2. K5 clean on installed build?
3. Any UI_* screenshot from facilitators?
4. Receipt promotion_allowed still true?
5. Hotfix waiting on Weblate or on Addressables?

If (5) is Addressables, do not merge TMS-only PR until K4 re-runs.

FAQ

We do not use Localization package—still run this?

Yes. K4/K5 still apply to UI prefabs, audio, and gameplay Addressables. Set localization_tables_in_player_build: n/a in receipt with reason.

Remote Addressables for fest—allowed?

Yes if K1 keys resolve to remote catalog entries and K5 smoke runs online. Document remote_catalog_ok in receipt.

How does this relate to Lesson 219?

Lesson 219 — Addressables fest string table receipt is the course milestone; this challenge is the blog-scale calendar.

Can we run challenge in three days?

Compress K1+K2 Monday, K3+K4 Tuesday, K5–K7 Wednesday–Friday only if team already has inventory discipline—otherwise keep seven days.

What if InvalidKey only on Deck?

Run Deck log bundle plus Windows K5—Proton paths differ.

Should we delete unused Addressables during audit week?

No. Deletion is a scope change. Audit week only documents and proves inclusion. Defer cleanup to post-fest.

Does cloud build change K2?

Yes—record fingerprint from CI artifact, not only local Library/. Mismatch between local and cloud is a common K2 false pass.

Sample weekday log (2026-05-27_gateK1.log)

# Gate K1 — 2026-05-27 (Monday)
Owner: [email protected]
build_label: fest-demo-2026-10-rc4
inventory_path: address_inventory_v1.json
keys_enumerated: 47
orphan_literals: 0
analyze_duplicates: resolved (MenuPanel address unified)
gateK_pass: true
next: K2 catalog fingerprint Tuesday 10:00 UTC

Repeat template for K2–K7—auditors grep gateK_pass: true across seven files.

Timebox tip: If K4 Build Report export exceeds 90 minutes, you likely need fewer Addressables groups or a cleaner K3 plan—fest demos should not require enterprise-scale catalogs to pass.

Closing discipline

Half-finished audits hurt worse than skipping: a receipt with promotion_allowed: true while facilitators still post UI_* screenshots destroys trust faster than delaying the content-update PR one day. If K6 fails, set promotion_allowed: false, post the screenshot in the engineering channel, and restart from K3—not from a panic key rename at midnight.

Related reading

• Invalid Key at runtime (help)
• String Tables empty after strip (help)
• Localization tooling resource
• BUILD_RECEIPT beginner
• Wednesday demo smoke
• Thursday row review
• Refund signal dashboard
• Store-demo mismatch recovery playbook
• Lesson 219 — string table fest receipt
• Outbound: Unity Addressables documentation

Next in cluster: Proton Vulkan silent-demo case study (published); blog backlog #5 refund correlation playbook.