Installing HungerBridge takes only a few minutes. The process differs slightly between Fabric and Paper, but in both cases it boils down to dropping a single JAR file into the right directory and starting your server. This page walks you through every step for both platforms.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/iFamishedX/HungerBridge/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
Make sure your environment meets these requirements before downloading HungerBridge.Java 21
HungerBridge is compiled for Java 21. The GitHub Actions release pipeline uses the Temurin distribution. Both Fabric and Paper require Java 21 for Minecraft 1.21.x anyway, so no extra setup is needed in most cases.
Minecraft 1.21.11
The current release targets Minecraft 1.21.11. Fabric requires loader ≥ 0.18.4 and Minecraft ≥ 1.21.10. Paper requires API 1.21 or newer.
HungerBridge is a server-side only mod/plugin. It does not need to be installed on clients. On Fabric, the
fabric.mod.json declares "environment": "server".Download
All releases are published on the HungerBridge GitHub Releases page. Each release provides two JARs — one per platform — following this naming convention:Installation
- Fabric
- Paper / Purpur
Verify Fabric Loader version
HungerBridge requires Fabric Loader ≥ 0.18.4. Check your loader version in the Fabric installer or in your server’s startup log. Upgrade the loader if necessary before continuing.
Download the Fabric JAR
From the Releases page, download the file named:
Place the JAR in mods/
Copy the downloaded JAR into your server’s Your
mods/ directory:mods/ directory should now contain the HungerBridge JAR alongside any other server-side mods.Start the server
Start (or restart) your Fabric server normally. On the very first run, HungerBridge will detect that no configuration file exists and generate one automatically.You will see a log line similar to:
Locate the generated config
The auto-generated configuration file is written to:This file contains your randomly generated auth key. See the Configuration page for a full reference of every available option.
First-Run Behavior
When HungerBridge starts and cannot find aconfig.yaml, it:
- Creates the containing directory (
config/HungerBridge/orplugins/HungerBridge/) if it does not exist. - Generates a fresh
config.yamlwithport: 30007and a randomly generated UUID as theauth.key. - Enables all v2 endpoints and leaves v1 and legacy endpoints disabled.
- Starts the HTTP server on the configured port.
Verifying the Installation
After the server starts, you can confirm HungerBridge is running by sending a quick ping to the health-check endpoint. ReplaceYOUR_AUTH_KEY with the value of auth.key from config.yaml:
401 Unauthorized, double-check that the X-Auth-Key header matches the key in your config file exactly.
Next Steps
Configuration →
Customize the HTTP port, rotate the auth key, and toggle individual API endpoints.