Maximum health grows a little every time the game is saved and loaded

The hero wears a ring that adds strength, and after a few sessions the numbers are far too high. The save kept a figure that already contained the ring, and the game added the ring again. Here is what to save instead so totals never creep.

Why this works

A result that comes from rules should not be kept like an ingredient. If the save holds the cooked number, then loading cooks it again and the effect is counted twice. Keep the ingredients and let each load recipe produce the same dish.

When not to use it

Do not recompute when a value is meant to grow for good through play, such as a permanent boost from a rare potion. That is part of what the hero is, so store it in the base. Calculated numbers are for things that come and go.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 32 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 "Maximum health grows a little every time the game is saved and loaded" (read_entry rpg-max-health-grows-each-load) 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