Tags
Creators
Details
1.3.0+1.21.11
Compatibility
Changes
Coinkeep 1.3.0 for Minecraft 1.21.11 — the same features and content as 1.3.0, ported to a new game version (NeoForge 21.11.45). All 13 automated tests pass, and the book, shop and recipes were verified in a live client.
Upgrading a 1.21.1 world to 1.21.11?
- Stored balances, market demand and the starter-book flag do not carry over — NeoForge changed how player data attachments are stored between these Minecraft versions, so the old data is skipped with a log warning. Vault contents and banknotes survive, since they live in ordinary block and item data. On a live server: have players vault their money or withdraw it as banknotes before upgrading, then deposit again after.
- Fresh 1.21.11 worlds are unaffected.
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:O0a6NLTz:U7mVwH6k"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O0a6NLTz:U7mVwH6k"
}

