Skip to main content
  • Bundled client profiles span the selected releases 1.20.4–26.3. Independent launches of all eight presets verify selected menu geometry and ASCII/Latin-1 MOTD cases, including bold, italic, underline, strikethrough and version-specific shadows. Other glyphs and arbitrary style combinations, custom fonts and Bedrock are not claimed pixel exact. See profiles.md for the measured scope and references.
  • Supported bundled normal, bold, and italic glyph cases compare exact foreground and shadow masks against the recorded Linux Java references in Linux browsers and Windows Chromium. Windows wrapping checks retain separate foreground-coverage and shadow-anchor thresholds; custom fonts and unsupported glyphs retain browser rendering. An actual Windows Java-client reference remains open in #70.
  • Unsupported Unicode and decomposed combining sequences produce missing-glyph warnings for the bundled font. Browser fallback glyphs and their width estimates can differ from the client. Graphemes remain atomic while editing; this does not certify native shaping. Custom-font and unsupported-glyph italic fallback remains approximate.
  • CRLF retains its CR control and LF boundary. The native CR control glyph is not bundled: its display uses ? with a warning, while source and clipboard retain CR. Empty or multiline protected components require ordinary export rather than materialized layout.
  • Default background/icon/button illustrations approximate the client appearance. Original release panoramas and game textures are not shipped. Host-provided assets allow separate configuration; they do not by themselves establish complete pixel accuracy or redistribution permission.
  • Optional cubemap backgrounds reproduce the audited Java 26.3 camera pose, face order and rotation rate. Cross-origin faces require anonymous CORS permission; unavailable WebGL or GPU loss retains a static fallback. CSS blur/dimming approximate the native shader post-processing; exact shader blur and original panorama artwork are not included. The standalone examples use original CC0 artwork.
  • Bundled java-ltr profiles use the measured Java ASCII-space word-breaking rules; custom profiles that omit font.layout retain legacy grapheme wrapping. Complex shaping and bidi ordering are outside this LTR capability and produce unsupported-text-layout warnings. Extra imported lines and consumed source spaces are retained; only two MOTD lines are visible.
  • New inline MOTD edits are limited to two measured display lines, including soft wrapping, bold/proportional widths and resolved values. Over-limit typing, paste and formatting leave the document and undo history unchanged. Source/import can retain longer documents; the fixed viewport does not scroll into hidden rows, and existing overflow can be shortened or explicitly cleared.
  • Explicit layout export bakes measured visual breaks and alignment spaces into output. A break inside an unresolved placeholder or protected construct returns protected-layout; ordinary export preserves its source instead. Runtime alignment defaults to the 1.21.1 width unless the host supplies RuntimeContext.motdLayout; previews supply their actual profile and width.
  • Inline gradients and rainbows share the preview’s per-glyph color evaluation; see inline-effects.md. Protected unknown components still use their existing approximate visual fallback.
  • Unknown MiniMessage/JSON constructs remain protected. Inside a protected JSON subtree, literal text/extra/arrays can display known colors and boolean decorations without activating metadata or changing raw source. Inner styles remain part of the protected source and are edited in source mode; inherited outer formatting is retained unless overridden inside the atom. If a JSON component array starts with a protected component, the entire dependent array stays one source-editable atom so its inherited metadata and known display styles survive export. Surrounding components remain independently editable. Older saved documents that already lost this array boundary require reimporting the JSON source; it cannot be reconstructed reliably. Context-dependent content remains unresolved; custom fonts and arbitrary components remain approximate. Malformed, oversized or mismatching raw/fallback data and component boundaries that split graphemes retain plain fallback. Cross-format export may require explicit reduction. Ordinary export preserves raw source; explicit layout materialization uses the corrected visible widths and continues to reject protected splits.
  • Chromium, Firefox and Playwright WebKit run the automated editing/preview suite; see browser-verification.md. Real Japanese IME, assistive technology and shipping Safari on macOS/iOS still need manual verification. Synthetic composition events alone are not proof of actual IME support.
  • Count hover can be unreachable when players are hidden or the version is forced incompatible; diagnostics report this. Minecraft controls the final tooltip behavior.
  • No automatic network ping/import or clipboard permission assumptions. The consuming application supplies transport, persistence, permissions and publication.
  • Timed MOTD frames, scrolling, blinking and automatic gradient/rainbow playback are outside the Vanilla viewer’s scope, including an opt-in simulation mode. The measured vanilla 26.3 server list kept its cached MOTD until an explicit refresh in the tested intervals; selecting a frame per status request does not establish continuous client animation. See animation capabilities for the native timing evidence and viewer scope decision.