How patches get ingested
The agent is only worth having if it knows your game as it is today. When you ship a patch, we re-ingest the new build so the agent’s numbers move with it, and your connected sources stay in sync. You don’t have to send us anything.
What happens when you patch
When a new version of your game goes live, we pick it up and refresh the agent’s data from it. New costs, new units, rebalanced stats, added content: once the refresh lands, the agent answers from the new numbers and stops quoting the old ones.
There’s nothing for you to upload or trigger. The refresh runs from the shipped build.
Turnaround
Most patches are reflected within a day of going live, often the same day. A large content update can take a little longer. If you have a major patch coming and you want the agent current the moment it drops, tell us ahead of time on Slack and we’ll line the refresh up with your release.
If your community will hit new content the hour it ships, give us a heads-up before release day. A planned refresh beats a reactive one.
The gap before a refresh
Between your patch going live and the refresh landing, the agent may still answer from the previous build. You can watch for this in your analytics: a jump in low-confidence answers right after a patch usually means the data is briefly behind. It settles once the refresh completes.
If a patch changed something big and you’d rather the agent hold back than quote a stale number, you can pause it for the short window until the refresh lands.
Connected sources
Patches refresh what the agent knows from the published game. If you’ve connected source code or design docs, those stay in sync as they change too, so the agent keeps up with more than the build alone.
Telling us about a change
We track your game’s releases, but you know your roadmap better than we do. A quick note before a major update, a big rebalance, a new game mode, or a season, helps us get the refresh right the first time. Send it however is easiest: Slack or support@atcampfire.xyz.