Tags
Creators
Details
1.5.2
Compatibility
Changes
[1.5.2] - 2026-06-18 โ Legacy config-read fix + 20 new titles
Fixed โ legacy snake_case configs silently mis-parsed
Config files written before the 1.1.0 ConfigHolder refactor were serialized by the old
YACL serializer, which named nested-POJO fields in snake_case (title_id,
hide_requirements, item, skill, level). The current loader uses plain Gson with
IDENTITY field naming, so none of those keys matched the Pascal-case Java fields. Gson
constructed each object via its no-arg constructor and overrode nothing:
- Titles: every entry in a legacy
titles.json5collapsed to the constructor default (rookie). After the registry's dedup-by-id, only Rookie survived โ so the Title tab showed just Rookie + the two system titles (Administrator, Titleless) instead of the full list. This was the reported "only three titles" bug. - Item locks: every entry in a legacy
lockItems.json5collapsed to the default (minecraft:diamond/ Strength 2), silently breaking configured item gating.
Fixed by adding Gson @SerializedName(value = "<Pascal>", alternate = {"<snake>"}) to the
nested model fields (TitleModel, LockItem, LockItem.Skill). Both legacy snake_case and
current Pascal-case files now load correctly; new writes stay Pascal. Top-level @SerialEntry
fields (common.json5) were written verbatim camelCase and were never affected.
Added โ title default-merge on load
ConfigHolder loads an existing file as-is with no merge, so titles added to the built-in
defaults never reached players who already had a config. RegistryTitles.load() now unions
any built-in title whose id is missing from the loaded list (preserving existing entries and
custom tunings) and saves โ which also rewrites a legacy snake_case file in Pascal-case.
Added โ 20 modpack-themed titles
Boss kills (Ice & Fire gorgon/hydra/sea serpent, Cataclysm ignis/ender guardian, Bosses of Mass Destruction night lich/obsidilith, Mowzie's ferrous wroughtnaut, vanilla warden/wither), spellcaster titles (spellweaver/summoner/elementalist), Tinkering titles (artificer/master artificer/engineer), martial hybrids (gladiator/berserker/monk), and a spelunker title (mine ancient debris).
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:t7ORhK67:p0VNUDAQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:t7ORhK67:p0VNUDAQ"
}

