Paste a transformed nick back into the generator, apply a second style, and nothing happens. Paste the same nick into a game chat and you may see rows of empty boxes. Both failures trace to specific lines in the transformation code, so we read all 16 style maps in the nickname generator and worked out the exact combination space you can reach.
What the nickname generator maps, character by character
Every mapped style runs the same pipeline. The code spreads your input into single characters, applies one function per character, and joins the result back into a string.
function transformText(text, font) {
if (font.isWrap) {
return font.map(text);
}
return [...text].map(c => font.map(c)).join('');
}
Each function matches three ASCII ranges. Uppercase letters sit at codes 65 to 90, lowercase letters at 97 to 122, digits at 48 to 57. The bold card sends uppercase to the block at 0x1D400, lowercase to 0x1D41A, and digits to 0x1D7CE. Everything outside those ranges passes through untouched, so spaces, punctuation, and letters like s with cedilla or g with breve survive every map unchanged.
Coverage differs per card, and the differences are visible in the source. The italic map handles letters with one special case for lowercase h at U+210E and skips digits entirely. The card named Serif maps uppercase A to Z only, through a guard that can never fire, because the largest possible result is 0x1D584 for Z while the guard limit is 0x1D586. Lowercase and digits fall through unchanged. The superscript card maps Q to itself, and six letters share one glyph between uppercase and lowercase input.
The combination space and its one chaining rule
The maps share one hard limit. A second map receives the fancy output of the first, none of which is ASCII anymore, so every character passes through unchanged. Stacking the bold map onto the bubble map returns the bold text with no bubbles.
Wraps behave differently. The four wrap cards, the corner bracket pair, the star pair, the diamond pair, and the ornament frame, concatenate decoration around any content. They never inspect characters, so they stack freely with each other.
The chaining rule follows directly from the code. Apply at most one of the 12 character maps to a given string, then apply wraps in any order around the result. Counting the distinct outputs for one input, you get 12 bare maps, 4 bare wraps, and 48 combinations of one map with one wrap, which is 64 reachable strings before you start nesting wraps, and exactly zero valid map plus map chains. The 40 character input cap bounds each of them.
Three holes in the Unicode blocks
The double-struck card carries an explicit lookup table for a reason. Seven capital letters do not live in the Mathematical Alphanumeric Symbols block. The table routes C, H, N, P, Q, R, and Z to U+2102, U+210D, U+2115, U+2119, U+211A, U+211D, and U+2124 respectively. You can verify each value against the table in the source file.
The italic special case exists for the same reason. Lowercase italic h sits outside the italic block, so the code maps it to U+210E directly instead of computing an offset.
The Gothic card does not get the same treatment. Fraktur capitals start at 0x1D504, but five positions inside that range are reserved, because the glyphs for C, H, I, R, and Z live at U+212D, U+210C, U+2111, U+211C, and U+2128. The Gothic map uses the naive offset 0x1D504 plus code minus 65 with no hole table. Type an uppercase C, H, I, R, or Z and the function returns an unassigned code point, which most fonts render as an empty box. This is the clearest defect in the style set, and it explains the boxes you sometimes see in game chats.
Input limits and copy behavior
Three more constraints come from the interface code. The input field caps at 40 characters through maxLength, and longer pastes truncate silently. An empty field renders the default text WebRecast on every card, so the grid never shows blank results. Clicking a card copies its string through the clipboard API with no fallback and no error handling, then shows a confirmation mark for 1200 ms.
If the browser refuses the clipboard write, which happens on unfocused windows and insecure pages, the confirmation mark still appears and nothing reaches your clipboard. The failure is silent by construction. Verify the paste target after copying, and if the first paste produces nothing, click the card again with the window focused.
Honest limits of fancy text
Screen readers interpret these strings unpredictably, because code points outside the Latin alphabet carry no pronunciation rules. Some game filters and username validators reject the transformed output outright, and no style choice can bypass a validator that only accepts ASCII. Search engines treat the fancy forms as different characters, so a decorated name will not match searches for the plain spelling. Treat these styles as display decoration, never as your identity or login.
Checklist before you paste your new nick
- [ ] Keep the plain spelling somewhere safe for login and search.
- [ ] Apply one character map, then wraps, never two maps in a row.
- [ ] Avoid uppercase C, H, I, R, and Z inside the Gothic style.
- [ ] Test the final string in the target game or app before adopting it.
- [ ] Confirm the paste actually landed after the copy mark fades.
- [ ] Keep the decorated nick under the 40 character cap including decoration.
The whole map set is short enough to audit yourself. Load your name into the [nickname generator](/en/nick-generator), try the chaining rule, and tell us which platform rejected which style. If you find another letter that renders as a box, name the style and the letter, and we will add it to the hole list.
