Rich Presence Publish & Cache-Reset Checklist
Separate implementation bugs from partner publish and Steam client caching.
How it works
Plan state keys, steam_display templates, and per-language tables in the checklist below.
For “code runs but friends still see old text” — separates publish/cache from implementation bugs.
Do next
- Open partner → configure localization tokens for your app.
- Missing language falls back or shows blank — add english baseline.
- Many teams forget publish step — verify revision live.
- Retry after 15–60 minutes; avoid thrashing rapid edits.
- Client caches presence strings — second machine helps.
- Full quit Steam, not only game restart.
FAQ
- I published but nothing changed?
- Propagation delay and client cache are common. Restart Steam on the viewer side and re-test with a second account.
Related tools
-
RestartAppIfNecessary Bootstrap Generator
Wrapper-aware bootstrap order, C# starter snippets, dual-store notes, and QA relaunch checklist.
-
Steam Callback Pump Scaffold Generator
RunCallbacks placement for client/server, threading notes, feature matrix, regression checklist.
-
Steam Inventory Schema Draft Builder
Categories, tradability, bundles/consumables — draft itemdef-oriented JSON + policy warnings.
-
Workshop Upload Error Explainer
InvalidParam and common codes — ranked causes, path checks, legal/preview metadata checklist.
-
Steam Relay vs Unity Relay Decision Helper
Storefronts, concurrency, cross-store, cost — scored recommendation and phased migration.
-
Steam Capsule Validator
Generate Steamworks-sized PNGs from one master image, ZIP export, safe-area inspector, and policy reminders.