The CLI is strongly recommended and maintained. Use jarock-cli-full or jarock-cli-lite for the supported command-line experience. The TUI remains available in future releases, but it is unmaintained, provided as-is, and may not receive fixes for input or compatibility problems.
Every release continues to provide four Windows ZIP families: jarock-cli-full, jarock-cli-lite, jarock-tui-full and jarock-tui-lite. CLI editions use the maintained classic command-line flow. TUI editions include the standalone jarock-tui.exe; both start-server.bat and parameter-manager.bat open the central terminal menu, while DedicatedPower continues to manage the server window. Full editions include the Java installers; Lite editions preserve the existing Lite behavior. scripts/jarock-edition.ini records the installed interface and tier, and verified updates never switch between CLI/TUI or Full/Lite. Use clean-cache.bat to remove inactive updater downloads, rollback backups and temporary wrappers without removing the server runtime; the same action is available from both CLI and TUI menus.
The CLI is strongly recommended and maintained. TUI packages continue to be published for existing users, but the TUI is unmaintained and provided as-is.
- Minecraft Java Fabric Server — installation guide
- Minecraft Java NeoForge fallback
- How does Jarock work?
- First run guide
The English guides are the source of truth for the technical procedure. The current project version is stored only in the scripts/version.txt file.
parameter-manager.batconfigures the loader, RAM, GUI/console mode, a conservative GC profile, online-mode, the ready banner, world import/export (Iimports a world folder or.zipon the next start and asksRemember this world for future starts? (Y/n);Eexports the world to a destination folder after every clean shutdown), the optional interactive startup update check and user-scoped Java environment setup. A remembered source is imported again at every start with confirmation and a backup of the existing world; an incomplete world folder is replaced the same way after confirmation. It edits a temporary copy and includesExit without savingto discard all pending changes.scripts/server-launch-settings.ini.templateis the tracked safe default.scripts/server-launch-settings.iniis local and ignored by Git.java-home.txtis an optional local override for a custom JDK folder and is ignored by Git;JAROCK_JAVA_HOMEis the advanced equivalent.scripts/java-runtime.ps1finds a compatible 64-bit Java 25+ runtime even when Java 8 or Java 21 appears first onPATH; if none is available and the bundled installers are present inprerequisites/,start-server.batruns them automatically (legacy Java 8 first, then the Temurin JDK 25 MSI); otherwise it lists the detected incompatible candidates and gives a Java 25 installation link.scripts/configure-java-environment.ps1updates only the current user'sJAVA_HOMEandPATH, preserving unrelated entries. Startup update modes: AUTO_UPDATE_MODE=install checks for a compatible release and installs the verified package matching scripts/jarock-edition.ini automatically; AUTO_UPDATE_MODE=check checks for updates only and never installs; AUTO_UPDATE_MODE=never does not check for updates and does not install updates. The default is AUTO_UPDATE_MODE=install; choose check or never in parameter-manager.bat to override it.
Each requested locale has a concise translated how-does-jarock-work.md. The English file is the complete explanation; localized files preserve essential technical steps and literals.
Every supported locale has a first-run.md guide. The English guide is the complete version; localized guides preserve all commands, paths, configuration keys and safety messages. Technical names and launcher output literals remain unchanged where users must match them exactly.
Every supported locale has translated visible document titles for the server, network, and NeoForge fallback guides. Technical filenames remain stable so links, release packages and maintenance scripts continue to work.
The English guides remain authoritative for detailed network setup, troubleshooting, backup paths, compatibility checks and security warnings. Localized files preserve technical literals, commands, paths, keys and URLs.
Fabric is the first choice for native optimization and technical mods. NeoForge is the final loader fallback when a required mod is unavailable or unsuitable on Fabric. Forge is currently displayed as unavailable until an official Minecraft 26.2 server build is verified. Forge and NeoForge are distinct loaders; never install a Forge mod on NeoForge unless the mod author explicitly provides compatibility.