All versions
1.1.0
Release
BuyClaimChunks Continued 1.1.02 months ago 49
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
Added
- NeoForge 1.21.1 support.
- Configurable progressive pricing based on the player's current personal extra-claim total in FTB Chunks.
- Configurable currency item, personal extra-claim cap, and per-command purchase limit.
- Bulk purchases with sequential per-slot price calculation.
- Automated pricing tests and dedicated-server startup validation.
- Complete English and Japanese installation, configuration, migration, and troubleshooting guides.
Safety
- Payment items are consumed only after FTB Chunks confirms that the personal extra-claim allowance was increased.
- Invalid configured item IDs, excessive totals, and purchase-limit violations stop the transaction without consuming items.
- Price calculations include overflow protection.
Important
- This mod increases a player's personal FTB Chunks extra-claim allowance. It does not automatically claim a chunk and does not increase an FTB Teams party allowance.
- The original BuyClaimChunks and BuyClaimChunks Continued use the same
buyclaimchunksmod ID and cannot be installed together. - Existing
buyclaimchunks-common.tomlfiles are preserved. To use the new default price curve, change an oldamountRequired = 1value to4, or regenerate the config while the server is stopped.
Requirements
- Minecraft 1.21.1
- NeoForge 21.1 or newer within the Minecraft 1.21.1 line
- Java 21
- FTB Chunks 2101.1.20 or newer, below 2102
- FTB Chunks' required dependencies: FTB Library, FTB Teams, and Architectury API
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:A5Li9858:VILxjEgX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:A5Li9858:VILxjEgX"
}

