Work out which files a returning player must download after an update

If every update makes players download the whole game again, they stop updating, and if files keep their names the browser may keep showing old ones. This entry shows the AI how to compare two builds and list exactly what changed, moved or can go.

Why this works

Whether a file changed is a matter of its content, not its date or name. A fingerprint of the content lets you tell untouched, changed, moved and gone apart, so players fetch only what is new, and a fingerprint in the name stops old copies from lingering.

When not to use it

For a tiny game, the bookkeeping is more work than a full download, and it only pays once updates are frequent and the package is large. If the game is a few small files, simply serve everything fresh and skip the list.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 34 lines of example code with 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Work out which files a returning player must download after an update" (read_entry update-only-changed-files) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP