Finding IDs
Looking up the advancement and dimension IDs a gate needs, and checking them before release.
Resource location format
Minecraft IDs use:
namespace:pathExamples:
minecraft:the_end
minecraft:end/kill_dragon
twilightforest:twilight_forest
mypack:quests/end_accessUse lowercase IDs unless the providing mod or datapack explicitly defines otherwise. Standard resource locations do not allow spaces.
Finding advancement IDs
Useful methods include:
- Inspecting the advancement JSON file in a mod jar or datapack.
- Using the
/advancementcommand with command suggestions. - Reviewing the providing mod's documentation.
- Checking a KubeJS or datapack advancement script.
- Searching the server log or generated data.
- Temporarily enabling command suggestions as an operator.
A visible advancement's translated title is not its ID.
For example:
Title: Free the End
ID: minecraft:end/kill_dragonFinding dimension IDs
Useful methods include:
- Reviewing the dimension mod's documentation.
- Inspecting datapack dimension JSON paths.
- Using commands that provide dimension suggestions.
- Checking the mod's source or registry dump.
- Reviewing teleport or dimension configuration from the providing mod.
A dimension's displayed name is not always its registry ID.
Validate before release
Start a test server and review the Advancement Portals validation summary.
An advancement ID can be syntactically valid but still unknown because:
- The mod providing it is missing.
- A datapack failed to load.
- The ID changed between mod versions.
- The path contains a typo.
- The advancement is generated only under certain conditions.
- The server and client pack contents differ.
