Skip to main content
No. None of the /ca/generate/... commands require operator permissions — any connected player can run them, and in single-player they work whether or not cheats are enabled. See Commands.
Not in this version. The three /ca/generate/... commands automatically trigger a reload of advancements, textures, and language files after they finish writing. If you hand-edit a JSON file directly instead of using a generate command, run the vanilla /reload command (or restart the game) to pick up your changes — see Quickstart.
No. Custom Advancements reads JSON files directly from the customadvancements/ folder in your game directory and injects them into every world as if they were a global datapack — no datapacks/ folder setup, and no per-world configuration needed.
This version of Custom Advancements targets Minecraft 1.21.1 on both Fabric (with Fabric API and Forge Config API Port) and NeoForge. See Installation for exact minimum versions.
No — edit the config file while the server is stopped, then restart to apply it. Running a generate command or the vanilla /reload command does not re-read the config file; it only reloads advancement JSON, textures, and language files. See Config File.
Yes. Set disableStandardAdvancements = true to stop the mod from loading anything except what’s in your customadvancements folder, or use whitelist mode (blacklistIsWhitelist = true) with an empty advancementsBlacklist to remove everything and add back only what you whitelist. See Blacklist & Whitelist.
Run /ca/generate/ids in-game. It writes every currently loaded advancement’s ID to customadvancements/advancements.txt, one per line. See Commands.
Yes. The background field accepts COLOR, LINEAR_GRADIENT, and RADIAL_GRADIENT types in addition to IMAGE and the vanilla-style tiled TEXTURE. See Background Types for every option.
Yes. Custom textures and language files are synced to clients over the network, but only a client actually running Custom Advancements can receive and render them. A player without the mod sees Minecraft’s vanilla defaults instead. See Textures and Language Files.
Yes — set noRecipeAdvancements = true. It removes every advancement whose path contains recipes/, independently of advancementsBlacklist. See Config File.