
Ultimate Scaler
An advanced tool mod designed for exploring the furthest boundaries of Minecraft's terrain generation. It not only provides a stable path to the legendary Far Lands but also allows you to manipulate the core rules of world generation itself
Links
Tags
Creators
Details
0.4.0+1.21
Compatibility
Required content
Changes
English | 简体中文
Marking the completion of the project refactor, this release rebuilds the project's foundation rather than adding gameplay features. In-game behavior remains compatible, and existing V2/V3 configurations migrate automatically to the new V4 format.
Added
- A new configuration screen with five categories, unified environment/risk/performance/restart labels, a distance-effect legend, dependent sub-options, decimal validation, block dropdowns, and clickable Wiki/Issue links.
- Automatic migration from V2/V3 configurations to the V4 configuration model.
- AppVeyor nightly and release pipelines; tagging a release now builds, packages and publishes automatically.
- Project documentation and community infrastructure: a rewritten README, CONTRIBUTING, a contributors list, bilingual Issue templates, expanded Wiki pages, and Javadocs for core code.
- Third-party license files for bundled dependencies.
Changed
- The configuration model is now V4, organized into General, World Generation, Fixes & Expansion, and Utilities, with field names that better match their behavior.
- Configuration migration results are written back immediately; the V2 file is deleted only after the new configuration has been saved successfully.
- The keybind now opens the new configuration screen directly. Configuration loads at startup, a default file is
generated on first launch, and
/reloadre-reads the file. - The configuration file header now links to the Wiki; detailed documentation lives in the Wiki and in the screen's tooltips.
- Migrated to mojmap and the modern Fabric template, renamed the package to
xyz.inf32768.ultimatescaler, and split client/common sources. - Unified configuration naming, added
ModMetadatafor shared constants, and switched version checks to Fabric's built-inVersion. - Upgraded to Gradle 9.5.1, Loom 1.17, Fabric Loader 0.19.3 and Fabric API 0.136.1.
- Replaced fragile
@ModifyConstantinjections to improve cross-version compatibility. - Rewrote
locate pos: all parameters are nowdouble, negative values are supported, manual range selection is gone, and calculations are dramatically faster. - Cached debug HUD coordinate conversions to avoid repeated work.
- Adopted Conventional Commits, trunk-based development, and atomic commits as the project workflow.
Deprecated
- The old configuration screen remains as a transition and is marked deprecated; hold Shift while clicking the mod icon in Mod Menu to reach it. It will be removed in a future release.
Removed
- Per-option comments are no longer written to the configuration file.
- Manual range selection in
locate pos. - The vendored toml4j source; toml4j is now a regular dependency.
Fixed
- Fixed configuration loading so it no longer replaces the active configuration with defaults when loading or V3
migration fails. The previous configuration is kept and written back; if there is no previous configuration, defaults
are used. Before a fallback write, the original file is backed up as
ultimate_scaler.toml.bak; saves use a temporary file with atomic replacement when the filesystem supports it. - Fixed the
RELEASEFar Lands position behavior. - Fixed incorrect End island offsets in certain configurations.
- Fixed
raritycalculation inWeirdScaledSampler. - Fixed a wrong mixin target for mineshafts.
- Fixed several 1.21.x compile/runtime issues, including a fluid sampler crash and mixin loading conditions.
Upgrade note: Existing V2/V3 configurations migrate to V4 automatically; back up custom configurations before upgrading. The old configuration screen is deprecated and will be removed in a future release.
Automated smoke tests remain a deferred follow-up; build verification is currently in place. Normal feature development resumes from this release.
Optional dependencies
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:ktrA4Qtm:rz9pq864"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ktrA4Qtm:rz9pq864"
}
