01 / DIRECT ANSWER
Font coverage answers “which characters?” Size answers “can I use the UI?”
Install or confirm v26.3.6, record your current UI setting, test one exact string, change one variable and inspect navigation, tables and dialogs before restarting. The creator publishes the two additions, but not the font name, glyph inventory, setting path, default, range, unit or restart behavior. The live interface—not a guessed screenshot—must supply those missing details.
Release-listed support for Chinese, Japanese and Korean characters.
Replaces legacy Font Scale; accepts a user-entered UI size.
A readable character does not make an English label localized.
Readable only counts when controls remain visible and the setting survives.
02 / FOUR FAILURE LAYERS
Square, small, English and empty are not synonyms
The application cannot render a required character with its available font path.
TEST: exact specimenThe glyph exists; the physical reading size or UI density is uncomfortable.
TEST: one size changeThe glyph renders, but no localized interface string is being supplied.
TEST: product language contractThe field or source value is absent, malformed or not reaching that surface.
TEST: another row & fieldFast classification: if copy-and-pasting the expected text into another application renders it, that proves the operating system has a path—not that Live Editor uses the same renderer or fallback. Unicode explicitly notes applications may have their own font selection logic.
03 / ORIGINAL LOCAL INSTRUMENT
Rehearse the text. Prove it in the live interface.
The lab provides neutral Latin, Simplified Chinese, Traditional Chinese, Japanese, Korean and mixed specimens, plus a custom string. Its pixel slider changes this webpage only; every product claim still requires a human observation in v26.3.6.
Interface Readability Lab
Rehearse a specimen, then record what the installed v26.3.6 interface actually does.
OVR 99 · POT 94 · ID 30999
Mark each line only after checking the installed editor, not this browser preview.
04 / RELEASE CHRONOLOGY
Persistence was repaired before the control was redesigned
Historical release note: saving Font Scale in settings was fixed.
Compatible with today’s game build, but before these named additions.
Extra CJK font and user-entered UI Font Size appear together.
Do not merge the notes: the v26.3.2 fix belongs to legacy Font Scale. It is useful history, not a published guarantee about the storage key, validation or persistence of the redesigned v26.3.6 Font Size control.
05 / VERSION IS NOT FEATURE PARITY
The current game accepts two editor releases; only one lists this feature
FC 26 v1.6.6 build 1.0.139.20381 accepts it, but the new CJK/Font Size notes are absent.
CHECK ACCESS MODEL →1.0.139.20381
The manifest’s current release link is tier-specific. That timing delta is current, not a permanent promise.
OFFICIAL RELEASE ROUTE ↗06 / EVIDENCE ENVELOPE
Two official sentences; eleven unanswered implementation questions
- Extra font supports CJK characters
- Chinese, Japanese and Korean are named
- Font Scale is replaced by Font Size
- User can input a custom UI font size
- Both changes are in v26.3.6
- exact settings click path
- font family and license
- glyph inventory / Unicode ranges
- automatic vs selectable font
- default, minimum, maximum and unit
- validation or clamping
- live apply vs restart
- storage key / settings file
- reset control
- Windows DPI interaction
- supported UI languages
Editorial rule: this guide never invents a recommended number. The local 12–24 px specimen is a browser demonstration, clearly separated from the product’s unpublished accepted values.
07 / SEVEN-CHECKPOINT PROTOCOL
One string. One surface. One changed variable.
- 01PAIRConfirm v26.3.6
Record FC26.exe build and editor version before troubleshooting a release-gated feature.
- 02BASELINECapture the current setting
Screenshot the readable state, display resolution, Windows scale and monitor.
- 03SPECIMENUse the exact failing text
Record the script, field, row and visible characters—including punctuation or symbols.
- 04ISOLATEChange font or size—not both
A one-variable test preserves cause and keeps rollback simple.
- 05SURFACESInspect nav, table and dialog
Look for missing glyphs, truncation, overlap, lost actions and unreadable numeric columns.
- 06RESTARTClose and relaunch completely
Repeat the same specimen and surface; immediate success alone does not prove persistence.
- 07DECIDEKeep or restore
Keep only when glyph, layout and navigation remain usable; otherwise restore the captured value.
08 / SIZE IS A LAYOUT TEST
The largest readable text is not automatically the most usable UI
Stroke detail and character distinction are comfortable at the viewing distance.
Long Latin and CJK labels fit without covering neighbors or action targets.
Dense numeric columns preserve alignment and row-to-row scanning.
Buttons, tabs and the F9 route remain reachable after the change.
Accessibility model, not certification: W3C’s resize-text guidance treats enlargement as successful only when content and functionality remain available. We borrow that test logic for the editor; we do not claim Live Editor meets WCAG.
09 / WINDOWS DISPLAY BOUNDARY
Font Size and Windows scaling can produce similar symptoms through different owners
A product control introduced in v26.3.6. Test its result inside the overlay.
OWNER: APP SETTINGOS-level desktop scaling can affect size, sharpness and clipping in general.
OWNER: DISPLAY ENVIRONMENTRecord resolution, percentage and monitor; change only one owner per attempt.
PROOF: CONTROLLED A/BMulti-monitor trap: Microsoft documents that desktop apps may behave differently across DPI-awareness modes and monitors. This is general Windows context; the repository does not publish Live Editor’s DPI-awareness mode.
10 / SYMPTOM ROUTER
Route what you see before changing anything
Font coverage: Test the exact code points with the v26.3.6 CJK path.
Font Size: Increase one step; inspect tables and dialogs before restart.
Layout density: Restore baseline or choose the last size with full access.
Localization: No public promise says the editor UI is translated.
Data / issue #35: Use the blank-name diagnostic; do not call it a glyph fix.
Encoding or source data: Compare another row, field and clean instance before diagnosis.
Game localization: The Live Editor UI font is outside that owner.
Settings persistence: Record pair, value and restart steps; avoid reinstallation guesswork.
11 / ISSUE #35 BOUNDARY
A blank Name column is not evidence of a missing CJK glyph
Reported shape: empty Name column in the Players list.
Missing proof: no maintainer diagnosis ties it to font selection; release notes through v26.3.6 do not name a fix.
Correct route: reproduce the exact surface and version pair, then use the dedicated diagnostic page.
12 / SAME RELEASE, DIFFERENT CONTRACT
Settings neighbors are not one feature
+ FONT SIZE
Glyph coverage and UI legibility. This page owns the test protocol.
YOU ARE HEREHOTKEY
v26.3.6 adds hotkey settings for an already-existing speed control.
OPEN SPEEDHACK GUIDE →HOTKEY
v26.3.6 can assign a supported Lua script to a hotkey.
OPEN LUA HOTKEY GUIDE →13 / PERSISTENCE RECEIPT
Do not let a readable preview strand you after restart
Screenshot or transcribe the prior usable setting.
Navigation, dense table and dialog remain complete.
Same characters, surface, monitor and display scale.
Return to the recorded setting before stacking another change.
Escalation packet: attach release pair, Windows version, resolution/scale, monitor, exact text, affected surface, before/after screenshots, chosen visible control values and whether a full relaunch resets them.
14 / VIDEO EVIDENCE AUDIT
The current exact walkthrough does not exist in the audited results
Legacy visual: a caption-backed FC 26 tutorial opens the F9 overlay at 10:40 and changes legacy Scale to 1.5 at 10:56–11:04 to make it easier to see. That is historical behavior, not a new Font Size range.
Current-result inspection: v26.3.5 and overlay-fix videos were checked for audience language and UI context; neither documents the v26.3.6 CJK/font contract.
Search result: queries for CJK font, font size, font scale, Chinese/Japanese/Korean, UI settings and v26.3.6 returned broad mod tutorials, irrelevant results and unavailable videos—not an exact controlled test.
Editorial consequence: no numeric recommendation, menu path or “works for all CJK” promise is borrowed from video.
15 / FAQ
Questions users ask when “the font is broken”
01What changed in FC 26 Live Editor v26.3.6?+
The official changelog adds an extra font supporting Chinese, Japanese and Korean characters and replaces Font Scale with Font Size, allowing a custom UI font size.
02Does v26.3.5 have the new CJK font and Font Size control?+
The current manifest accepts v26.3.5 with FC 26 v1.6.6, but the changelog introduces these specific UI additions only in v26.3.6. Compatibility is not feature parity.
03Where is the CJK font setting?+
The public repository confirms the feature but does not publish an exact click path, control label or screenshot. Open the installed v26.3.6 settings and follow the controls actually visible there; do not copy a guessed path.
04What Font Size value should I use?+
No official default, range, unit or recommended value is published. Record your current value, change one step at a time and test navigation, dense tables, dialogs and a full restart.
05Does CJK support mean Live Editor is translated?+
No. A font can provide glyphs without translating interface strings. Glyph coverage, UI language and localized copy are separate layers.
06Does the CJK font fix blank player names?+
Not automatically. Issue #35 reports an empty Name column, which is a data/list symptom rather than proof of a missing glyph. No release note through v26.3.6 names that issue as fixed.
07What is a missing glyph or tofu box?+
It is a visible placeholder used when the rendering system cannot find a glyph for a character. A blank field, question marks from bad data and an English label are different symptoms.
08Does the feature change Chinese, Japanese or Korean text inside FC 26?+
The release note describes a Live Editor font/UI setting. It does not promise changes to base-game localization, database records, commentary or in-game menus.
09Do I need to restart after changing Font Size?+
The public sources do not define live-apply or restart behavior for the new control. Test both the immediate result and a complete editor relaunch, then record what survives.
10Can Windows display scaling affect the result?+
Windows DPI scaling can change desktop-app size, sharpness and clipping in general. Record display resolution, Windows scale and monitor before comparing results, but do not assume a Windows setting is the cause without a controlled test.
11Why can larger text become less usable?+
Larger text may be easier to read yet cause labels, rows or actions to clip or overlap. Readability requires both legible glyphs and a usable layout.
12Is the font included for every Unicode character?+
No official glyph inventory or coverage table is published. CJK support is not a promise that every ideograph, symbol, variation sequence or emoji renders. Test the exact text you need.
13Are v26.3.6 hotkey settings part of this guide?+
They shipped in the same release, but their behavior belongs to the separate Speedhack and Lua Events & Hotkeys guides. Shared release timing does not make them font controls.
14How do I roll back a bad size change?+
Record the prior readable value before testing. If layout becomes unusable, restore that value using the still-accessible settings surface; keep a screenshot or receipt so rollback does not depend on memory.
16 / SOURCE LEDGER
Primary product evidence first; standards context kept in its lane
Primary wording for the v26.3.6 CJK font and custom Font Size additions, plus the v26.3.2 legacy Font Scale save fix.
Dated source change that introduced the two UI release notes; it does not expose implementation or setting ranges.
Historical provenance for “Saving font scale in settings”; not proof of the new Font Size persistence contract.
Maps FC 26 v1.6.6 build 1.0.139.20381 to Live Editor v26.3.5–v26.3.6 and publishes tier-specific links.
Current Silver release route surfaced by the official manifest.
Creator-owned Windows/offline product scope; no current UI source or font inventory is published.
F9 overlay and launcher baseline. It contains no exact v26.3.6 CJK/Font Size walkthrough.
Current boundary evidence for an empty Name column; no maintainer diagnosis establishing a font cause.
Standards-body explanation of missing-glyph placeholders and characters that render differently.
Explains that applications may use their own font-selection and fallback logic independent of the operating system.
First-party Windows explanation of glyph fallback across GDI, Uniscribe and DirectWrite.
First-party UI-font examples for Simplified/Traditional Chinese, Japanese and Korean; context only, not identification of the Live Editor font.
First-party explanation of DPI-aware, system-scaled and per-monitor desktop UI behavior.
Primary web standard for ordered font-family matching and missing-glyph behavior in this page’s browser preview.
Accessibility test model: enlarging text must preserve content and functionality; used as a layout-testing principle, not a product-conformance claim.
Caption-backed visual at 10:40–11:04 shows F9 options and legacy Scale 1.5 for legibility; historical UI only.
Caption-audited troubleshooting video; useful for audience vocabulary but does not document current CJK or Font Size.
Current earlier-release walkthrough inspected during the audit; it cannot prove a feature first listed in v26.3.6.
Method: creator sources control product facts; Unicode, Microsoft and W3C explain general rendering, DPI and readability principles; videos expose real audience language and visual history only. Checked 18 August 2026.