GFGameName Forge
← Back to name checker

Public, repeatable, and correctable

How GameName Forge checks a name

The score exposes common usability risks. It does not judge taste or prove account availability. This page publishes the current rules, weights, sources, and limits.

Method version 2.0 · July 17, 2026

1. Readability score

Every non-empty candidate starts at 100. Detected patterns apply the deductions below, with a floor of zero. The rules do not interpret meaning, and candidate names are not uploaded to the server.

CheckPenaltyReason
Fewer than 3 characters-20Very short names can be unclear and often need backup variants.
More than 20 characters-15Long names are more likely to be clipped in scoreboards, overlays, or mobile layouts.
Same character repeated 3+ times-15People can miscount the spelling when speaking or typing it.
More than 2 separators-15Reduces portability and spoken readability.
3+ confusable I, l, 1, O, or 0 characters-15These characters can look identical in some fonts.
Year, long number string, or @ marker-25May expose a personal-information pattern and deserves priority review.
Digits exceed 40% of the name-10Usually weakens recall and voice clarity.

These thresholds are product heuristics, not platform bans. A 70-point name may fit a specific squad perfectly; a 100-point name may still have a poor meaning, be claimed, or conflict with a brand.

2. Candidate ranking

The comparison page sorts by readability score first. Ties are broken by the number of platform format checks passed, then by original input order. The first result is the top comparison result, not registration advice or a legal judgment.

3. Platform format checks

Platform checks compare length and character structure only. Rules are reviewed against official help pages, announcements, or account flows. The checker does not bypass login, call private endpoints, or scrape player accounts.

4. Why we do not promise live availability

A name missing from public search is not proof that it can be registered. Platforms may use reserved terms, hidden accounts, moderation rules, regional differences, suffix systems, or temporary limits. Only the signed-in official registration or rename form can authoritatively respond to an exact name.

Treat any third-party service claiming simultaneous live checks across every platform with caution when it does not use an official signed-in flow. Never provide passwords, session tokens, or two-factor codes.

5. Privacy and data handling

The single-name audit and multi-candidate comparison both calculate in the browser. Input is not submitted to the generation API, analytics events, or server logs. Checker events record actions such as copying a report or opening official verification, plus a count or platform, never the name text.

6. Updates and corrections

When platform rules change, we update the checker logic, source date, and affected guides rather than changing only an article title. To report an error, include the platform, official source link, field observed, and date.