core/remote_content_pack
library
Classes
-
ContentPackHistoryEntry
-
One verified, previously-applied content revision (ENH-96) — metadata
only, by design: never the content body itself. Exposed via
RemoteContentPack.history / RemoteContentPack.diagnosticsSummary so a
support/live-ops investigation can answer "which content version was
active when this happened" without ever handing back a player's actual
game data (a level layout, a shop catalog, whatever
T represents).
-
RemoteContentPack<T>
-
A typed, signed remote content slot — live-ops content (a level
definition, a shop catalog page, an event schedule) pushed from a
server without an app-store review cycle, built on the same 3 pieces
RemoteConfigService, VersionedJsonStore and
save_integrity.dart
already provide separately (IDEA-37): asset-fallback-then-fetch,
schema-version migration, and HMAC signing.
