Installing the mod
Getting the jar into a NeoForge 1.21.1 profile, on its own or alongside a pack.
Fragments is one jar. It installs the way any other mod does, and it does not need a server, a port, or anything opened on your router.
What it runs on
- Minecraft
- Java Edition 1.21.1. Not Bedrock, and not the console editions.
- Loader
- NeoForge. There is no Fabric build, and a Fabric profile will not load it.
- Java
- Whatever your launcher already uses for 1.21.1. Fragments adds no requirement of its own.
- Everyone else
- The same build as you. A group running two different builds is the first thing to check when something behaves oddly.
Getting the jar
Take the recommended build from Downloads unless somebody has told you otherwise. Builds are listed newest first, each with the Minecraft versions it was built against and a SHA-256 to check the file against.
Where the jar goes
Into the mods folder of a NeoForge 1.21.1 profile. Where that folder is depends on how you launch the game.
The official launcher
Install NeoForge for 1.21.1 first, which adds a profile you can select. The mods folder sits beside your saves:
- Windows:
%APPDATA%\.minecraft\mods - macOS:
~/Library/Application Support/minecraft/mods - Linux:
~/.minecraft/mods
CurseForge, Prism, MultiMC and the rest
Make or pick an instance on NeoForge 1.21.1, open its mods folder from the launcher’s own menu item, and drop the jar in. Per-instance is the arrangement we would recommend even where your launcher offers the other one, because it keeps a heavy pack and a light one from sharing a mods folder.
Checking that it loaded
Look for a small square button carrying the Fragments mark in the top-right of the Multiplayer screen. Fragments puts nothing on the title screen, so that is the place to check.
- The Fragments button. It opens the account-link screen and nothing else. If it is missing, the mod did not load.
- Add Server is where a world’s link goes. This is the door you will actually use to play.
If the button is not there, the usual causes are a Fabric profile instead of a NeoForge one, a jar in the wrong instance, or a game that was already running when the file was copied in.
Keeping it current
Two places offer a newer build: a small card in the bottom-left of the title screen when one exists, and /vbf update in game.
Neither swaps the jar underneath a running game. The new build is put in place as you quit, so it takes effect next time you start. The card’s own button says Quit and finish when it reaches that point, and pressing it closes the game for you.
- Don’t show again on the card stops it appearing at all.
- Setting
VBF_PHONE_HOME=offstops the check being made in the first place, along with everything else the mod would send on its own. What that covers is set out in what we send.
Removing it
Delete the jar. Worlds you joined stay on your disk as ordinary single-player saves in the Anvil format the game has always used, and you can open them without the mod. Worlds you shared stay registered until you delete them from the dashboard, and other members keep playing.