-
Notifications
You must be signed in to change notification settings - Fork 0
Compatibility
Optional. With Curios installed, a beacon worn in the charm slot works exactly like one carried in your inventory. The binding ships with the mod, so nothing needs configuring.
A worn beacon wins if you somehow carry two. A beacon you deliberately equipped should beat one that merely happens to be in your bag — the other way round made a worn beacon look broken, with nothing on screen to explain why.
The binding is additive, so a modpack can move beacons to a different slot with its own datapack without fighting the shipped one.
Without Curios installed, none of that code is ever touched. It is a genuine soft dependency, not a requirement in disguise.
Trinkets is the Fabric equivalent of Curios. Portable Beacons is a NeoForge mod, so there is nothing to integrate with. If Portable Beacons is ever ported to Fabric, Trinkets is what it would use there.
Portable Beacons ships a JEI plugin, which does two things.
It tells the augments apart. All fifteen share one registered item and differ only by a data component, which JEI cannot guess is meaningful — without the plugin it showed a single entry, so fourteen augments were invisible and their recipes all produced an indistinguishable "Augment".
It adds a fuel category, listing every burnable item with what it is worth as runtime. That
figure appears nowhere else in the game. The list is built from the fuel registry, so a datapack's
own fuels appear in it with no extra work.
No plugin. Recipes are ordinary shaped recipes so they still show up, but augments will collapse into one entry there, exactly as they did in JEI before its plugin existed. EMI is the likelier next one.
Every recipe also unlocks in the vanilla recipe book, which needs no extra mod at all.
Any registered mob effect can be projected — vanilla, another mod's, or datapack-added. Icons come from the vanilla effect atlas, so nothing needs a texture from Portable Beacons.
It is not enabled by default, though: the shipped pool is deliberately limited to the vanilla beacon's own effects, because an unrestricted pool turns a utility mod into a cheat item. Adding another mod's effect is one datapack file.
NeoForge 1.21.1 only, for now. The mod's arithmetic and data model are kept in a layer with no dependency on rendering, packets or data components, so a port to another 1.21.x — or a backport to 1.20.1 — is mostly a matter of rewriting how the beacon's state is stored.
Ports are deliberately not being done before the first release has been in players' hands for a while: every extra branch multiplies the bug reports, and those have not started yet.
The mod is required on both sides. All the arithmetic runs server-side and the beacon screen is a real container menu, so a client cannot grant itself effects its beacon does not allow — every action is re-checked on the server against the beacon's tier, its effect pool, the amplifier cap and the aura mode.
Its four options are a server config, synced to clients on join, so your rules apply rather than each player's local file.
This wiki is the reference for Portable Beacons. Numbers on these pages are taken from the shipped datapack files — if a modpack you are playing has changed them, its own values win.
CurseForge · Source · Issues · MIT
Playing
Running it
Extending it