Knowing the player and getting the name recognised should feel like the same task, but spelling conventions can make them seem different. Crossover checks a canonical player identity together with its supported aliases and labels. That allows several legitimate forms to point to one person.
It does not make every nickname, partial name or phonetic guess acceptable. When a form is uncertain, the clearest complete name you know is a better starting point than testing fragments.
Think in identities first
The canonical name is the player identity used by the game. An alias is another recognised way to write that identity; it is not a second answer with a different score.
The current collection explicitly supports many familiar surnames and short forms. For instance, Messi identifies Lionel Messi where he is eligible, while Chicharito is a listed alias for Javier Hernández. These are input examples, not a promise that either player fits the prompt currently on your screen.
Check the club, final and any nationality condition before deciding that a rejected submission must be a spelling problem. Perfectly typed names can still be ineligible.
Accents need not become a keyboard obstacle
The matching process normalises accents, so you do not have to pause to find an accented character for every Latin-script name. The collection also includes specific alternate spellings where needed: Müller has supported forms including Muller and Mueller.
Those conveniences do not imply unlimited fuzzy matching. A genuinely different name or arbitrary typo may still fail. Do not rely on the game to infer a person from a vague resemblance.
The wider guide to accents and aliases in answer input explains the distinction between supported normalisation and guessing what the input system might forgive.
Use the name form you can type reliably
Chinese player labels are included in the collection, and supported aliases may include additional familiar Chinese forms. Latin-script display labels generally preserve the player's proper name across the other supported languages.
Changing the interface language therefore need not mean inventing a new translation of a name. Use a supported form you know, whether that is a canonical name, an explicit surname alias or a listed Chinese label.
The language-switching guide covers the interface behaviour. A language change does not create a new question, reset attempts or turn an ineligible identity into an eligible one.
Avoid ambiguous shortcuts
A surname can be convenient when it is explicitly supported. A first letter, half a surname or “the left-back” is a different kind of input and should not be treated as equivalent.
On a small keyboard, take a moment to inspect the text before submitting. Autocorrect can replace a proper name with an ordinary word, and tapping twice is not a strategy for increasing the chance of acceptance.
If an answer fails, re-read both the submitted text and the prompt. Three incorrect attempts are the round's limit. Spending them on speculative variants can exhaust the round without addressing an underlying eligibility error.
Aliases never bypass duel's shared restriction
Duel tracks the canonical player, not the exact text that was typed. Once a player has been successfully used, entering a surname or another language label does not make that player available again.
The burned-names guide explains the practical effect across both participants. Treat alternate spellings as input assistance, not as extra players you can reserve for later.
Play crossover with the name form you can enter most confidently. After completing the game, use the review to distinguish a missing historical connection from an input issue. A short note about the supported form can solve the latter; it cannot replace learning why the player belongs in the named eleven.
