1.16.0
Compatibility
Changes
EcoMOTD 1.16.0
Minecraft 1.16 — Nether Update
🆕 What's New in 1.16.0
This is a major milestone for EcoMOTD. Version 1.16.0 brings full RGB hex color support, unlocking millions of new color possibilities for your server's MOTD.
✅ Features
- MOTD Modes —
SINGLE,RANDOM(weighted),ROTATING(timer-based) - 5 Built-in Random MOTDs — Nether Update themed with full hex colors
- 3 Rotating MOTD Slots — Timer-based cycling
- Placeholder Support —
%online%,%max%,%date%,%time%,%tps%,%newline% - Fake Player Count — Display a custom online/max count
- Hide Player List — Remove the hover player list
- Custom Hover List — Set custom hover lines with hex color support
- Maintenance Mode — One toggle maintenance override
- Custom Server Icon —
DEFAULT,RANDOM, orCUSTOMpath - Response Cache — Cache responses to reduce ping overhead
- Admin Commands —
/ecomotd reload,/ecomotd info,/ecomotd preview - Tab Completion — Full tab complete support
- Debug Mode — Console logging per ping
*** NEW in 1.16.0 ***
Full RGB Hex Color Support
You can now use &#RRGGBB format anywhere in your MOTD lines, hover list, protocol name, and maintenance messages.
Example:
line1: "&#FF6B35&lMyServer &#FFD166Nether Update"
- Hex colors are automatically detected per client version
- Clients below 1.16 will have hex codes safely stripped — no errors, no broken text
- Standard
&color codes still work as normal
🔧 Changes from 1.15.0
- Added full
&#RRGGBBhex color rendering engine - Added automatic hex stripping for sub-1.16 clients
- Updated Spigot API target to
1.16.5 - Updated plugin
api-versionto1.16 - Refreshed default MOTD theme to Nether Update colors
- Protocol range updated to
735(1.16) —754(1.16.5)
⚙️ Compatibility
| Software | Supported |
|---|---|
| Bukkit | ✅ Yes |
| Spigot | ✅ Yes |
| Paper | ✅ Yes |
| Purpur | ✅ Yes |
⚠️ Notes
- Hex colors are fully supported on 1.16+ clients via
&#RRGGBB - Requires Java 8 or higher
- Protocol range:
735(1.16) —754(1.16.5)
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:elRJtGsV:gtoNto1p"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:elRJtGsV:gtoNto1p"
}

