Tags
Creators
Details
2860
Compatibility
Changes
Slimefun4Core — Build 2860
New Features
- Storage Migration System — Safer migration and handling of existing Slimefun storage data.
- Checkpoint System — Create verified recovery points before important data operations.
- Report System — In-game reporting with Discord integration and diagnostic information.
- Addon Services Upgrade — Improved addon management, syncing, updates and service handling.
- Addon GUI — Manage addons directly through the Slimefun Guide.
- Automatic Error Detection — Detect Slimefun/addon errors and generate useful diagnostic reports.
- Improved Error Handling — Better error detection, logging and failure handling.
Bug Fixes
- Fixed / working on multiple reported issues and internal errors.
- Fixed
EXPLOSIVE_BOWentity errors. - Fixed Slimefun storage and backup-related errors.
- Fixed Backpack lore
NullPointerExceptionissues. - Fixed addon and configuration warnings.
- Fixed Discord addon-list formatting issues.
- Fixed broken characters appearing in log output.
- More bug fixes and internal improvements.
Known Issues
- Addon downloads currently do not verify JAR SHA/signatures.
- Discord webhook delivery may fail without confirming successful delivery.
Special Thanks
A special thanks to everyone who helped test, report issues, provide feedback, and follow the development of Slimefun4Core throughout this development cycle.
Special thanks to:
- m0iy_0
- dido__kf
- graxe_1h7
- pasindunayanajith_
- thefryguy_
Your bug reports, testing, feedback, and patience have helped make this release more stable and easier to maintain.
Thank you for supporting Slimefun4Core.
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:Fz9hstnG:M14FNoN1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Fz9hstnG:M14FNoN1"
}

