Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated 3 days ago
All versions
2.0.0-beta.31-MC26.3
Beta
2.0.0-beta.31-MC26.33 days ago 6
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client-side
Server-side
Client and server
Changes
Player data and persistence
- Added
PlayerConfigto represent persisted player data and supply a default player ID. - Refactored Paper player registration to load and save player configurations through the integration’s configuration system.
- Registered the player collection as a config value so changes are actually persisted.
- Introduced a player factory and refactored
PlayerManager/PaperPlayersto centralize player creation and management. - Updated player lookup to use the configured player ID instead of storing a separate UUID on
PaperPlayer. - Added JSON initialization support for player models and their metadata.
- Improved UUID handling in
PlayerManagerby usingOptional.
Metadata and serialization
- Implemented
JsonSerializableforMetadata. - Initialize metadata when creating a
MinecraftPlayer, expose it for consumers, and serialize it with the player data. - Added metadata deserialization to the Minecraft and Paper player JSON constructors.
Paper plugin structure and fixes
- Refactored
QuiptPluginto providelisteners()andcommands()extension points, and movedPaperPlayersinitialization into the base plugin class. - Fixed the team ID check in
ExtraLifePlatform. - Updated
PaperPlayersto use the integration configuration and clarified how it retrievesPlayerConfig. - Registered
PartyCommandwith the command system.
Tests
- Added Mockito as a test dependency.
- Added unit tests covering metadata serialization and the Paper player lifecycle.
Build and publishing
- Updated the project build number to 27.
- Improved Modrinth upload logging to include version details after the task completes.
- Updated the upload webhook payload structure.
- Consolidated Jenkins configuration and added the Discord update channel and token to the pipeline environment.
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:Kgmpx44o:ZtvQe4g5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Kgmpx44o:ZtvQe4g5"
}

