Tags
Creators
Details
2.0.0
Compatibility
Changes
https://github.com/Happyuky7/SEPARE-WORLD-ITEMS/releases/tag/2.0.0
2.0.0
This is a major rewrite/recode release.
Full Changelog: https://github.com/Happyuky7/SEPARE-WORLD-ITEMS/compare/1.2.26...Pre-Update-2.0.0-DEV-105-TEST-2
Discord: https://discord.gg/3EebYUyeUX
Download Directories:
Highlights
- Folia support
- WorldGuard integration (BETA)
- Multiple storage backends (YAML / SQLite / MySQL / MariaDB / MongoDB / Redis)
- Any → Any migration between backends
- Backups (scheduled + manual)
- Change-logs (audit snapshots) with minimum 30 days retention
- Critical actions confirmation workflow (
confirm <code>/cancel) - Updated translations / multi-language support
New
- Storage system rewrite with selectable backends.
- Backup system:
- scheduled backups
- manual backups (
/swi backup) - optional remote snapshot export for DB backends
- Change-logs (audit): snapshot logs + retention cleanup.
- Config improvements for SQL:
storage.sql.jdbc-urlsupport- or host/port/database/parameters fields
Fixes / Stability
- WorldGuard region switching only applies inside configured regions (ignores
__global__). - Reduced risk of inventory overwrite in rapid world/region transitions by serializing per-player switching.
- Improved stability for remote DB backends via async operations (recommended for remote MySQL/MariaDB).
Commands
/separeworlditems(aliases:/swi,/separeitems)- New confirmation flow for critical actions:
/swi confirm <code>/swi cancel
Notes / Warnings
- YAML and SQLite are the most stable options.
- MySQL/MariaDB/MongoDB/Redis are BETA in 2.0.0.
- WorldGuard region switching is BETA: test before production and keep backups.
Upgrade notes
- This is a major update: make a full server backup before upgrading.
- If you have an old config, regenerate it and re-apply settings.
- If you plan to migrate storage, do a manual backup first.
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:lpniJhfY:B11UNT3H"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lpniJhfY:B11UNT3H"
}

