All versions
1.1.0
Release
Ashen World 1.1.03 weeks ago 56
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Ashen World 1.1.0
Adds an in-game config screen and fixes the mutation threshold system to actually respond to config changes.
New Features
- In-game config screen — The Config button in the Mods menu is now
clickable. No third-party config mod (Configurable, Configured) required.
Opens a scrollable screen with sliders for all 15 config options across
4 categories:
- Radiation Thresholds (6 sliders: Tier 1/2/3 triggers, sickness, wither)
- Biome Radiation Rates (7 sliders: per-biome rad rates + global multiplier)
- Hazmat Armor Effectiveness (2 sliders: gain reduction, sickness reduction)
- FEV Sample Loot (1 slider: loot weight) Changes apply immediately and save to disk on close.
Bug Fixes
- Mutation thresholds now respect config values. Previously, the Tier 1 (400), Tier 2 (650), Half→Full (750), and Tier 3 (950) thresholds were hardcoded and ignored the config file entirely. The config screen was saving values correctly, but the mutation engine never read them. All four thresholds now read live from config, changes in the config screen take effect immediately without restart.
Notes
- All 15 config options are now functional. Previously only the biome rad rates, hazmat settings, sickness/wither thresholds, and FEV loot weight were wired to config. The four mutation thresholds were the only broken ones, now fixed.
- Config screen uses vanilla Minecraft GUI components (no external dependencies).
- JEI remains optional for Chem Station recipe browsing.
- Requires NeoForge 1.21.1.
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:p1mKaKWo:UQJkcq4b"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:p1mKaKWo:UQJkcq4b"
}

