Change a boss's behavior at health marks, even when one hit skips past two

A boss that gets angrier at two thirds and one third health sounds simple until a big hit jumps past a mark, healing crosses it backwards, or the same change fires every frame. This entry sets rules that make phase changes happen once, in order and only forward.

Why this works

A change in a boss is a story beat that happens once. Treat the phase as progress that only moves forward, and compare it with where the boss already is, so a big hit, a heal or a second look at the same health cannot play the beat again.

When not to use it

Skip it when the boss should change by what the player does, not by health, such as after a puzzle step or when a weak spot is hit. Then trigger the change from that event. A boss that heals back to a calm state also needs different rules.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 26 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 "Change a boss's behavior at health marks, even when one hit skips past two" (read_entry boss-phase-from-health-thresholds) 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