XYZ388

Standards

How the generator works

What the tools actually do, what they never do, where the material comes from, and who to email when something on this site is wrong.

Maintained by the XYZ388 teamLast reviewed

This is the page the byline on every guide and idea list points at. It is the policy itself, so it changes only when the policy does.

Everything runs on your device

The generator is a script that loads with the page and then stays put. When you press generate, your browser picks words from the sets that ship with the page, joins them, and sometimes adds a number or a small spelling tweak. That is the whole mechanism. There is no request to a server, no queue, and no model behind it.

The practical result: your word, the names you get, and the names you copy never leave the device you are holding. Nothing is stored, because there is nowhere to store it. There is no account, no login, and no history to delete. The fonts and symbols tool works the same way. You can check this yourself with your browser's network tab open, and you should.

The word sets are fixed lists written for this site, not scraped from usernames in use somewhere else. They contain no real people's names, no brand names, and no slurs. If a combination still comes out badly, that is a bug and we want to hear about it.

Where the styled letters come from

The fonts tool does not install a font and does not make an image. It swaps each letter you type for a different character that already exists in Unicode, the standard that assigns a number to every character computers can display. The bold, italic, script, and monospace styles come from the Mathematical Alphanumeric Symbols block. The circled letters come from Enclosed Alphanumerics. The wide letters come from Halfwidth and Fullwidth Forms. Those blocks are published in the Unicode code charts, which is what we check the tool's output against.

This also explains why a styled name is rejected in some places and not others. Three separate things can go wrong, and they fail differently:

  • The field only accepts a short list of characters. Most core account names allow plain letters, digits, and one or two punctuation marks. A character outside that list is refused at the point of typing, no matter how it looks.
  • The platform blocks look-alike characters on purpose. Characters that resemble ordinary letters can be used to impersonate an existing account, so platforms screen for them. Unicode publishes the security guidance behind that screening in UTS #39.
  • The character is accepted but the device cannot draw it. The name saves, then shows as a blank box or a question mark for anyone whose system font lacks that glyph. Nothing is broken. It just looks broken to other people, which is worse.

So we say the same thing on every page that touches this: styled text belongs in display names, bios, clan tags, and chat, and you should paste it into the exact field before you commit to it.

What the platform rules are checked against

Length limits, allowed characters, and how a name change works are read from each platform's own support documentation, not from other websites repeating each other. Those are the sources behind the guides:

Every guide and idea list ends with the subset of these it actually leaned on, so you can see which page a given claim came from rather than taking the whole list on trust.

We link the support section rather than one deep article, because those article URLs get renumbered and quietly break, and a dead citation is worse than none.

Platforms change these rules without announcing them. Every guide carries a published date and an updated date at the top, and when a rule changes the page gets edited and the date moves. What triggers a re-read is a reader telling us a rule has moved, or one of the pages above changing under us, rather than a fixed schedule we would only end up missing. So if the date on a page looks stale to you, treat the detail as worth confirming at the source above before you rely on it, and tell us.

The important one

Generating a name does not reserve it. The generator never contacts Xbox, PlayStation, Steam, Roblox, Minecraft, Discord, or anyone else, so it cannot know whether a name is free and cannot hold it for you. Two people generating at the same moment can get the same result. The only thing that decides availability is typing the exact spelling into the platform where you want it.

Why we will not pretend to check availability

A tool that shows a green tick next to a name would get used a lot more than one that tells you to go and check. We are not building it, because we would have to scrape sign-up forms to do it, the answer would be stale within minutes, and people would trust a badge that is wrong. The availability guide shows the method that actually works instead.

The rest of the list of things this site will not do is short:

  • No accounts, no email capture to unlock a result, no paywall.
  • No storing, selling, or resurfacing the names people generate.
  • No claim of affiliation with any game, studio, or platform. There is none.
  • No copying another site's word lists or guide text.

How this site pays for itself

XYZ388 is free, and the costs are small: a domain, static hosting, and the time it takes to keep the pages current. Those come out of the pockets of the people who run it. Today the site carries no ads, no sponsored placements, and no affiliate links, so nothing on a page is here because someone paid for it to be. If that ever changes, the disclosure goes on this page and on the privacy page before the first paid link goes live, and it will never change what the generator produces. Traffic is measured with privacy-friendly aggregate analytics that count page views, not people.

Who writes this

Everything on the site is published under one byline, the XYZ388 team. That is a team byline for the people who write and maintain XYZ388, not an individual. There are no author photos, no invented biographies, and no credentials claimed here, because we would rather show you the sourcing than assert expertise you cannot verify.

What you can check instead: every claim about a platform's rules points at that platform's own support pages, every claim about styled characters points at the Unicode charts, every page carries an updated date, and the generator's whole mechanism is in the page source you already downloaded.

Report a broken style or a wrong rule

Corrections are the fastest way to make this site better, and they are welcome even when they are blunt. Email [email protected] with:

  • The page, and the exact line or style that is wrong.
  • What you saw, and where. The field, the platform, and the device help a lot.
  • What the platform actually says now, or a link to its support page, if you have it.

Factual errors get fixed on the page itself and the updated date moves. If a correction changes what a page told you to do, we say so in the page rather than editing it quietly. If we cannot reproduce a broken style we will write back and ask, rather than guess. This is a small independent site, so a reply can take a few days, but messages are read.

For anything that is not a correction, the contact page covers what else is useful to send. One thing we genuinely cannot help with is an account, login, or ban problem on a specific platform. Only that platform's support can touch those.