Tags
Creators
Details
v0.3.2-beta
Compatibility
Changes
Changes
- Updated to 1.20.4
- Changed config option
"use_custom_textures"to"block_features"to better represent functionality - Updated README.md
- More backend work & cleanup, next update will probably be more of this
- Updated the config menu to gray out config options when dependencies are not met, updated some tooltips
- Reworked the lang file, and we now have a Chinese Simplified translation!
Additions
- Config
- Added config option
"recipe_features", this can be toggled on or off to enable compatibility with and of the recipe mods
- Added config option
- Rei
- Added tooltips
- Possibly improved some performance
- Fixed a problem with item comparing
- Jei
- Added tooltips
- Jade
- This was technically a part of an older release but I forgot about it!
- There is experimental support for Slimefun Items on Jade (Requires SlimefunServerEssentials on the Server and for
"block_features"to be enabled
Fixes
- Fixed REI functionality in general
- Fixed backwards filling arrow mismatched UV for emi
- Fixed timing of some displays and tooltips being incorrect
Other News
Slimefun is getting a recipe rewrite, this rewrite will make exporting/transferring the recipes to SlimefunEssentials exponentially easier. After the rewrite this mod and Slimefun Server Essentials will both need to be rewritten, as the rewrite to SF is progressed, you can track the progress here, I will be working on the rewrite for both this mod and the plugin. Don't worry, unlike the last rewrite this one won't be a huge overhaul, a lot of the api's and systems I have in place will be used so it will primarily be a big migration, this is a good thing!
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:C0neDqXC:zgvsOTdG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:C0neDqXC:zgvsOTdG"
}

