Tags
Creators
Details
1.1-RELEASE
Compatibility
Changes
Changed
- Removed the
gc-monitormodule. It listened for garbage-collection notifications and warned about long pauses, which only ever caught one cause of a slow tick and put a JMX listener on every collector bean to do it. Watching a server for lag belongs in/lagg tps,/lagg performanceand the samplers, which report on demand instead of writing into the log on their own. - The plugin is now called ClearLAGGG. The command stays
/lagg, and/clearlagand/clearlaggkeep working as aliases. The data folder moves fromplugins/Clearlaggtoplugins/ClearLAGGG, and the PlaceholderAPI placeholders change from%clearlagg_...%to%clearlaggg_...%. - Removed
/lagg gc. Forcing collection throughSystem.gc()is only a hint to the JVM, can be turned off with-XX:+DisableExplicitGC, and usually performs worse than letting the collector run on its own schedule. Thegc-monitormodule is unaffected and still reports long GC pauses. - The
tps-metersection no longer ships an enabled trigger. Previously the bundledcritical-tpstrigger ran asaycommand, which broadcast a TPS warning to every player on the server whenever the server dipped below 15 TPS. Triggers are now opt-in. - ClearLAGGG is now open source under the GNU General Public License v3.0. Source: https://codeberg.org/LucasTHCR/ClearLAGGG
- Every player-facing text now comes from
lang/messages_<language>.yml. The clear and kill-mobs broadcasts, the spawner, mob-egg and breeding denial messages, the GC pause warning and the halt/resume broadcasts used to be read fromconfig.yml, which only ever held English. Reword them in the language file from now on; the correspondingconfig.ymlkeys are gone.
Fixed
- Output is no longer half English on a translated server. With
settings.languageset to anything but English, the messages listed above stayed English while the rest of the plugin was translated. - Filled in fifteen messages that only existed in English and German. The other ten languages silently fell back to English for command usage, sampler results, profiler output and several errors.
- Messages added in a new version now resolve on servers that already have a
language file. Bukkit never overwrites an existing
lang/messages_*.yml, and the fallback pointed at the English file on disk, which was equally outdated, so a new key printed[Missing message: ...]. Defaults now come from the copy inside the jar, in the configured language. - PlaceholderAPI placeholders were lowercased using the system default locale,
which broke them on servers running a Turkish locale. They now use
Locale.ROOT.
Note for existing installs
Bukkit does not overwrite an existing config.yml on update. If you installed
1.0-RELEASE, remove the critical-tps entry under tps-meter.triggers in
plugins/ClearLAGGG/config.yml by hand and run /lagg reload, otherwise the
broadcast stays active.
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:zASITjNd:bCB2KAAn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zASITjNd:bCB2KAAn"
}

