Accept a typed quiz answer despite small slips, but not a wrong year

Players type answers with a missing accent, a stray article or one wrong letter, and a strict comparison feels unfair. A loose one lets 1901 pass for 1900. This entry shows how forgiving to be, by how much, and what must still be exact.

Why this works

A slip of a letter in a long name is a typo, but a slip in a short word or a number is a different answer. Letting the allowed error grow with the length, and never for digits, forgives what a person means and nothing else.

When not to use it

Do not forgive slips in a puzzle where the exact word is the challenge, such as a spelling quiz, a password or a code. Also, for a very short list of right answers, compare against the list exactly and skip the fuzziness.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• A diagram of every state
• 41 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 "Accept a typed quiz answer despite small slips, but not a wrong year" (read_entry typed-answer-forgiving-match) 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