1.2.2

[WillTDA]

A patch release on top of 1.2.1: World Type and the other settings Minecraft only reads on a server's first start, Normal as the default difficulty, and a modpack hardening fix. Versioned 1.2.2 in the last commit, so merging leaves master ready to tag.

New

• World Type — the create page and Settings gain World Type, and their world options now sit under a separator, two to a row: Game Mode and Difficulty, then World Type and World Seed. Minecraft 1.19 renamed the world types and reads none of the old names it doesn't happen to share (checked on real servers: largeBiomes or default on 26.3, and minecraft:flat on 1.18.2, all generate a normal world), so each version gets its own list. A value is stored in the spelling the server's version reads, and a version change in Settings translates it. A value Craftbox doesn't know, like a modpack's own world type, is kept rather than saved over, and creating from a modpack offers "Modpack default" so the pack's stays unless another is picked. The API takes levelType on create, both modpack creates and edit; the server record mirrors it and templates carry it. Checked end to end: a flat world picked in Craftbox really generates flat on 26.3 and 1.18.2.
• First-start settings — level-type, hardcore, generator-settings and (1.19.3+) initial-enabled-packs/initial-disabled-packs are only read when a world is generated, and Minecraft only writes them on the first start (1.17 never writes most of them), so they couldn't be set before the one start that uses them. New servers now get them up front with the defaults each version writes itself, taken from real 1.12.2 through 26.3 servers, and the Properties page lists them.

Changed

• Normal difficulty by default — preselected on the create page and used by the API when a create request leaves it out, in place of Easy. Existing servers are unchanged.

Fixed

• A modpack could put JVM flags on the server's command line. Forge and NeoForge start as java … @libraries/…/unix_args.txt, a JVM argument file, and a pack's files and overrides land after the loader installs, so a pack could overwrite it (or add a higher-numbered folder, which Craftbox picked) with -javaagent or -XX:OnOutOfMemoryError=<command>. Any pack file that would land under libraries/, as a top-level .jar or *_args.txt, or as user_jvm_args.txt, run.sh, run.bat or fabric-server-launcher.properties is now skipped and named in the install warnings, and Forge/NeoForge launch the args file of the build Craftbox installed first. A pack's recommended memory was checked as well: the .mrpack format has no memory setting, so the 4 GB suggestion for modpacks stays.
• The Properties page matches enum values case-insensitively, so 1.12's level-type=DEFAULT shows as Normal.

CI

• The API smoke test now covers the new defaults and first-start settings, World Type on create and edit, the Settings, Properties and create pages' HTML (the first page checks, over the setup wizard's session), and a real .mrpack install that plants launch files. It builds the pack itself with a small zip writer, so still no test dependencies.
• Run locally against this branch's Docker image: 31/31 API checks, and all seven server types started at their newest versions.

Screenshots

The README's Create and Settings images were retaken in Chrome on Windows from the 1.2.2 image, with the same server, selections and framing as before and the new options at their defaults.

Notes

• NeoForge's Maven served a truncated version list for a while today (its metadata was rewritten at 14:47 UTC on 2026-09-28), which left the NeoForge version list empty in every Craftbox version. It had recovered by the time this was pushed; if the NeoForge start job fails on this PR, that's the first thing to rule out.
• Not in scope, noticed along the way: Minecraft 1.12 and older read difficulty and gamemode as numbers, while Craftbox has always written names, so those versions fall back to Easy/Survival.