Tags
Creators
Details
4.4.0
Compatibility
Changes
LPC 4.4.0 โ one jar for everything
No more picking the right build. LPC 4.4.0 ships a single universal jar that runs on Paper 1.21.x (incl. 1.21.11) AND Paper 26.2. Just download LPC-4.4.0.jar and it works on your server, whatever the version.
Why one jar works
Compiled once against Paper 1.21 / Adventure 4 / Java 21 (api-version: 1.21):
api-version: 1.21is accepted by Paper 26.2 (forward-compatibility)- Java 21 bytecode runs on Java 25
- the Adventure APIs LPC uses stay binary-compatible across Adventure 4 โ 5
A new crossCompatTest CI task proves this every build by running the Adventure-4-compiled tests against an Adventure 5 runtime โ the exact thing a Paper 26.2 server does. (It already caught and fixed one real incompatibility.)
๐ [item] permission fix
[item] needs the lpc.itemplaceholder permission โ which previously defaulted to false, tripping up users (even admins) who only enabled the config. Now:
lpc.itemplaceholderdefaults toopโ ops can use[item]immediately- players who type
[item]without the permission get a friendly in-chat hint - to enable
[item]for everyone:/lp group default permission set lpc.itemplaceholder true
Platform detection
- startup log:
Running on Paper (API 1.21-R0.1) on Java 21 [Paper/Adventure chat] /lpc versionnow shows the build target and the live runtime (API + Java) โ great for support
Still includes
- the 4.2.0 chat click/hover/insertion exploit fix (defence-in-depth sanitizer)
- MiniMessage chat formatting, LuckPerms group/track formats, PlaceholderAPI, @mentions, emojis, clickable links, [item], moderation toolkit
Requirements
- LuckPerms (required) ยท PlaceholderAPI (optional)
- Paper 1.21.x โ 26.2, Folia or Spigot ยท Java 21+
Full changelog: https://github.com/Ayont/LPC-with-minimessage/compare/4.3.0...4.4.0
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:LOlAU5yB:ujzZ1xJ4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LOlAU5yB:ujzZ1xJ4"
}

