Health is cut down on loading because the gear that raised it was not back yet

The hero saved at full health, and after loading is already hurt, or a spell loses its target. Parts of the game were restored in the wrong order, so one part looked at another that did not exist yet. Here is how to put the order in writing and check it.

Why this works

Some things only make sense once others exist, like a limit that needs the thing it limits. Writing down what each step waits for lets the order work itself out, and a mistake becomes a loud error at startup rather than a quiet loss later.

When not to use it

Do not build a dependency list for a small game with only a few restore steps. A short, fixed order written in one place is clearer. The list earns its keep when many people or many systems keep adding new steps.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 22 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 "Health is cut down on loading because the gear that raised it was not back yet" (read_entry rpg-load-order-health-after-gear) 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