Tell which game version is newer, so that 1.10 really beats 1.9

A game that offers an update, refuses an old save, or picks the latest patch notes needs to compare version numbers. Comparing them as plain words gets 1.10 wrong, and test versions like beta and rc have their own order. This entry shows the comparison that works.

Why this works

A version number is not a word but several counts side by side, and each count must be compared as a number. Test labels have their own agreed order, with a pre-release below the finished version, so the rule is written once and trusted instead of guessed each time.

When not to use it

Skip it when you number builds by date or by a single counter, since a plain comparison of whole numbers is then right and simpler. And if players never see or compare versions, you may not need any order at all.

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 3 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Tell which game version is newer, so that 1.10 really beats 1.9" (read_entry version-numbers-ten-beats-nine) 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