The NeoForged project has published NeoForge 21.1.242 — another maintenance release for the long-term support branch targeting Minecraft 1.21.1. The 21.1.x line is far from legacy leftovers: as the LTS version, 1.21.1 underpins many of the big modpacks, which is exactly why NeoForged keeps servicing the branch at a steady pace. If your modded server at game-serverhosting runs NeoForge on 1.21.1, 21.1.242 is the current state.
What is new in NeoForge 21.1.242
NeoForged ships builds in quick succession; per-patch changes are documented by the project on neoforged.net and its release channels. 21.1.242 slots into the ongoing LTS maintenance — stability and compatibility work rather than new game content.
The bigger picture across NeoForge branches at release time is worth a look:
| Branch | Status |
|---|---|
| 21.1.x (Minecraft 1.21.1) | LTS, stable — current: 21.1.242 |
| 26.1.2.x (Minecraft 26.1.2) | Stable — freshly served with 26.1.2.80 as well |
| 26.2.0.x (Minecraft 26.2) | Beta — ongoing beta builds, no stable yet |
The message for operators: NeoForge support for Minecraft 26.2 is still beta only. If you want a stable NeoForge server, stay on 1.21.1 (LTS) or 26.1.2.
The tight maintenance cadence on the LTS branch is the genuinely good news for modpack operators: you do not have to chase newer Minecraft versions just because they exist. Your pack's mod authors target 1.21.1, NeoForged delivers the fixes underneath — and your server sits on a version supported from both sides.
Server compatibility
NeoForge is an independent mod loader — NeoForge mods do not run on Forge, Fabric or Paper and vice versa. Within the 21.1.x branch, releases are designed for compatibility: your existing 1.21.1 mods normally keep running unchanged after the patch update. Bedrock crossplay via Geyser (pre-installed at game-serverhosting) is of limited use on modded servers since Bedrock clients cannot render mod content.
How to update your server at game-serverhosting
- Take a backup: before any loader update, save the current state via the Backups tab.
- Open the version switch: in the server panel, set the NeoForge version to the new build.
- Confirm and restart: the server moves to 21.1.242 — worlds, mods and configurations are preserved.
- Check the boot log: after the restart, verify briefly that all mods load cleanly.
FAQ
Should I already move to NeoForge for Minecraft 26.2?
For production servers: no. NeoForge support for 26.2 is still beta only. Wait for a stable release or stay on the 1.21.1 LTS branch.
Will my mods stay compatible after updating to 21.1.242?
Almost always yes — patch releases within 21.1.x are designed for compatibility. The boot log after restarting gives you final certainty.
What does LTS mean at NeoForge?
Long-term support: the branch keeps receiving fixes over an extended period, even as newer Minecraft versions appear. That is why large modpacks favour 1.21.1.
How do NeoForge and Forge differ?
NeoForge split off from Forge in 2023 as an independent project. Both are actively maintained loaders with separate ecosystems — the modpack you want to play decides the loader.
My server runs on 26.1.2 — am I left behind?
No. With 26.1.2.80 that stable branch received a fresh update in parallel. The in-panel version switch gets you onto the newest build of your branch at any time.
How often should I update the loader at all?
There is no fixed rhythm. A proven approach: apply stable patches of your branch promptly (low effort, keeps fixes current), but hold off on branch changes until your modpack officially supports the target version. With a backup and the version switch, either takes just a few minutes at game-serverhosting.