Tags
Creators
Details
2.0
Compatibility
Required content
Changes
This is a major update to the mod, and contains the following changes:
- Switched to environment fog instead of fake client-side only status effects. This means that the fog this mod provides is now fully customizable, and does not rely on pre-existing status effects.
- Added the ability to customize the fog, and the following details are available for customization: view range (fog end), thickness (fog start), and color. Customization is available for both the default fog and world-specific fogs.
- Added fog presets. Blindness and Darkness now act as fog presets.
- Re-added Truly Blind mode as a fog preset. This is a more difficult version of the Blindness fog, where the it is hauntingly close, with a radius of 1.9 blocks, as opposed to Blindness's 5 blocks.
- Added Silent Hill as a fog preset. This is less restrictive than Blindness but has a dark, foggy blue color.
- Visually revamped the configuration screens. This is a side effect of adopting YetAnotherConfigLib.
- Removed server-side integration. This removal was scheduled since 12 of february, 2026. For more information, read the deprecation notice.
- Darkness (the BlindMe setting) no longer causes the world gamma to pulse. This, by itself, was not considered a feature and thus the option to remove the pulsing darkness has been removed.
- Blindness and Darkness (the status effects) now properly show up in the inventory screen.
- The lock button on the configuration screen no longer asks for confirmation before locking or unlocking. This is a technical limitation of adopting the YACL configuration library.
This version was compiled against Minecraft 26.2, and requires Fabric Loader (or equivalent), Fabric API (or equivalent), and YetAnotherConfigLib.
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:EJoehBeH:RU0InoHl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EJoehBeH:RU0InoHl"
}



