Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 4 months ago
All versions
0.8.3
Beta
Lattice 0.8.35 months ago 10
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Paper
Changes
Added
- Added
CommandExceptionMappersas the reusable default command failure mapper for plugins that build command registration manually. - Added
LatticeRuntime.COMMAND_EXCEPTION_MAPPERso Paper plugins can customize command failure wording through the runtime service model. - Added explicit
LatticeBuilderhelpers for default service registration, intentional service replacement, and service lookup during bootstrap. - Added standalone descriptor coverage to keep the Paper release jar dependency list intentional.
Changed
- Typed
LatticeBuilderservice helpers now provide defaults only when a service has not already been supplied. - Paper bootstrap now creates the default command registrar after plugin customization and passes the configured command exception mapper into it.
- The standalone Paper descriptor no longer declares Junction as an optional dependency; Junction remains available through reflective integration detection when present.
- Public authoring docs now spell out service customization, command feedback ownership, command help ownership, and optional integration checks.
Fixed
- Supplying a custom
COMMAND_SERVICEno longer constructs the default Paper command registrar or registers its lifecycle handler as a side effect. - The standalone descriptor test now fails on accidental optional dependency additions, not just missing expected dependencies.
Compatibility
- Existing strict
LatticeBuilder#service(key, service)behavior is unchanged. - Plugin code that intentionally replaces a service should use
replaceService(key, service). - Plugin code that only needs custom command failure text should prefer
commandExceptionMapper(...)instead of replacing the full command service. - Plugins using Junction integration should check
PaperIntegrations.JUNCTION_VARIABLES; declare a plugin dependency only when their own load order requires Junction.
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:Ed95iBPq:brq1q5Nh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ed95iBPq:brq1q5Nh"
}

