Tags
Creators
Details
1.0-RELEASE
Compatibility
Changes
First release.
133 commands across teleporting, homes, warps, spawns, kits, economy, moderation, chat, inventories, world control and information.
Every command can be switched off. commands.yml carries one entry per command with its aliases, permission node, cooldown and price. A command set to enabled: false is never registered with the server, so it disappears from /help and from tab completion and gives its name back - a name that vanilla owned, such as /give or /list, returns to vanilla.
Two-way EssentialsX migration. /serversystem migrate here reads an existing installation: balances, homes, warps, spawns, jails, kits, worth prices, nicknames, ignore lists, mail, active mutes and the vanilla ban list. Item names from before the 1.13 flattening are understood, so a worth.yml that has been in use for years comes across whole. /serversystem migrate to essentials writes all of it back out in Essentials' own layout. Nothing is deleted on either side and running it twice updates rather than doubles.
Player data in a database. SQLite with no setup at all, or MySQL when several servers share one set of balances and punishments. Online players are held in memory, so no command waits on a query, and /baltop is one ORDER BY rather than a walk over thirty thousand files.
Economy on BigDecimal with a transaction log, offered to other plugins through Vault.
Folia. Every task goes through the region scheduler and teleports are asynchronous.
Per-player languages. Players are served in their client's language without any configuration. English, German and French are included; further files drop into plugins/ServerSystem/lang.
Tested on Paper 1.21.11 with Java 21: all 133 commands were run against a live server, 74 from the console and the rest through a connected client, with no exceptions. The migration was checked against a real EssentialsX 2.22 installation.
Requires 1.21.4 or newer - /heal uses an attribute that was renamed in 1.21.3.
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:3jGmDvjD:72JejmMv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3jGmDvjD:72JejmMv"
}

