Tags
Creators
Details
1.6.0+fabric-26.2
Compatibility
Required content
Changes
Changelog
v1.6.0
Subtitles now show on quest tooltips and can run over several lines, quests can use a live mob as their icon, locked icons can stay at full color, and advancement tasks show the advancement's own icon. FTB Quests imports keep image titles. This release covers issues 54 and 88 to 91.
The network protocol changed, so clients and servers both need 1.6.0.
New for players
- Quest tooltips show the subtitle under the title. The Quest subtitles setting picks both tooltips, only simple or only advanced
- Dim locked icons in the map settings. Turn it off to show the icons of locked quests at full color in any theme
- Mob icons in the map settings. Turn it on to draw the mob on kill quests instead of its spawn egg, on the node and the task row. It is off by default because each mob redraws every frame
- Advanced tooltips no longer repeat the first line of the description
- The Classic theme keeps locked icons at full color, like FTB Quests
New for pack makers
- A subtitle can hold several lines. Write
\nin the JSON, or use the new text box in the quest editor - Advancement tasks use the advancement's own icon instead of a knowledge book, even before the player can see that advancement. A task
iconstill replaces it iconstakesall, which covers every state exceptunknown- Entity icon layers take
pose,yaw,pitch,spinandnbt, the same fields as the entity content block client_defaults.jsoncan setmap.subtitles,map.dim_lockedandmap.mob_iconsfor a whole pack
FTB Quests import
- Image titles become decoration tooltips, one line per
\n. An image with no click action is left without one, because FTB Quests never shows its title
Optional dependencies
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:f456ZrGZ:prakeJYP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:f456ZrGZ:prakeJYP"
}

