Ship incremental config changes to a game version as patches.
Patches let you make incremental changes to a game version’s
configuration after it’s been created — without standing up a whole new version.
A game version’s configuration cannot be edited once that version is in production. Patch a
dev or staging version, validate it, then promote — production versions are locked to keep live
players stable.
Dashboard
Unity
Unreal
Create and manage a version’s patches on the Game Patches page (Configurations → Game
Patches), while the version is in dev or staging.
Manage a version's patches in the dashboard.
Your game receives the patched configuration automatically — the generated config accessor
returns the patched values for the running game version, so a normal read needs nothing extra
and never has to know whether a patch applied.
// Already patched, if a patch applies to this game version.var gameplay = await FlockClient.Instance.Config.GetGameplayAsync();
Inspecting the patches themselves — listing them, or fetching one by id — is not part of
the Unity public API. Those reads are internal, used by code generation. Use the dashboard
to see which patches exist and what they change.
Flock Resolve Config Data already returns the patched values for the running game version, so a
graph usually needs nothing else — it never has to know whether a patch applied.
To inspect the patches themselves — all patches, by id, or by config — use the config provider in
C++; those reads are not yet exposed as Blueprint nodes.
Qwacks
Flock
Protokite
Data Duck