Fabric mod manifest
server/mods-manifest.ps1 — pinned Fabric server-side downloads.
Purpose
The manifest gives the bootstrap a controlled list of URLs, filenames, versions, and SHA-512 values. The bootstrap downloads only the matching files and rejects a file whose calculated hash does not match the pinned value.
What belongs on the server
| Group | Examples | Reason |
|---|---|---|
| Required dependencies | Fabric API | Common dependency for many Fabric mods. |
| Cross-play | Geyser-Fabric, Floodgate-Fabric | Java/Bedrock bridge and authentication. |
| Optimization | Lithium, FerriteCore, Krypton, ServerCore | Server-side performance improvements when compatible. |
| Technical play | Fabric Carpet and compatible extensions | Rules, diagnostics, and redstone testing. |
Client-only boundary
Do not add Sodium, Litematica, MiniHUD, or Tweakeroo to the dedicated server automatically. These are normally client-side tools. Each Java player installs compatible client mods separately, and Bedrock players cannot use Java client mods.
Updating the manifest
- Confirm the file explicitly supports Minecraft 26.2 and Fabric.
- Confirm server-side support and all dependencies.
- Download from the official project page.
- Calculate and record the SHA-512 hash.
- Update one mod at a time, start the server, and inspect the log.
- Back up the world before changing the loader or a major mod.
Related references
Optimization guide · Fabric API · Geyser downloads · NeoForge fallback manifest