Count armour set pieces so two of the same ring do not count twice

A set gives a bonus when you wear enough of its pieces, but players soon find that wearing two copies of the cheapest piece fills the count. This entry counts what should count, keeps the bonuses in steps, and ignores what sits in the bag.

Why this works

A set bonus rewards variety, so what it counts must be variety. Counting different pieces that are worn right now, and recounting after every change, means duplicates and bag clutter cannot buy the reward, and the count can never fall out of step.

When not to use it

Don't punish duplicates when the set is a theme of one kind of gear, such as a pair of identical boots or a full row of the same charm. There, make the bonus count each worn piece, and say so in the item text.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• 25 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 "Count armour set pieces so two of the same ring do not count twice" (read_entry set-bonus-counts-distinct-pieces-only) 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