Keep the download size of your game in check, and see which files grew

A game built by chat grows quietly: one more music track, one bigger picture, and the download is twice as large as last week. This entry shows how to set a limit per kind of file, warn before it is crossed, and point at the files that cause it.

Why this works

One limit for the whole game lets the biggest kind of file eat everything while the total still looks fine. Giving each kind its own budget, and checking after every build, turns slow growth into a warning while it is cheap to fix, and each kind has its own remedy.

When not to use it

Skip it for a small game that is far below any limit a player or a store would care about. Also, size is not the same as loading time: if the real worry is a slow first start, measure that and load big files later.

In the full entry

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

Say this to your AI

Use the Spielerando entry "Keep the download size of your game in check, and see which files grew" (read_entry build-size-budget-by-kind) 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