Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated 2 years ago
All versions
v0.3.0-beta
Beta
Slimefun Essentials v0.3.0-beta The Rewrite!4 years ago 483
Compatibility
Minecraft: Java Edition
1.19.4
Platform
Fabric
Supported environments
Client-side
Changes
Update
This version of Slimefun Essentials is a Complete Rewrite since v0.2.4!
Changes
- Updated to 1.19.4
- Rewrote how Slimefun Essentials loads Recipes
- Almost Everything is now data driven allowing for a much broader support for custom per server addons
- The big data file has been split into three directories, the file name is based on the addon it adds support for e.g. 'slimefun.json'
slimefun/items, for serialized slimefun item stacks, can be generated by Slimefun Server Essentialsslimefun/labels, for any custom textures & tooltips to label recipes, e.g. The Sun "Requires Sunlight" for Solar Panelsslimefun/categories, for serialized categories, can be generated by Slimefun Server Essentials
- Rewrote Support for EMI
- Rewrote Config System (Now has a Keybind to open Config & Addons is a list)
- Fixed UTF symbols in Items
- Added Support for JEI & REI
- Added Automatic Addon Fetching
- Requires Slimefun Server Essentials on the Server
- Added Custom Block Texture Framework
- Until a PR gets merged for Core Slimefun, this will not be available as Slimefun Server Essentials requires 2 new Events
- Removed Built-in Support for all previously supported Addons, will return in the future! (Hopefully Soon!)
Full Changelog
https://github.com/JustAHuman-xD/SlimefunEssentials/commits/rewrite
Optional dependencies
Unavailable version
Unavailable version
Unavailable version
Unavailable version
Unavailable version
Unavailable version
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:AXC3ZOt4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:C0neDqXC:AXC3ZOt4"
}

