config/customadvancements.toml inside your Minecraft instance directory. This file is generated automatically with default values the first time the game launches with the mod installed — you do not need to create it by hand. On Fabric the file is managed through the forgeconfigapiport library, which implements the NeoForge config API so the format is identical on both mod loaders.
All keys live under the section header [Config for Custom Advancements]. Edit the file with any plain-text editor while the server is stopped, then restart to apply changes.
All configuration options
boolean
default:"false"
When
true, every advancement whose path contains recipes/ is removed from the game. This applies to both vanilla and custom recipe advancements. Processed independently of the blacklist.list of strings
default:"[]"
A list of advancement resource location IDs (e.g.
"minecraft:story/root") that the mod should remove. Use the wildcard form "modid:*" to remove every advancement belonging to a specific mod namespace. When blacklistIsWhitelist is false (the default), every listed ID is removed and everything else is kept. See Blacklist & Whitelist for full details.boolean
default:"false"
Inverts the meaning of
advancementsBlacklist. When true, only the advancements in the list are kept; all others are removed. An empty list combined with whitelist mode removes every advancement. See Blacklist & Whitelist.boolean
default:"false"
Enables the progression system. When
true, a player cannot earn an advancement until its parent advancement has been fully completed. See Progression for full details.list of strings
Adds virtual parent links between advancements that belong to separate trees. Each entry uses the format
"parent_id -> child_id". The defaults connect the Nether and End root advancements to the main story line so that players must progress through the overworld before unlocking those tabs. Only active when advancementProgression = true. See Progression.boolean
default:"false"
When
true, all advancement progress for a player is revoked the moment they die, forcing them to start over. See Progression.enum
default:"ALL"
Controls which advancements are subject to the progression system. Accepted values:
ALL— every advancement in every namespace is gated.MODS— applies progression gating to all mods, withmodBlacklistused to exclude specific mods (or, whenmodBlacklistIsWhitelist = true, to exclusively include specific mods).MINECRAFT— only advancements in theminecraft:namespace.CUSTOM_ADVANCEMENTS— only advancements in thecustomadvancements:namespace.
list of strings
default:"[]"
A list of mod IDs to exclude from the progression system. Only relevant when
advancementProgressionMode = MODS. Flip modBlacklistIsWhitelist to treat the list as an allow-list instead. See Progression.boolean
default:"false"
When
true, modBlacklist becomes a whitelist: only advancements from the listed mods are subject to progression gating. See Progression.enum
default:"UNSORTED"
Determines the order of tabs in the advancements screen. Accepted values:
UNSORTED— tabs appear in their natural load order.ALPHABETICALLY— tabs are sorted A–Z by their display title.DEFINED_LIST— tabs are ordered according toadvancementSortingList.
list of strings
default:"[]"
An ordered list of root advancement resource location IDs used when
advancementTabSortingMode = DEFINED_LIST. Tabs not included in the list fall back to their natural position after the listed tabs. See Tab Sorting.boolean
default:"false"
When
true, the mod completely replaces the vanilla/mod advancement loading pipeline. Only advancements placed in the customadvancements folder are loaded; every advancement that would otherwise come from a datapack or mod is ignored.Complete example file
config/customadvancements.toml
Further reading
- Blacklist & Whitelist — filter advancements in or out by ID or mod
- Progression — gate advancements behind their parents and configure death resets
- Tab Sorting — control the order of tabs in the advancements screen