Links
Tags
Creators
Details
Licensed ARR
Published 4 months ago
Updated 3 days ago
All versions
1.0.5
Release
FTB Quests UI Overhaul 1.0.52 months ago 61
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client-side
Changes
Changes from 1.0.2 to 1.0.5
1.0.3
Navigation
- Opening the questbook or switching chapters now focuses the camera on your progress instead of the middle of the chapter: your tracked quest, then anything with rewards waiting, then whatever you can do next, and in an untouched chapter its starting quests
- When several quests need framing, the view zooms out just enough to fit them - it never zooms in past the zoom you chose. Capped at the eight targets nearest their centroid so a chapter with many scattered roots does not drag the camera to minimum zoom
- New rebindable key (default Space) re-centers the quest view on your progress, like the default FTB Quests UI
- New Tracked Quest button jumps straight to the quest on your HUD and opens it, so you can untrack it without hunting through chapters - it cycles in book order if you have several tracked
- New chevron beside the QUEST CHAPTERS title collapses or expands every chapter group at once
Fixes
- Rewards marked invisible (commonly command rewards used for backend functionality) are no longer shown in the quest popup, and a quest no longer advertises an unclaimed-reward state - or becomes a camera focus target - for rewards nobody can see
- Long quest subtitles no longer overflow outside the quest popup: they were wrapped against the description's text scale but drawn at the larger objective scale, so every line came out wider than its budget
- Formatted quest descriptions are preserved
- Quest item recipe clicks restored
1.0.4
Recipe viewer
- Clicking a quest requirement now opens JEI. Previously these clicks fell through to the default FTB Quests UI: FTB Quests 2001.x ships no recipe-viewer integration, so its
getRecipeModHelper()is always the no-op whoseisRecipeModAvailable()returns false, and the recipe branch could never be taken. The mod now talks to JEI directly through a@JeiPlugin, keeping the FTB helper as a fallback for REI/EMI users who have FTB XMod Compat - JEI stays optional: the API is compileOnly and no JEI class is named outside the plugin
- Requirement clicks now resolve the stack the icon is actually showing, so tag-based item tasks and foreign task types open a recipe too, instead of only single-item tasks. Submitting still wins where a task can be turned in
Settings
- New description alignment setting (defaults to centered, matching the framed artwork)
- Added a config screen so Forge's Config button works - Forge 1.20.1 has no config UI of its own, so the button was inert without a registered
ConfigScreenFactory
1.0.5
UI
- The Tracked Quest button moved out of the chapter selector and into the frame strip below the quest tree: centered on the tree, shorter, and sized to its own label instead of the full chapter button width
Dev
- Added a kill-task quest to the local dev testing pack so the tracked state can be reached without the quest completing the moment it is accepted
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:BH8DzrcH:mCkLJCAT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BH8DzrcH:mCkLJCAT"
}

