Two items in my data have names that look the same and the game picks the wrong one

When a list holds both a fire sword and a fire_sword, the game quietly uses one and ignores the other, and no error appears. This entry gives your AI a lookup that groups names that only differ in spacing, dashes or capitals, so you can choose one.

Why this works

Games that load data into a lookup keep one entry per key, and the later one wins. When two names differ only in decoration, one silently replaces the other, so a normalised key exposes the pair that the lookup hides.

When not to use it

If two things should truly be separate, such as a plain ring and a ring of fire, this does not touch them, since only decoration is ignored. Never use it to merge words that differ by meaning.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 28 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 "Two items in my data have names that look the same and the game picks the wrong one" (read_entry rpg-lookalike-ids-in-data) 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