Skip to main content
Custom Advancements stores all of its settings in a single file located at config/customadvancements-common.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. All keys live under the section header ["Config for Custom Advancements"].
Config changes require a restart. The /ca reload command re-reads advancement JSON files, textures, and language files, but it does not re-read this file. Edit it with the game or server stopped, then start back up.

All Configuration Options

boolean
default:"true"
When true, the mod sends a chat message to the player if a newer version of Custom Advancements is available. Set to false to silence update notifications.
boolean
default:"false"
When true, the mod removes all advancements from the game — vanilla, mod-added, and custom alike. Takes precedence over advancementsBlacklist, so there is no need to populate the blacklist when this is enabled. See Blacklist & Whitelist.
boolean
default:"false"
When true, every recipe-unlock advancement is removed from the game. This suppresses recipe unlock toast notifications without touching any other advancement category. Processed independently of the blacklist. See Blacklist & Whitelist.
list of strings
default:"[]"
A list of advancement resource location IDs (e.g. "minecraft:story/mine_stone") that the mod should remove. When blacklistIsWhitelist is false (the default), every listed ID is removed and everything else is kept. Run /ca generate resource_locations to get a list of all currently loaded IDs. See Blacklist & Whitelist.
boolean
default:"false"
Inverts the meaning of advancementsBlacklist. When true, only the advancements in the list are kept; all others are removed. 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. This is the master switch — every other progression option is inert without it. See Progression.
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, and the player is notified in chat. Applies to every advancement, independently of advancementProgressionMode. 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 — every namespace is gated, including minecraft:, with modBlacklist used to carve out exceptions.
  • MINECRAFT — only advancements in the minecraft: namespace.
  • CUSTOM_ADVANCEMENTS — only advancements in the customadvancements: namespace.
See Progression.
list of strings
default:"[]"
A list of namespaces 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 namespaces 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 to advancementSortingList.
See Tab Sorting.
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 overwrites the vanilla advancement loading pipeline with its own generated advancements instead of loading the standard advancement data. Enable this when you want to supply entirely custom advancement definitions.

Complete Example File

Below is a complete customadvancements-common.toml showing all fourteen options at their default values. Copy it into your config/ directory as a starting point and adjust from there.
config/customadvancements-common.toml

Complete Example: Modpack Configuration

A typical modpack configuration does three things at once: strips the advancements the pack does not want, gates the rest behind the progression system, and fixes the tab order so the pack’s own tab appears first.
config/customadvancements-common.toml
Ship this file in your pack’s overrides/config/ directory so players get your configuration automatically on first launch, alongside the customadvancements/ folder in overrides/.
An invalid TOML file causes the mod to fall back to its defaults, which can look like your changes being silently ignored. If a setting appears to have no effect, check for unclosed quotes, missing commas in lists, and wrong value types before anything else.

Further Reading