Tags
Creators
Details
Licensed LGPL-3.0-only
Published last year
Updated 16 hours ago
All versions
1.7.2
Release
ResourcePackManager 1.7.29 months ago 461
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
Platforms
Paper
Purpur
Spigot
Changes
Resource Pack Manager 1.7.2:
- [New] Added collision log file (collision_log.txt) - all file collisions are now logged to a single file instead of flooding the console.
- [New] Added HTTP timeout configuration for Auto Host requests - 30 second connect timeout, 60 second default socket timeout, and 5 minute timeout for file uploads to prevent hanging connections.
- [New] The mixer folder is now automatically created on startup, making it easier for users to add custom resource packs.
- [Fix] Fixed overlay directories from ItemsAdder and similar plugins being incorrectly merged - directories containing "overlay" or starting with "ia_overlay" are now skipped.
- [Fix] Fixed problems related to merging shaders
- [Fix] Reduced resource pack send delay from 5 seconds to 1 second for faster processing after stability is detected.
- [Fix] Reduced console spam by removing verbose logging for routine operations (resource pack additions, cluster copies, pack.mcmeta copy, skipped packs).
- [Fix] Fixed server lag caused by resource pack mixing running on the main thread - mixing now runs asynchronously.
- [Fix] Fixed zip extraction failing when the output directory didn't exist yet.
- [Fix] Improved error logging when resource pack extraction fails - now shows detailed error messages.
- [Fix] Merged resource packs now use ResourcePackManager's own pack.mcmeta, ensuring valid and compatible metadata.
- [Fix] Custom core shaders are now removed from merged resource packs to prevent shader compilation errors caused by version-incompatible shaders.
Optional dependencies
Any compatible version
Any compatible version
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:jmQaa0X3:uyD8NYLU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jmQaa0X3:uyD8NYLU"
}

