SCHEMA BUILDER - ONE WINDOWS DOWNLOAD

Download and open Schema-Builder-Play-1.5.exe. This is the only file you
need to handle; support files are managed under your Windows user folder.
The optional recovery ZIP still supports extracting the whole folder and
opening Play.cmd. Keep those extracted files together when using that fallback.
The graphical launcher shows your detected installation before setup.
Choose Live (account sign-in) or Beta (no account), then click UPDATE & PLAY. Later plays
remember your choice. The server selector can change it at any time.
Prism and matching profiles are detected automatically before setup. Extra
options stay inside the hamburger menu: Browse Prism can recover a custom
portable installation; Browse offline kit selects Beta and reuses that kit
and its world. The main choices always remain Live and Beta (no account).
Progress, update details and any choices appear in the launcher window.
Prism Launcher handles your Microsoft/Minecraft sign-in. A licensed Java
Edition account is required for Live. Beta uses the separate
development client without an account. No administrator password or Java installation
is needed for the automatically installed portable Prism profile.

Each play checks the server release and downloads verified updates first.
If your selected Prism or Minecraft profile is open, the loader lists the
blocking applications and offers to close them. You can keep them running
and finish later; verified downloads stay cached. Closing is requested
normally first. Hidden or unresponsive applications need a second explicit
force-close confirmation; unsaved progress may be lost. Other Java apps
and unrelated installations are left alone. If Windows hides an app's details,
Check apps asks for Windows permission to identify it. The loader then offers
Close apps and, when necessary, a separate Force close confirmation. Another
Windows user's game can have unsaved progress too; save before confirming.
Only app inspection and closing request permission; updates run as your user.
If Windows still cannot verify the app, the update remains blocked and a
private diagnostic report is sent or queued. A completed Live update refreshes
the original Schema Builder mod and reviewed Modern Companions 4.65 mod,
then opens the Live profile and server. Beta updates its offline kit's Schema
Builder mod and reviewed helper files, then opens the offline Beta client.
Existing worlds, account settings,
screenshots and other mods stay in their existing profile.

The loader reuses a compatible live profile automatically. If several match,
choose the child's existing profile by number. Beta profiles stay separate.
If none match, a clean pinned profile is created without an import dialog.
First Minecraft/Java setup may take several minutes. The loader enables
Prism's automatic Java selection/download and disables only the selected
profile's manual Java-location override. Stored Java paths, memory options,
other settings and accounts are retained. Changed config originals are backed
up under %LOCALAPPDATA%\SchemaBuilder\prism-config-backups.

After successful setup use "Schema Builder Play" on the Desktop or Start menu.
Reviewed helper scripts are kept under %LOCALAPPDATA%\SchemaBuilder\loader-1.5.
The single executable is retained under the verified bootstrap-<kit hash>
folder in the same SchemaBuilder directory. You may remove the extracted download
folder after setup. Per-channel profile choices are remembered in
%LOCALAPPDATA%\SchemaBuilder\live.json or offline-beta.json. Former beta.json
settings remain untouched for recovery.
No accounts file is read. Beta asks for an existing compatible kit
folder once, or Enter creates a managed kit. That kit's worlds and runtime
caches are retained for subsequent updates.
Older compatible offline kits receive a verified update of shipped bootstrap
files and Schema Builder mods only. Original files are retained under
%LOCALAPPDATA%\SchemaBuilder\kit-migration-backups; failed migrations restore
them. Worlds, test identity, .tools, build caches and downloaded Java/wrapper
files stay in place.

Older Live profiles: after a successful update the loader offers to archive
recognized Live profiles that no longer match their server. Former signed-in
Beta profiles and beta.json are retained for recovery. Beta now uses the
distinct offline world at port 25567; Live remains at port 25565. No world or
player identity is moved between the former Beta world and offline Beta. Type REMOVE only if you want all listed profiles moved outside
Prism. Enter keeps them. Archives preserve the entire profile under
%LOCALAPPDATA%\SchemaBuilder\archived-instances\<timestamp>.
If Prism is on a different drive, archives stay beside its instances folder in
schema-builder-archived-instances. The loader prints the exact archive location.
To restore, close Prism and move the entire archived profile folder back to
its original Prism instances folder. No profiles are deleted.

Feedback if something goes wrong:
Failed official-family updates automatically send Dad a private diagnostic
report and show the report ID or queued status. Only bounded loader diagnostics
are included. Account files, game logs, worlds and environment settings are
excluded; sensitive paths and authentication values are removed before saving
or sending. If the home server is unreachable, reports stay queued for retry.
Use Report a problem in the hamburger menu to add your own description.
A reporting failure does not turn a failed update into a success.

Advanced (PowerShell):
  .\Play.ps1 -Channel beta
  .\Play.ps1 -ChooseServer
  .\Play.ps1 -Channel live -UpdateOnly
  .\Play.ps1 -InstanceDirectory 'D:\Prism\instances\Child' -PrismExecutable 'D:\Prism\prismlauncher.exe'
  .\Play.ps1 -StateDirectory 'D:\SchemaBuilder'

Play.cmd defaults to Live in the first-run choice and accepts the same options.
The EXE and desktop shortcut open the graphical launcher with no terminal.
For command-line/headless operation use Play.ps1 directly. Graphical mode can
also be opened with powershell.exe -STA -File Play.ps1 -Graphical.
The launcher stays responsive while a background worker performs updates.
During an update, wait for it to finish before closing; selection dialogs can
be cancelled safely. Cancelling a choice prevents its action and game launch.
UpdateOnly updates without launching or offering archives. New roots use
automatic Java selection/download. Existing launcher data roots are selected
from the portable config beside Prism or its UserData folder, otherwise
%APPDATA%\PrismLauncher. Custom InstanceDir is respected.

Ordinary future mod releases need no new profile import. New loader helpers
are downloaded from the same release site, verified against the published
SHA256, safely extracted into a fresh version folder and used automatically.
Helper downgrades are refused. Local saved choices stay outside helper folders.
Only the shipped project helper package can be used for this automatic update.
Game/loader pin changes still require a compatible profile supported by that
reviewed loader version; existing profile data is never overlaid.
Verified official Prism portable bootstrap currently targets x64 Windows.

Bundled files:
  Play.cmd
  Play.ps1
  README.txt
  Loader-UI.ps1
  Process-Guard.ps1
  assets\launcher-hero.png
  Update-Client.ps1
  Install-Companions-4.65.ps1
  offline-helpers\ (four reviewed offline scripts)
