Tags
Creators
Details
4.3.0-legacy
Compatibility
Changes
LPC 4.3.0 โ Multi-version support (Paper 1.21.x and 26.2)
This release ships two jars so LPC runs on both old and new servers. Pick the one for your platform on the Modrinth download page (Modrinth's game-version filter shows the right one automatically):
| Build | Minecraft | Java | Adventure | api-version |
|---|---|---|---|---|
LPC-4.3.0.jar (default) |
26.2 | 25 | 5.2.0 | 26.2 |
LPC-4.3.0-legacy.jar |
1.21.x (incl. 1.21.11) | 21 | 4.23.0 | 1.21 |
Why two jars?
Adventure 4 (bundled by Paper 1.21) and Adventure 5 (bundled by Paper 26.2) are binary-incompatible โ a single jar cannot reliably run on both. The same LPC source now compiles + passes all tests against both Adventure versions; the Gradle -Ptarget=modern|legacy switch selects the platform.
๐ Still includes the 4.2.0 security fix
The defence-in-depth ComponentSanitizer (strips click/hover/insertion from player & item-name output) is in both builds.
Bug fixes & UX
- Fixes the recurring "Unsupported API version" / "plugin won't load on 1.21.11" reports โ use the
-legacyjar on Paper 1.21.x / Java 21. /lpc versionnow reports the build target (e.g.Build: Minecraft 1.21.x ยท Java 21 ยท Adventure 4.23.0 (legacy)) so support can tell which jar you installed.build.ymlCI runs a modern + legacy matrix on every PR.
Installation
- Paper 26.2 / Java 25 โ download
LPC-4.3.0.jar - Paper 1.21.x / Java 21 (incl. 1.21.11) โ download
LPC-4.3.0-legacy.jar
Requires LuckPerms. PlaceholderAPI optional.
Full changelog: https://github.com/Ayont/LPC-with-minimessage/compare/4.2.0...4.3.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:mYs2fo1e"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LOlAU5yB:mYs2fo1e"
}

