5.0-SNAPSHOT
Compatibility
Changes
● ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
OreoEssentials — Update v4.4
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🌐 WEB PANEL — REBUILT FROM SCRATCH
The OreoStudios web panel has been completely redesigned and rewritten. New layout, better performance, and a ton of new features.
────────────────────────────────────── ⚙️ CONFIG EDITOR (NEW FEATURE) ────────────────────────────────────── You can now manage all your OreoEssentials config files directly from the web panel — no more SSH, no more FTP.
Supported files: • config.yml • chat-format.yml • tab.yml • clearlag.yml • settings.yml • scoreboard.yml • afk.yml • maintenance.yml • rtp.yml • craft-actions.yml • join-quit-messages.yml • playervaults.yml • playerwarps.yml • dailyrewards.yml
Features: [+] Visual form editor — edit settings through a clean UI [+] Raw YAML editor — full text editing with live validation [+] Push to Plugin — send config changes live via RabbitMQ (no server restart required) [+] Fetch from Plugin — pull current config files from your running server directly into the panel [+] Auto-save to database — configs are stored server-side
────────────────────────────────────── 🛠️BUG FIXES ────────────────────────────────────── [] Fixed internal server error when saving config files [] Fixed RabbitMQ connection status showing incorrect state [] Fixed panel crash on load (null element errors) [] Fixed push failing silently when plugin was online [] Fixed YAML parse error when config root was not a map [] Stability improvements to the AMQP listener
────────────────────────────────────── ➕ OTHER CHANGES ────────────────────────────────────── [+] Servers can now be deleted from the dashboard [+] Improved error messages across the panel [+] Better RabbitMQ reconnection handling
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:GL6bPnaP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mW41qQ0T:GL6bPnaP"
}

