My AI left player2.js and player_new.js next to my real player file

Over a long session an AI sometimes writes a new version of a file next to the old one instead of replacing it, and then edits the wrong one. This helper finds files that are almost the same and shows which one the rest of the game really loads.

Why this works

Copies share most of the names of the things they define, so comparing those names finds them even when the text was reworded. Counting who refers to each copy shows which one is alive, which is the one to keep.

When not to use it

Two files may share names on purpose, such as a level file and its test. Check the pair before deleting anything, and keep a copy until the game runs without the other file.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 2 common mistakes and the fix
• 49 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 "My AI left player2.js and player_new.js next to my real player file" (read_entry work-act-ai-made-copies-of-my-files) 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