Updating from 3.0.x
The old config syntax that still works, and how to move a pack to 3.1 safely.
Legacy configuration support
The 3.0.x syntax remains accepted:
"minecraft:the_end=[minecraft:end/kill_dragon]"Multiple requirements are also supported:
"minecraft:the_end=[minecraft:story/mine_diamond,minecraft:nether/obtain_ancient_debris]"Legacy entries always behave as ALL.
The brackets are optional to the internal parser, but keeping the original format unchanged is recommended until converting to the new syntax.
Recommended replacement:
"minecraft:the_end | ALL | minecraft:end/kill_dragon"Updating from 3.0.x
Version 3.1 keeps the original dimensionRequirements key and legacy entry syntax.
An existing entry such as:
"minecraft:the_end=[minecraft:end/kill_dragon]"continues to work as an ALL gate.
Recommended update process
- Back up the world and config.
- Replace the old mod jar with version 3.1.0.
- Start the server.
- Allow the expanded config sections to generate.
- Stop the server.
- Review
[dimensionGating]and[ftbTeams]. - Decide whether team advancement sharing should be enabled.
- Convert legacy entries to the new syntax when convenient.
- Restart the server.
- Review validation output.
- Test each destination with a normal player.
- Test both online and offline team sharing.
Existing team progress
Progress earned before installing 3.1 is not automatically present in the new SavedData history.
The mod can discover configured portal advancements from online teammates during login and portal synchronization.
For best upgrade results:
- Have established team members join the server.
- Allow login synchronization to run.
- Attempt the relevant gated portal with another teammate.
- Confirm that the gate advancement is shared.
- Check logs if it is not.