Tags
Creators
Details
1.5.0+fabric-26.2
Compatibility
Required content
Changes
Changelog
v1.5.0
Item rewards can give a random item from a tag, quests can take their own spot in the world view, backgrounds zoom with the map, shaders get rounded corners, and add-ons get a server API. This release also fixes the reports from issues 72 to 87, including shader styles that lost their settings on Forge 1.20.1.
Packs that use tag rewards or world positions need 1.5.0 on clients as well as the server. The network protocol did not change.
New for pack makers
- Item rewards take a tag as
item, such as"item": "#minecraft:flowers". Each claim gives one random member, the reward row cycles through the members, and an empty tag refuses the claim. Reward tables take them too - Quests take
"world": {"x": 3, "y": -2}, a position in the chapter world view separate from the map position. The quest editor has World X and World Y fields for it - Background shader presets that follow the map now zoom with it.
U_Zoom=0keeps a preset at its pixel size - A
shadercontent block draws a preset in a box, as a map decoration or inside a description. It takeswidth,heightand a nodeshapesuch ascircleorstar, which presets that follow the node shape adopt - Every shader texture takes
U_Corner, a corner radius in GUI pixels. The shader is clipped to the same rounded boxsdf()draws - FTB Quests imports keep Ember's Text API tags and custom tag pairs that open and close on one line, instead of escaping them.
<click>tags still import as plain text
New for players
- Task and reward items show the full item tooltip, with or without a recipe viewer
- Crafting recipes that fit the 2x2 inventory grid draw as a 2x2 grid with JEI, EMI or REI installed, instead of the viewer's 3x3 page
- Dependency lines end at the node's shape instead of its square box, and quests on touching tiles keep their arrow on the shared edge
In the editor
- Alt click a required quest to remove the dependency. The node menu and the "Edit N quests" window have "Remove requirement" too
- Scene timeline keys can be copied with Ctrl+C, pasted at the playhead with Ctrl+V, and duplicated or deleted from a right click menu
For add-on authors
QuestApireads and writes task progress, finds quest owners, works on offline players, completes quests quietly, explains why a quest is blocked and lists book problems.QuestEventsgainsrewardClaimed,bookLoadedand aSourceon task progressQuestBookApiopens chapters, selects quests, closes the details and reports media loads, scene builds and the world theme
Fixes
- Shader styles and quest effects with a
scale()lost their uniforms and transform, so the shader fell back to its defaults - Description paragraphs no longer overlap after the quest window changes width
- Dependency arrows between overlapping nodes no longer draw on top of them
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:5ZhNCXsZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:f456ZrGZ:5ZhNCXsZ"
}

