Tags
Creators
Details
Licensed LGPL-3.0-only
Published last year
Updated last week
All versions
2.3.1
Release
ResourcePackManager 2.3.12 months ago 3,702
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.4β1.21.11
Platforms
BungeeCord
Paper
Purpur
Spigot
Velocity
Waterfall
Changes
ResourcePackManager 2.3.1:
- [New] Bedrock players now receive custom entity models through a bundled Geyser extension shipped in the plugin folder
- [New] Plugin updates now propagate automatically across proxy and backend servers
- [New] Proxy networks now provision one shared network key to backends automatically, including setups where Floodgate runs only on the proxy
- [New]
/rspm statusshows a safe network-key fingerprint and source, and warns clearly when the proxy is missing ResourcePackManager - [New] Added a setting to disable automatic Geyser extension installation and update staging
- [New] Admins are now notified in game about unread releases and can review them from the ResourcePackManager changelog command
- [New] Added
/nightbreaklogoutfor clearing the stored Nightbreak account token - [Fix] A corrupt or unreadable pack no longer loops the mixer forever; it is quarantined while remaining packs are delivered
- [Fix] A failed Bedrock conversion no longer withdraws the last verified pack and mappings
- [Fix] A backend that cannot reach the hub now backs off instead of retrying every five seconds
- [Fix] Proxy-only Floodgate installations no longer leave each backend with an incompatible self-generated key
- [Fix] Current Geyser item definitions and Bedrock asset mappings are converted consistently
- [Fix] Downloaded plugin updates are validated before replacing the installed jar
- [Fix] Servers no longer log a command-unregistration error while shutting down on Paper 26.2
- [Tweak] Bedrock packs are optimized before publication
- [Tweak] Setup and status output now gives direct repair instructions for missing proxy components
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:T7XPqweQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jmQaa0X3:T7XPqweQ"
}

