
Modrinth · Minecraft mod
Update Beacon
Automatically checks for and updates your servers mods - highly configurable
Quick answer
Which Update Beacon release matches 26.3?
Update Beacon 1.2.0 targets 26.3 with NeoForge. Do not install it on the client. It must be installed on the dedicated server. No extra mods listed for this file.
Where it goes
Is Update Beacon required on the client, server, or both?
Do not install it on the client. It must be installed on the dedicated server.
This file is marked server-only.
What else does Update Beacon 1.2.0 need?
1.2.0 on 26.3. Every mod below is checked against that same setup.
This file does not list any required mods. Do not add a library just because a different file uses it.
This file does not list any required or optional mods.
Before you install it
Add Update Beacon without breaking your instance.
Built for Update Beacon 1.2.0 on 26.3. Pick another file and the loader, install side or required mods may change.
- 01
Stick to this file
Use 1.2.0. It targets 26.3 with NeoForge; another release may have different loader, side or dependency requirements.
- 02
Bring the mods it needs
This file does not list any required mods. Do not add a library just because a different file uses it.
- 03
Put it on the correct side
Do not install it on the client. It must be installed on the dedicated server.
- 04
Pick the file you checked
Use the “Get this file” button beside 1.2.0. It opens that exact file at the source.
About this project
What does Update Beacon add?
UpdateBeacon
A server-side Minecraft mod that automatically checks for updates to your installed mods on Modrinth and CurseForge, then notifies your operators — and can download and apply the updates for you. No client installation required.
Features
Update detection
- Checks every installed mod against both Modrinth and CurseForge (CurseForge is enabled by adding a free API key).
- Hash-based matching — compares the SHA-512 of each installed jar against Modrinth's file records (and CurseForge fingerprints), eliminating false positives from version-string quirks (e.g.
1.4.147vs1.4.147+v240613). - Nested and bundled sub-mods are skipped automatically.
- Per-mod update channels — track
release,beta, oralphaindependently for each mod. - Pins — freeze a mod at its current version to silence update notices until you unpin it.
Notifications
- Console — logs available updates on every check.
- In-game chat — colored output with clickable download links, sent to eligible ops.
- Player login — ops see any pending updates when they join.
- Webhooks — post to any number of endpoints at once (see below).
Downloads & applying
- Download pending updates to a staging area with hash verification against the source's expected hash.
- Apply staged jars on the next server stop, or run a timed apply countdown that restarts the server for you.
- Replaced jars are backed up first, so any update can be rolled back.
Maintenance
- Integrity scan — verify your installed jars against their published hashes.
- Hot reload — re-read the config without restarting.
- Optional scheduled checks on a repeating timer.
Commands
All commands are under /updatebeacon and require permission level 2 (op).
| Command | Description |
|---|---|
/updatebeacon check |
Run a fresh update check and display results |
/updatebeacon list |
Show cached results from the last check |
/updatebeacon info <modid> |
Detailed info, channel, and a direct download link for one mod |
/updatebeacon scan |
Integrity scan — verify installed jars against published hashes |
/updatebeacon download |
Download all pending updates to the staging area |
/updatebeacon staged |
Show what is downloaded and waiting to be applied |
/updatebeacon apply [seconds] |
Apply staged updates now, or start a restart countdown |
/updatebeacon apply cancel |
Cancel a running apply countdown |
/updatebeacon rollback <modid> |
Restore a mod's previous jar from backup |
/updatebeacon pin <modid> |
Pin a mod at its current version (suppress updates) |
/updatebeacon unpin <modid> |
Remove a pin |
/updatebeacon ignore <modid> |
Stop checking a mod entirely |
/updatebeacon unignore <modid> |
Resume checking a mod |
/updatebeacon channel <modid> <release|beta|alpha|any> |
Set a mod's update channel |
/updatebeacon reload |
Hot-reload updatebeacon.toml without restarting |
Webhooks
Add one [[webhooks]] block per target, each with its own URL and format:
[[webhooks]]
url = "https://discord.com/api/webhooks/..."
format = "discord_embed"
[[webhooks]]
url = "https://your-endpoint.com/hook"
format = "generic_json"
Supported formats:
discord_embed— rich embed for Discord webhooksgeneric_json— simple JSON payload for custom integrations
Installation
Drop the mod jar that matches your Minecraft version and loader into your server's mods/ folder, then start the server once to generate the config.
Requirements:
- A supported Minecraft version (see table above)
- Fabric Loader with Fabric API, or NeoForge
- A free CurseForge API key (optional — only needed for CurseForge update checks)
Configuration
Generated at config/updatebeacon.toml on first run:
[general]
enabled = true
check_on_startup = true
check_interval_minutes = 0 # 0 = disabled; any positive value = minutes between checks
[ignore]
mod_ids = [] # mod IDs to skip, e.g. ["mymod", "anothermod"]
quiet_when_no_updates = true # suppress all notifications when everything is up to date
[console]
enabled = true
[chat]
enabled = true
ops_only = true # only notify server operators
permission_level = 2 # minimum permission level to receive notifications
# Add one [[webhooks]] block per target. Supported formats: discord_embed, generic_json
# [[webhooks]]
# url = ""
# format = "discord_embed"
[downloads]
auto_download = false # automatically download updates after each check
auto_apply = false # swap staged jars into mods/ on server stop
backup = true # keep replaced jars in .updatebeacon/backup/
allowed_mod_ids = [] # empty = all mods eligible; non-empty = whitelist
apply_countdown_seconds = 300 # default countdown length for /updatebeacon apply
[curseforge]
# Get a free API key at https://console.curseforge.com/
api_key = "" # leave blank to check Modrinth only
# Per-mod update channel: "release", "beta", or "alpha"
[mod_policy]
# lithium = "beta"
# Pin a mod to prevent update notifications. Use /updatebeacon pin <modid>
[mod_pins]
Staged downloads and backups live under .updatebeacon/staged/ and .updatebeacon/backup/.
Notes
Mods are matched on Modrinth by default; CurseForge checks turn on once you set a curseforge.api_key. Mods that aren't published on either platform are silently skipped.
Project description from Modrinth.
Pick your setup
Update Beacon by Minecraft version and loader
Choose the version and loader you play, then open the matching release.
26.1.2
2 loader builds26.1.1
2 loader builds1.21.11
2 loader builds1.21.10
2 loader builds1.21.9
2 loader builds1.21.8
2 loader builds1.21.7
2 loader builds1.21.6
2 loader builds1.21.5
2 loader builds1.21.1
2 loader builds1.20.1
1 loader buildCheck the dependencies, then try the file in a copied instance before changing a world you care about.
Recent files
Update Beacon versions and loaders
1.2.0
UpdateBeacon-neoforge-26.3-1.2.0.jar
18 Sept 2026
1.2.0
UpdateBeacon-fabric-26.3-1.2.0.jar
18 Sept 2026
Looking for an older file? The official Modrinth project page is in Resources.
