Make wet, burning and cold effects cancel each other, whatever the order

Rain on a burning hero, frost on a soaked one: survival games love these reactions, but they turn into bugs when the result depends on which spell came first. This entry gives a small table where each pair gives the same answer in both orders.

Why this works

Players trust a world when the same two things always give the same result, in either order. If the outcome depended on what came first, it would feel like a bug, but when effects simply cancel they feel like physics a player can plan with.

When not to use it

Skip it when you have only one or two kinds of attack, or when you want a rich combo system where order and timing are the skill. Then give each combination its own written outcome rather than cancelling.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 33 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 "Make wet, burning and cold effects cancel each other, whatever the order" (read_entry rain-and-fire-and-frost-reactions) 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