Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 years ago
Updated 2 years ago
All versions
2.5.1
Release
Et Futurum Requiem 2.5.13 years ago 9,998
Compatibility
Minecraft: Java Edition
1.7.10
Platform
Forge
Supported environments
Client and server
Changes
# Et Futurum Requiem 2.5.1: Tiny Tweaks
Aaaaand welcome to the inevitable bugfix release shortly following a major Et Futurum Requiem version!
Additions:
- Added a config option in world.cfg to change the husk/stray spawn behavior back to the old behavior, where it'd be a part of the regular entity spawning table instead of replacing 80% of zombies or skeletons exposed to the sky.
- This is a response to #332 where OptiFine breaks the sky-exposure spawning logic. Gotta love OptiFine breakages =.='
- Added a config option to toggle honey blocks, honeycomb blocks, honeycombs and honey bottles separately from bees for pack authors who want to use them without backported bees.
- If you disabled the bees and want the blocks and items to stay disabled you'll need to turn this off. Bee nests and beehives are still tied to bees being enabled.
- Added the new sponge block sounds from 1.20.2, as well as the absorbing sound, removed the water particles and stone sound when absorbing water.
Fixes:
- Oak Chest Boat recipe is no longer broken
- Deepslate slabs now output 6 instead of 4
- Smooth quartz slab now has a recipe
- Copper block recipes are now consistent
- Bees no longer throw a rare crash relating to their path finder
- Spectating entities no longer the server
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| Et_Futurum_Requiem-2.5.1+nomixin.jar | Unknown | 3.87 MiB |
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:o56psTwz:NUSiJv7c"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:o56psTwz:NUSiJv7c"
}

