MC³ correctness test profile

Release boundary:
  This corrected setup text is prepared for MC³ 0.3.11. The immutable 0.3.6
  profile retains older embedded guidance and must not be rewritten.

Updating:
  The download is always published as mc3-test.mrpack. Its internal version
  identifies the release, but the stable URL does not change.

  To update the same Modrinth App instance, first back it up, then open:
  Settings -> Installation -> Change version
  and select the newly downloaded mc3-test.mrpack. Current Modrinth App reuses
  that instance/profile, including its per-instance Java memory setting, while
  replacing the pack-managed content. Import is only for a separate clean
  instance. Automatic one-click discovery still requires a pack published as
  a Modrinth project.

Logo:
  Modrinth App recognises overrides/icon.png during direct .mrpack import and
  assigns it to the new instance automatically. mc3-logo.png is also included
  at the instance root as a reusable copy for manual selection or export.

Memory:
  Set this instance's maximum memory to 12288 MiB (12 GiB) in the launcher.
  8 GiB is workable for settled play; 6 GiB is tight during roam transients.

The Modrinth .mrpack v1 format contains game files and dependencies only; it
does not have a JVM-memory field. Modrinth App therefore cannot import this
setting from the pack itself.

Profiling:
  In a world, run /mc3 profile start 60 and reproduce a slow vertical drop.
  MC³ writes the JFR recording and JSON summaries into the instance's debug/
  directory even if the render thread freezes.

Rendering:
  Sodium and Iris are installed, with shaders disabled.

  Near terrain streams as a full square prism: Minecraft's render distance
  controls the Chebyshev X/Z square and verticalViewDistance controls Y.

Generation:
  generationMode=per_cube is the shipped path. Each 16 x 16 x 16 cube receives
  structures, decoration and light before first delivery. unified and
  deferred_band are comparative modes.

  Voxy is installed because it is a mandatory correctness target. MC³ pushes
  delivered sections into Voxy and feeds resident cubes in a configurable far
  prism (voxyViewDistance, default 64 cubes) with the same first-delivery
  gates as the near view; block edits invalidate far sends on the next sweep.
  The far feed still never starts generation — coverage beyond the near view
  grows with exploration and /mc3 pregen.

  MC³'s far-feed distance is separate from Voxy's own render ring. Pinned Voxy
  represents only section Y -128..127 in its LOD identity; terrain outside
  that span remains available through Sodium's near view but has no Voxy far
  LOD. On cubic levels MC³ 0.3.11 caps Voxy's top-level render-ring radius to 63
  (199,248 nodes across 16 Y rows) because radius 64 needs 205,648 nodes and
  exceeds Voxy's fixed 200,000-node capacity. Non-cubic Voxy is unchanged.

Compatibility:
  C2ME is not installed in this profile. If added manually, MC³ 0.3.11's enabled
  aquifer path accepts exactly c2me-opts-worldgen-vanilla
  0.4.2-alpha.0.43+26.2. Absent or disabled C2ME uses MC³'s vanilla route;
  another or unreadable enabled implementation fails closed. The
  absent/disabled/exact-enabled runtime matrix remains a release gate.
  Published 0.3.6 instead requires C2ME's aquifer optimisation to be disabled.

  E-LITE is deliberately excluded.
