Tags
Creators
Details
Licensed ARR
Published 3 years ago
Updated 3 weeks ago
All versions
3.8.7
Release
PluginPortal 3.8.73 weeks ago 1,668
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
PluginPortal 3.8.7
- Added external plugin management through YAML adapters, including GitHub release downloads, imports, managed filenames, and recognition exclusions.
- Added
/pp list --outdatedwith marketplace and external plugins in one view. Use/pp list --externalfor external plugins only. - Added
/pp searchfor related results while keeping/pp installand/pp viewfocused on unique exact-name matches. Duplicate names now include provider IDs for disambiguation. - Added
/pp update <plugin> --refreshto bypass cached marketplace metadata after a plugin release. - Improved compatible-version selection across Paper, Folia, SpigotMC, Hangar, Modrinth, and Polymart. Plugin Portal now checks full paginated version histories when the cached results do not contain a compatible build.
- Added free Polymart download support. Paid Voxel Shop and Polymart plugins remain visible for entitlement checks but cannot be downloaded or updated through Plugin Portal.
- Preserved marketplace identity during imports and prevented incompatible Plugin Portal self-updates.
- Migrated older
plugins.jsonentries that do not contain anentryId, so existing servers can replace the JAR without rebuilding their managed-plugin state. - Fixed missing command output on newer Paper builds, stuck
Loading...suggestions, already-installed output, command separator spacing, and several noisy multi-line install and update results. - Added safer premium entitlement validation and restored supported marketplace license-key imports without treating placeholder values as real keys.
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:5qkQnnWO:kRPQKWCU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5qkQnnWO:kRPQKWCU"
}

