Tags
Creators
Details
2.0.0
Compatibility
Changes
Complete Rewrite + Paper API Migration (BREAKING CHANGES)
This is a huge update for PackManagerPro which includes breaking changes. Please read over all items below as they do affect existing users.
Paper API Migration
As of this release, 2.0.0, PackManagerPro has moved off of the Spigot API and over to the Paper API.
PMP has been completely rewritten from the ground up using Kotlin, Gradle, and most importantly the Paper API.
The move to the Paper API was necessary in order to continue to evolve with the modern Minecraft server landscape.
The rewrite in Kotlin + Gradle was done because lots of rewriting was going to be needed anyways for the migration to the Paper API.
What Does This Mean For You?
How you use PackManagerPro:
❗ PackManagerPro will no longer work on plain Spigot servers, and will only work on Paper (or Paper-based) servers (like Purpur).
Chat Formatting System Change
With the migration to the Paper API, we also switched to using Paper's preferred chat formatting and coloring API, MiniMessage.
❗ You will need to update you message formatting in your config to support the MiniMessage format.
ℹ️ If you have not changed your messages from their defaults, you can replace your messages section with the following:
messages:
prefix: "<dark_gray>[<dark_green>PackManagerPro<dark_gray>] <reset>"
reload: "<gray>PackManagerPro has been reloaded."
no-permission: "<red>You do not have permission!"
Minimum Version of 26.2
This version of PMP strictly supports a minimum game version of 26.2.
Bug Fixes & Other Changes
- Fixed a bug in the per-world configuration where the resource pack from a world wouldn’t clear when the player switched to a world without a resource pack configured.
- Fixed any other bugs potentially associated with running previous versions of PMP on modern Paper servers. (Since Paper uses a different API for sending resource pack requests).
- Polished text in config and plugin documentation.
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:8URCbL42:rMYAB6Wx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8URCbL42:rMYAB6Wx"
}

