Advancement Portals
Lock dimensions behind advancements: what the mod does, how to install it, and how a gate decides who gets through.
Overview
Advancement Portals gates player travel to configured dimensions behind Minecraft advancements.
A gate contains:
- A destination dimension.
- A matching mode.
- One or more advancement requirements.
When a player tries to travel to that destination, Advancement Portals checks the player's completed advancements.
- If the gate is complete, travel continues normally.
- If the gate is incomplete, travel is canceled and the player is shown what is still required.
- If no gate exists for the destination, Advancement Portals does nothing.
The mod can use:
- Vanilla advancements.
- Modded advancements.
- Datapack advancements.
- Visible advancements.
- Hidden advancements.
- Dedicated pack-progression advancements.
Advancement Portals does not create the advancements themselves. It reads advancements already loaded by Minecraft, a mod, or a datapack.
Supported environment
- Minecraft
1.20.1 - Forge
47.x - Java
17 - FTB Teams is optional
- Mod ID:
advancement_portals
Requirements and installation
Place the Advancement Portals jar in the mods folder for the Forge instance.
For a normal modpack installation, include it in both the client and server mod lists. The gate logic is server-authoritative, but matching client and server mod lists are the safest supported distribution.
FTB Teams is not required. When it is absent:
- Dimension gates continue to work.
- The FTB Teams config section is safely ignored.
- No team progress is shared.
When using FTB Teams advancement sharing, use a compatible Forge 1.20.1 FTB Teams release.
How dimension gating works
Advancement Portals listens for player dimension-travel attempts.
Only destinations listed in dimensionRequirements are gated. The source dimension does not matter.
For example:
dimensionRequirements = [
"minecraft:the_end | ALL | minecraft:nether/obtain_ancient_debris"
]This means:
- Travel to
minecraft:the_endis gated. - A player must have completed
minecraft:nether/obtain_ancient_debris. - Travel to the Nether, Overworld, or any unlisted modded dimension is unaffected.
- Returning from the End to another unlisted destination is unaffected.
The event applies to server players. Non-player entities are not checked by this gate handler.
The system is based on the destination dimension rather than one specific portal block. Any travel method that fires Forge's normal player dimension-travel event can be evaluated by the gate.
Where to go next
Creating gates
Where the config lives, how to write a gate, and what ALL and ANY mean.
Finding IDs
Looking up the advancement and dimension IDs a gate needs, and checking them before release.
Examples
Ready-made gates for the Nether, the End and modded dimensions, plus team-sharing setups.
Config reference
Every option in the config file, section by section.
FTB Teams sharing
How teammates share advancements, online and offline, and what that means for gates.
Messages and bypasses
What players see at a locked portal, and who gets through anyway.
Troubleshooting
How mistakes in the config are reported, and fixes for gates that block, leak or never unlock.
FAQ
Answers to the questions pack authors ask most.
Technical details
How the mod caches gates, retries portals and stores shared progress, and what it doesn't do.
Pack-author practices
Habits that keep progression gates working through every pack update.
Updating from 3.0.x
The old config syntax that still works, and how to move a pack to 3.1 safely.
