Schema Builder private offline beta test - Windows x64

1. Extract the WHOLE ZIP to a writable folder, such as Desktop\SchemaTest.
   Do not launch inside the ZIP. Keep this separate from normal Minecraft.
   Already have the original offline beta.1 kit? Close the game and other Java
   applications, then extract this new Update-Play ZIP into that SAME folder,
   replacing its shipped setup files when prompted. The ZIP has no .tools,
   cached Gradle wrapper JAR, build cache, run settings, logs, saves or account
   files, so those existing local files remain available. Keep your existing
   run folder; do not delete it. Use the new Update & Play-Beta.cmd afterward.
2. Double-click Update & Play-Beta.cmd. Windows may show its normal downloaded-script
   prompt. Use only the package supplied by the owner.
3. Enter a unique test name for this PC once: DadTest, Kid1Test, Kid2Test.
   Use 1-16 letters, numbers or underscores. Each simultaneous player needs a
   different name. The name is remembered locally across package updates.
4. Let initial setup finish. It downloads a private Java 21 if needed, then
   official Gradle/NeoForge/Minecraft development dependencies. Initial setup
   may take up to an hour and needs internet, disk space and a Windows x64 PC.
5. On the first game launch, choose accessibility settings and click Done.
   The development game then attempts to join 192.168.2.149:25567. If needed, choose
   Multiplayer > Direct Connection and enter that address. The PC must be on
   the home LAN. Production and the authenticated beta use different ports.

No Microsoft sign-in or account profile is used by this supported NeoForge
development launch. It is a private mod-testing environment. The ZIP contains
our original beta mod, small build/configuration/launch files and notices;
Minecraft, NeoForge, Java, Gradle binaries, caches, accounts and worlds are
downloaded/generated locally rather than included in the ZIP. Nothing changes
your regular launcher or Microsoft accounts. Treat each test name consistently:
the offline server associates saved progress with that name. Avoid real account
names; this test server has separate progress from the normal servers.

This package starts with Schema Builder 0.4.0-beta.1, Minecraft 1.21.1 and
NeoForge 21.1.256. client-manifest.json records the exact original mod JAR SHA256
and embedded source fingerprint matching the owner's server snapshot. The game
loads the verified installed JAR from run\mods. Launches do not compile the newer repository
source. Only the original custom mod is included; no original beta source
snapshot is claimed. Source fingerprint is an input digest, not a Git commit.

Updating: close the game and other Java applications, then use
Update & Play-Beta.cmd in this same folder. It checks
https://minecraft.dokinetix.com/updates/offline-beta.json before starting.
An unchanged mod is not downloaded or copied again. Changed mods are staged,
SHA256 checked, backed up under offline-beta-backups, then installed into mod
and run\mods. A failed update refuses to start the game; installation errors
restore the previous files. The launcher/bootstrap files keep their original
integrity checks; offline-update-state.json separately records the installed mod.
Your private runtime/cache, test name, options and local worlds are reused.
Only the offline-beta channel on server port 25567 is accepted. Java/game/loader
pin changes require a new kit. Play-Test.cmd still starts the verified installed
snapshot without checking for a new release; prefer Update & Play-Beta.cmd.
Owners can use -ManifestUrl http://192.168.2.149:8088/updates/offline-beta.json
for the LAN manifest, or -UpdateOnly to check/update without starting the game.

Troubleshooting:
- Use a fresh extracted folder if a file-hash or extra-mod check fails.
- Keep mod and run\mods free of extra files, mod JARs and symbolic links.
- First download needs internet; later launches reuse local upstream caches.
- A connection error can mean the server is stopped or this PC is off the LAN.
- Logs: run\logs\latest.log. Keep logs private if sharing a failure with Dad.
- To change a test name: delete %LOCALAPPDATA%\SchemaBuilderOfflineBeta\test-name.txt
  and run again. A new name gets a different offline player/save identity.
- Need manual Java: install Windows x64 JDK 21 from
  https://learn.microsoft.com/java/openjdk/download and set JAVA_HOME.
- Advanced terminal checks: powershell -NoProfile -ExecutionPolicy Bypass
  -File .\Play-Test.ps1 -PrepareOnly -TestName ClientSmoke -JavaHome C:\path\to\jdk21
  Add -NoJoin to show the game menu instead of attempting the test server.

Runtime validation and the limits of testing are recorded with the download
page's evidence. A working launch or LAN join does not establish two-PC human
playability, graphics/controls, or every gameplay mechanic.

Authoritative references:
https://docs.neoforged.net/docs/1.21.1/gettingstarted/
https://github.com/neoforged/ModDevGradle
https://services.gradle.org/distributions/gradle-9.2.1-wrapper.jar.sha256
https://adoptium.net/temurin/releases/?version=21

NOT AN OFFICIAL MINECRAFT PRODUCT. NOT APPROVED BY OR ASSOCIATED WITH MOJANG
OR MICROSOFT. Original Schema Builder content is All Rights Reserved; the MDK
template retains its bundled MIT notice. Gradle wrapper scripts are Apache-2.0
(full license in GRADLE-LICENSE.txt). Downloaded upstream dependencies retain
their own licenses. No upstream authors endorse this test package.
