Technical details
How the mod caches gates, retries portals and stores shared progress, and what it doesn't do.
Gate cache
Parsed gates are cached. The cache is rebuilt when the raw dimensionRequirements list changes.
One gate per destination
The internal gate map uses the destination ID as its key. The last valid duplicate entry wins.
Unknown advancement behavior
Unknown advancement IDs are kept in a gate's requirement list and evaluated as missing. This is a fail-closed design.
Advancement completion
The mod uses Minecraft's completed advancement progress. It does not treat individual completed criteria as a completed gate unless the advancement itself is done.
Unlock notifications
Unlock notifications listen for the server-side advancement-earned event.
For ALL, the event that completes the final required advancement triggers the message.
For ANY, the message is suppressed when another qualifying advancement already completed the gate earlier.
Warning memory
The mod tracks the last warning tick for connected player UUIDs. The entry is removed when the player logs out.
Portal retry delay
Blocked travel applies the configured portal cooldown to reduce rapid repeated dimension-travel events. It does not grant Fire Resistance or other effects.
Optional FTB Teams integration
The integration uses reflection so FTB Teams is not a hard code dependency.
If the expected API cannot be resolved, an error is logged once and team sharing is skipped while normal gating remains active.
Persistent sharing data
Stored advancement knowledge is saved per player UUID in the Overworld data storage.
It is not permanently keyed to an FTB team ID in version 3.1.
No administrative commands
Version 3.1 does not currently include commands such as:
/advancementportals reload
/advancementportals validate
/advancementportals checkRestarting the server remains the recommended way to ensure validation runs after configuration changes.
No per-gate custom text
Version 3.1 automatically formats dimension names and uses advancement display data. Per-gate custom names, icons, locked messages, and unlock messages are not yet configurable.