Tags
Creators
Details
1.7.0
Compatibility
Required content
Changes
Full English changelog available on GitHub. Full French changelog available on our Discord.
Summary
This update improves the template screen with a larger layout, better group navigation, an integrated recipe preview, selection shortcuts, and several UI polish improvements.
Added
- Added a larger template screen layout
- Added an integrated recipe preview panel directly inside the template screen
- Added a larger and more readable recipe preview
- Added a small information button explaining template shortcuts
- Added
Ctrl + Asupport to select all visible templates - Added
Delete/Supprsupport to delete the current template selection - Added a visible counter for templates and selected templates
Changed
- Changed the group selector from a cycling button to a dropdown-style selector
- Changed the default open group to
Ungrouped - Changed the active group to be preserved when returning from Rename, Group, or Group Options screens
- Changed the recipe preview to be integrated into the main UI instead of floating outside the screen
Improved
- Improved search bar and group selector placement
- Improved bottom button alignment by centering the action buttons
- Improved template row readability with taller rows
- Improved template icon and text alignment inside the list
- Improved group dropdown rendering and readability
- Improved
no templates foundmessage placement - Improved shortcut help readability
Notes
Ctrl + Clickstill toggles multi-selectionCtrl + Aselects all currently visible templatesDelete/Suppropens the delete confirmation for the current selection- Double-click still loads a single template as before
- The regular delete button remains available for players who do not want to use keyboard shortcuts
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:bmJygyO3:72OnEVh5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bmJygyO3:72OnEVh5"
}

