Tags
Creators
Details
1.1.3
Compatibility
Required content
Changes
Please Read
This version is accessible on Modrinth primarily for modpack purposes. However, please be aware that this version is no longer supported or updated.
We recommend players to update to the latest version to ensure optimal performance and access to ongoing support. Thank you for your understanding.
Changelog:
This is planned to be the last 1.16.5 update. On to 1.17!
Hotfix to fix some critical issues with the previous release
Fixes
The Nightwatcher will no longer crash the game if its workstation is broken while robbing a villager.
Hostile mobs should spawn once again.
Previous Changelog:
Additions
- Small Frostbright trees can be grown with a single sapling.
- The Mason villager profession can sell the opposite dimension's stone bricks, allowing you access to both dimensions once you have found one.
- Added translations for Simplified Chinese, and unfinished translations for Spain Spanish, Hungarian, Italian, Japanese, and Turkish.
Fixes
- The Gatekeeper house no longer generates in dimensions that it shouldn't, such as the Twilight Forest.]
- Increased village spawnrates yet again. The spacing between them has been decreased by 1/4.
- Fixed a possible crash that could occur with the Diophyde Prowler.
- The Alchemy Table no longer takes up an extreme amount of memory with JEI, and is much easier to look at.
- Fixed a crash with Mowzie's Mobs.
- Fixed saplings not being able to grow in the Everbright or Everdawn.
- Fireflies should begin spawning on the surface instead of underground.
- Adjusted bosses to fix some issues with unintended combat mechanics.
- Fixed the food prep table crashing on startup with some mods.
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:DOSy3C4M:GGNu2fsd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DOSy3C4M:GGNu2fsd"
}

