FAQ
Answers to the questions pack authors ask most.
No. Only dimensions listed in dimensionRequirements are affected.
A gate can target minecraft:overworld, but test the behavior carefully. Normal login and respawn mechanics are not the same as ordinary portal travel, and blocking every route into a primary dimension may create an unusable progression state.
Yes. Hidden or display-less advancements can be used as requirements. Display-less advancements appear by resource ID in the locked message.
Yes, when the quest mod or datapack grants an advancement for that quest. Use that advancement ID as the requirement.
No. A requirement counts only when the advancement progress reports complete.
No. At least one configured advancement must be fully complete.
Not directly in 3.1. Use a custom datapack advancement to represent the grouped logic.
Only for team advancement sharing. Normal gating works without it.
No. Newly earned eligible progress is stored for offline party members.
The mod awards all remaining criteria for the shared advancement until it becomes complete.
Yes. Use that advancement in a gate and enable portal-only sharing:
dimensionRequirements = [
"yourmod:next_dimension | ALL | minecraft:end/kill_dragon"
]
[ftbTeams]
shareAdvancementsWithTeam = true
shareOnlyPortalAdvancements = trueNot by default. Recipe advancements are filtered unless enabled or explicitly required by a gate.
No. The gate handler checks server players.
Yes.
Yes, at permission level 2 or higher.
Yes:
showAdvancementDescriptions = falseYes:
enabled = falseYes. Existing 3.0.x entries remain supported.