Tags
Creators
Details
1.20.1-7.3.2
Compatibility
Changes
Changelog for Custom Advancements 7.3.2 for Forge 1.20.1
This update brings the 1.20.1 version in line with the code base of the 1.21.1 version and adds several new features and bug fixes.
⚠️ Some config options were removed or renamed. Please check the Breaking changes section before updating an existing world or modpack.
✨ New features
Customizable advancement screen size
- The advancement screen can now be enlarged to use the available screen space.
- New client config file
customadvancements-client.tomlwith the optionadvancementScreenSize(0–100 %, default90). - The space for the advancement tabs (and Forge's tab page buttons) is always keptfree, and the screen never gets smaller than its vanilla size (
0= vanilla size). - The window frame, the background, the tabs, the tooltips and the centering/scrollingof the content all adapt to the new size.
Display of connected advancements
- Root advancements that have a dummy parent in the
connectedAdvancementsListnow show that parent as a translucent widget next to them, including the connection line, its tooltip and its current progress. - New client config option
connectedParentOpacity(0–100 %, default40). Setting it to0turns this display off completely. - The parent is only shown if the player can already see it.
Improved advancement screen
- The window title now shows the name of the selected tab instead of"Advancements". Long names are cut off at the window border.
- Tab tooltips that would leave the screen at the top are now shown below the mouse.
Progression blacklist with wildcards
- New option
progressionBlacklist: a list of advancements that are not affected by the advancement progression system. - New option
progressionBlacklistIsWhitelist: turns the list into a whitelist, so only the listed advancements are affected. - Both lists support wildcards:
modid:*matches all advancements of a mod, andmodid:path/*matches all advancements inside a folder (e.g.minecraft:story/*). - Wildcards work in
advancementsBlacklistas well. - Entries of the
connectedAdvancementsListalways take precedence over the progression blacklist.
Server-side textures and translations
- Custom background textures, translations and advancement backgrounds are now sent from the server to the client. Players on a dedicated server no longer need the files locally.
- Advancement files are loaded asynchronously, which speeds up loading.
⚠️ Breaking changes
| Old option | New behaviour |
|---|---|
advancementProgressionMode |
Removed. Use progressionBlacklist instead (e.g. minecraft:* to only affect vanilla advancements together withprogressionBlacklistIsWhitelist = true). |
modBlacklist / modBlacklistIsWhitelist |
Removed. Use progressionBlacklistwith modid:* entries instead. |
noAdvancements |
Removed. Use an empty advancementsBlacklist together withblacklistIsWhitelist = true instead. |
disableStandardAdvancementLoad |
Renamed to disableStandardAdvancements. |
Commands
- All commands are now only available under
/ca(the/customadvancementsalias was removed). /ca generate resource_locations→ renamed to/ca generate ids./ca generate advancement <id>and/ca generate advancement allkeep their names./ca reloadwas removed. The vanilla/reloadcommand now also reloads the mod's files.
🐛 Bug fixes
- Fixed a crash when a gradient background (
LINEAR_GRADIENT/RADIAL_GRADIENT) had an empty or missingcolorsarray. - Fixed missing textures when a background was invalid (e.g. a
COLORbackground without acolorfield). An invalid background no longer prevents the other backgrounds from loading. It falls back to no background and logs an error.- Fixed advancements staying visible on the client after a/reloadremoved all visible advancements. - Fixed changes to the
connectedAdvancementsListonly taking effect after restarting the game. - Fixed being unable to scroll to content placed left of or above the tab root.
- Fixed a crash caused by texture files without a file extension.
- Texture files with invalid characters in their name are now reported with a clear error message instead of failing silently.
connectedAdvancementsListentries no longer need exactly one space around->. Invalid entries are skipped with a warning instead of causing errors.
🔧 Improvements
- Config entries are now only checked for a valid format. Entries that don't match any known advancement are logged as warnings while the advancements load, instead of being silently removed from the config.
- Updated and unified chat messages and translation keys.
- Added translations of the example advancement "Back to the Roots" (German, Spanish, French).
🗑️ Removed
- Compatibility code for BetterAdvancements.
- The update checker (chat message and update URL).
- The custom crash report section.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:cvjKMjpc:PeY4BxFP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cvjKMjpc:PeY4BxFP"
}

