7.1.4
Compatibility
Changes
🚀 OEssentials v7.1.4 is OUT NOW!
@everyone
A new OEssentials update is officially available for Paper & Folia 1.21.x!
This release focuses on stability, command compatibility, module isolation, and fixing feature toggles.
🔥 Major Fixes
✅ PacketEvents is no longer required for startup! Custom TAB lists and nametags now fall back to the Bukkit API when PacketEvents is missing.
✅ Fixed vanilla and third-party commands disappearing! Disabling OEssentials features will no longer accidentally remove commands from Minecraft or other plugins.
✅ Improved module stability! If an optional module fails to initialize, the rest of OEssentials continues running.
✅ Better startup diagnostics! Failed modules are clearly displayed in the console with error reasons.
⚙️ Command System Improvements
🔹 Disabled commands are now completely unregistered, including aliases, tab completion, namespaced commands and help entries.
🔹 Vanilla commands such as /tp, /gamemode, /kill and /bossbar can safely be restored by disabling their OEssentials equivalents.
🔹 Command toggles apply immediately without a restart!
🛠️ Feature Toggle Fixes
Fixed disabled features leaving commands or listeners active:
• 🏠 Homes & Player Warps
• 🎒 Player Vaults
• 🛒 Shop & Help
• 🐲 Mob Management
• 🚀 Jump Pads & Portals
• 🎁 Playtime Rewards
• 💬 Chat Channels
• 🌍 Random Teleport
• 🔧 Maintenance Mode
Disabled features now properly respect their configuration settings.
🧩 Internal Improvements
Updated MinecraftModulith to v0.5.0, adding support for optional modules and ordering-only dependencies.
📥 DOWNLOAD THE UPDATE
📌 Important: Changes to settings.yml feature switches require a server restart. Command toggles take effect immediately.
💙 Thank you for using OEssentials and supporting Oreo Studios!
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:mW41qQ0T:yPExCjzS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mW41qQ0T:yPExCjzS"
}

