Skip to main content
By default, Minecraft displays advancement tabs in the order they happen to be loaded, which can vary between game versions, mod updates, and modpack changes. Custom Advancements lets you take full control over that order — sorting tabs alphabetically with a single config line, or defining an exact sequence using a hand-crafted list. Both tab-sorting options live in config/customadvancements-common.toml and are applied client-side every time the advancements screen opens.
Sorting also applies inside the BetterAdvancements screen. Custom Advancements detects that mod automatically and reorders its tabs the same way — no extra configuration is needed.

advancementTabSortingMode

enum
default:"UNSORTED"
Controls how the tabs in the advancements screen are ordered. Accepted values:
  • UNSORTED (default) — Tabs appear in their natural load order. No reordering is applied; this is identical to unmodded behavior.
  • ALPHABETICALLY — Tabs are sorted A–Z by their display title, the text shown on the tab. Sorting uses the title as rendered in the current game language and is case-sensitive, so uppercase letters sort before lowercase ones.
  • DEFINED_LIST — Tabs are ordered according to the root advancement IDs listed in advancementSortingList.

advancementSortingList

list of strings
default:"[]"
An ordered list of root advancement resource location IDs, used exclusively when advancementTabSortingMode = DEFINED_LIST. Each entry identifies the root advancement of a tab — the advancement with no parent that anchors the tree. Tabs are displayed in the same order as their root IDs appear in this list.If the list covers every loaded tab, the tab order is replaced exactly. If only some tabs are listed, those tabs are moved to their respective index positions and the unlisted tabs keep their natural relative order around them.
Entries must be root advancement IDs — an advancement with no parent field. A child advancement’s ID or a tab’s display name will not work, and entries that do not correspond to a loaded root advancement are rejected, causing the option to fall back to its default.
Not sure which advancements are roots? Run /ca generate resource_locations to export every loaded advancement ID to customadvancements/resource_locations.txt, then look for the advancements whose JSON has no "parent" field. See Commands.
For reference, the vanilla root advancement IDs are:

Examples

No sorting is applied. Tabs appear exactly as Minecraft loads them. This is the default behavior and requires no extra configuration.
config/customadvancements-common.toml
Use this mode when you do not need to control tab ordering, or when another mod handles the tab layout for you.

Mixing vanilla and mod tabs

You do not have to list every tab. Listing just the few you care about is enough to pin them to the front:
config/customadvancements-common.toml
Here examplemod:main/root is placed second, directly after the vanilla story tab. Every other tab — including minecraft:adventure/root and minecraft:husbandry/root — keeps its natural position around the four listed tabs.
[INSERT IMAGE: Side-by-side comparison of the advancement tab bar under UNSORTED versus DEFINED_LIST ordering]

Applying Your Changes

Tab sorting is read from the config file at startup and applied client-side when the advancements screen opens.
/ca reload does not re-read config/customadvancements-common.toml. After editing either option on this page, restart the game or server for the new order to take effect. See Config File.