Taking back a skill point breaks the skills that were built on top of it

Respeccing sounds easy until the player removes a skill that three others depend on, and the tree is left in an impossible state. Here is how to find what blocks a refund, how to refund a whole branch, and how many points come back.

Why this works

A skill that depends on another cannot stand alone, so taking away the base while keeping what rests on it leaves the player with something that should be impossible. Check what leans on a skill before returning its points.

When not to use it

Skip refunds when choices are meant to be permanent and a mistake is part of the story, such as a hard mode. Or let the player rebuild everything at a cost, rather than one piece at a time.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 41 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 "Taking back a skill point breaks the skills that were built on top of it" (read_entry skill-refund-with-dependents) 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