Let players combine two items in either order and keep the tools

Players drag the rope onto the hook, or the hook onto the rope, and expect the same thing to happen. Here is how to make both directions work, which parts should be used up and which should stay, and what to do when someone combines an item with itself.

Why this works

The player does not know which item the game expects first, and should not have to. A rule between two things is the same rule whichever you pick up first, so it is stored once under a name that ignores order. That also means two copies can never drift apart.

When not to use it

When the order is the puzzle, such as pouring one liquid into another or lighting a fuse before a spark, a rule that ignores order throws away the clue. Store the two directions as separate rules there.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 24 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 "Let players combine two items in either order and keep the tools" (read_entry combine-two-items-in-any-order) 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