Tags
Creators
Details
5.7+build.3288
Compatibility
Changes
5.7 build 3288
This release contains bugfixes to build 3265 and a new theme.
Special thanks to Kopo, Leolebleis & Guinness_Akihiko for contributions to this update
Change log
Website
- Improved readability of World Pie on servers that have over 7 worlds
- Improved readability of Server Pie on networks that have over 7 servers
- Moved Performance graph loading to Web Worker (async threading in browsers) - This should improve rendering times slightly
- Fixed issue where Join Address Groups would reset when using HTTPS
- Fixed a couple of instances where Trend was not properly showing
- Fixed 'showPlayersOnline is not defined' when viewing network page on networks with multiple Proxy servers
- Fixed a bug with Change history floating on top of the Save button in Theme Editor when using Night mode.
- Fixed CUSTOM locale defaulting to Chinese locale for time/date/country localization due to "Best match" in browser matching.
- Fixed Swagger documentation not showing
- Fixed 'New player retention' label in Server overview
- Fixed typo in a locale key
- Fixed Low TPS Insights showing entities instead of CPU
- Leolebleis fixed reverse-proxy https address not being recognized as correct address
Fabric
Kopo updated Fabric to use Mojang mappings (Tested with 1.12.9-1.12.11)
Themes
Added solarized theme based on https://github.com/altercation/solarized
Config
- Possibly fixed a race condition that caused server identity to be reset, creating duplicate servers when server was shut down during Database patching
- Fixed trailing comments removing part of config setting value.
- Fixed some config changes being applied every time
Locale
- Guinness_Akihiko updated KO locale
Other
- Builds now require JDK 25 for switch to Mojang mappings.
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:wJQfHhxh:sTqNTnSr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wJQfHhxh:sTqNTnSr"
}

