One class wins 52 percent, so is it too strong or just lucky in its matchups?

In a game where classes counter each other, an average win rate hides the pairs that are really unfair, and games of a class against itself blur it further. This entry shows which pairings to look at and which classes truly dominate.

Why this works

A class can look fine overall and still be unbeatable against one other, because strong and weak meetings cancel out. Looking at each pairing, and leaving out meetings with itself, which are always even, shows where the real imbalance hides.

When not to use it

Skip it when classes are not meant to be even, such as a game where a counter-pick is the whole point, or when you have only a handful of matches per pair. Then learn from playtests and notes, not from a table.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 37 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 "One class wins 52 percent, so is it too strong or just lucky in its matchups?" (read_entry class-matchups-without-mirror-matches) 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