Tags
Creators
Details
All versions
2.1
Release
2.12 years ago 313
Compatibility
Minecraft: Java Edition
1.21–1.21.4
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
Platforms
Folia
Paper
Purpur
Spigot
Changes
The final feature update is here! For more info check #379.
- Added compatibility all the way through
1.21.4 - Added config option to set the maximum jukebox range
- Added config option to set the base url of the web API
- Added support for decorated pots
- Added support for Geyser Standalone (just drop the plugin jar in the Geyser extension directory)
- Added vault support
- Added trial spawner support
- Added crafter support (Note: crafter preview doesn't work as of now)
- Added support for bedrock in gui mode
- Added
.nbsfile support - Fixed custom discs not dropping when chest explodes
- Fixed many more bugs (I can't remember them all lol)
- Updated dependencies
- Technical changes:
- Renamed the
Stateobject toJextState - Renamed
IntegrationtoPermissionIntegration - Reworked assets loading
- Reworked disc system
- Reworked config file management
- Reworked GUI system
- Renamed the
- WebUI changes:
- An entirely new style, giving the WebUI a resemblance to the Minecraft launcher
- Removed remote plugin management from WebUI now it's only a companion app exclusive
- Added
.nbsfile support - Added new dungeons to the selector
- Updated documentation
- Companion app changes:
- Direct download from Youtube/Soundcloud (and many more websites!) using
yt-dlp - Remote disc management
- Remote config management
- Bulk importing
- Community disc packs
- Exports history
- Now desktop app downloads will no longer expire
- Direct download from Youtube/Soundcloud (and many more websites!) using
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:LRzd464N:YbJCBDjf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LRzd464N:YbJCBDjf"
}

