Update Beacon
Running a Minecraft server means keeping mods current. Manually checking every mod page for a new version is tedious, and missing an update can lead to crashes or security issues. Update Beacon solves this by acting as a server-side watchdog. It scans your installed mods, checks them against Modrinth and CurseForge, and then notifies your operators. Even better, it can download and apply those updates for you, all without requiring anything from your players.
Why Server-Side Update Management Matters
Most update tools require every player to install a client mod. Update Beacon flips this model. Because it runs entirely on the server, you only need to drop one jar into your mods/ folder. This saves time and removes the friction of asking your community to update their clients. The mod works with Fabric Loader (plus Fabric API) and NeoForge, supporting the latest stable Minecraft versions for both loaders. This makes it a versatile addition to any modded server setup.
Smart Detection That Eliminates False Positives
Version strings can be misleading. A mod might show 1.4.147 while a newer build is tagged 1.4.147+v240613. Update Beacon avoids these headaches by using hash-based matching. It compares the SHA-512 hash of each installed jar against Modrinth's file records and CurseForge fingerprints. This ensures that only genuine updates are flagged. Nested and bundled sub-mods are automatically skipped, so you won't get alerts for libraries that are packed inside another mod.
Per-Mod Update Channels and Pins
Not every mod follows the same release cycle. Some players prefer stable releases, while others want the latest beta features. Update Beacon lets you set a channel for each mod individually: release, beta, or alpha. You can also pin a mod to its current version, which silences all notifications until you unpin it. This gives you granular control over what gets updated and when.
How Notifications Reach Your Operators
The mod keeps you informed through multiple channels. Every check logs results to the console. In-game chat messages show colored output with clickable download links, sent only to eligible operators. When an op logs in, they see any pending updates immediately. For server owners who want external integration, Update Beacon supports webhooks. You can add multiple endpoints, each with its own URL and format. The built-in discord_embed format creates rich embeds for Discord, while generic_json works with custom dashboards or bots.
Automatic Downloads and Safe Application
Beyond notifications, Update Beacon can handle the entire update process. The /updatebeacon download command fetches all pending updates to a staging area, verifying each file's hash against the source's expected value. You can then apply these staged jars on the next server stop, or use a timed countdown that restarts the server for you. Before any jar is replaced, the original is backed up to .updatebeacon/backup/. This means you can always roll back a problematic update with the /updatebeacon rollback command.
Hands-On Command Control
All commands fall under /updatebeacon and require permission level 2 (op). The most useful ones include:
check- Run a fresh update check and display resultsscan- Verify installed jars against published hashesapply- Apply staged updates or start a restart countdownpin/unpin- Control which mods receive update alertsreload- Hot-reload the config without restarting
This command set gives you full control without needing to edit files manually during a session.
Configuration and Integrity Checks
The first time you start your server with Update Beacon installed, it generates a config file at config/updatebeacon.toml. Here you can enable scheduled checks, set a check interval in minutes, or define a whitelist of mod IDs that are eligible for downloads. The integrity scan feature verifies your installed jars against their published hashes, catching any corrupted or tampered files. For those who want to automate everything, the config supports auto_download and auto_apply options, which handle the entire pipeline after each check.
When you're ready to set it up, the process is straightforward. To download Update Beacon, grab the jar that matches your Minecraft version and loader, then place it in your server's mods/ folder. After starting the server once, the config file appears, and you can customize it to your liking. A free CurseForge API key is optional but enables update checks for that platform; without it, the mod checks Modrinth only. For players who prefer a more streamlined experience, the foxygame.net launcher offers a one-click install for Update Beacon for Minecraft, bundling it with your other server mods and ensuring version compatibility across different loader setups.
How to Install Update Beacon on Your Server
Understanding how to install is simple. First, ensure you have the correct loader installed: Fabric Loader with Fabric API or NeoForge. Next, download the mod jar from its official release page. Place it into your server's mods/ directory. Start the server once to generate the default configuration. Finally, edit updatebeacon.toml to add your CurseForge API key if desired, set your notification preferences, and define any webhook endpoints. That's it. The mod handles the rest, checking for updates on every startup and on any interval you define.
Rollback Safety and Final Thoughts
No update system is perfect, which is why Update Beacon prioritizes safety. Every replaced jar is backed up automatically, and the rollback command restores the previous version in seconds. Combined with the integrity scan, you have a complete toolkit for maintaining a healthy, up-to-date modded server. Whether you run a small private server or a large public community, this mod removes the burden of manual update tracking and lets you focus on playing. Set it up once, configure your channels, and let Update Beacon keep your server running smoothly.