Links
Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated 2 months ago
All versions
1.1.0-beta.1
Alpha
ForceBlend 1.1.0-beta.1 UNTESTED2 months ago 127
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
Platform
Fabric
Supported environments
Singleplayer only
Changes
User experience
- Added a read-only pre-analysis that counts scanned chunks, affected chunks, deferred chunks, and affected regions before any write.
- Added an estimated processing time based on the current analysis, with a conservative fallback when no useful sample exists.
- Added four post-analysis choices: apply and enter; back up, apply and enter; enter unchanged; or cancel.
- Added live analysis, backup, validation, and processing progress for larger jobs.
- Progress can show percentage, chunks or regions completed, ETA, active region files, and chunk throughput.
- Added a completion notification where desktop notifications are available.
Configuration and backup
- Added optional Mod Menu integration without making Mod Menu a runtime requirement.
- Added persistent settings for automatic analysis, automatic backup, detailed logs, per-opening chunk limits, and processing threads.
- Defaults are automatic analysis on, automatic backup off, detailed logs off, unlimited chunks, and all available processors.
- Settings are stored in
<game>/config/forceblend.propertiesusing atomic replacement. - Added complete world ZIP backups under
<game>/backups/forceblend/<world>/<timestamp>.zip. - Backups reject unsafe links and overlapping source/destination paths, keep timestamp collisions, clean partial files, and are discarded if the world changes during creation.
Processing and safety
- Split processing into a reusable immutable plan and an apply phase, so the confirmation dialog does not require a second full analysis.
- Added deterministic per-opening limits; deferred chunks remain eligible on later world opens.
- Region analysis, stale-plan validation, and application can use multiple worker threads while each region file still has a single writer.
- Added stale-plan checks for the region set, file metadata, Anvil headers, planned chunk outcomes, and external chunk payloads before replacement.
- Preserved temporary-file region assembly, forced writes, validation, unchanged-region avoidance, and cleanup on failure.
- Added recoverable multi-file commits for changed external
.mccchunks, restoring the original sidecars and region if any replacement move fails.
Verification status
- The automated test suite passes for the
1.1.0-beta.1code line. - This beta has not yet been re-tested in game on 1.18.2 or 26.2. Do not treat its automated status as a gameplay verification.
- Stable 1.0.0 remains the release verified in game on Minecraft 1.18.2 and 26.2.
- No performance benchmark claim is made for this beta.
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:Au3ykER5:R7mqrYPU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Au3ykER5:R7mqrYPU"
}

