Tags
Creators
Details
Licensed ARR
Published 6 months ago
Updated last month
All versions
1.0.18
Release
MuteEssentials 1.0.18last month 57
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
Platforms
Paper
Purpur
Changes
TL;DR for admins
- Recommended for everyone, and especially for servers on 1.0.17
- No manual changes required, your settings are carried over
- Commands you had switched off stay switched off
- A duplication path in
/bl deathrestoreis closed - The auto updater goes straight from 1.0.16 to 1.0.18
Critical fixes
- Switched-off commands came back on after 1.0.17:
/enderchest,/staffchatand/blocklogwere renamed toec,scandblin the configuration, and the old entries were no longer read: Whoever had turned one of them off had it back on. The update moves the setting and any custom aliases to the new names, and also repairs servers that are already on 1.0.17 - The first start after an auto update skipped the new settings: The new configuration keys and messages only arrived after a second restart, and some defaults were missing until then. They are applied on the first start now
- An update through the updater of 1.0.16 could be undone later: On Paper 1.21 the old updater wrote the new version into Paper's working copy instead of the plugins folder, so the server could fall back to the old version once Paper rebuilt that copy. The new version is put into the plugins folder on the next shutdown
/bl deathrestorecould hand out the same inventory twice: Two quick calls both got the items before the entry was removed. The entry is claimed first now- Muted players could still write to offline players with
/msg: The mute check covered online recipients only
Fixes
- AntiVPN no longer slows down every join when its check service is down. A failure is remembered for a minute, three failures in a row pause the checks for five minutes, and every request has a hard deadline. Local, CGNAT and IPv6 link-local addresses are recognised properly, a
RiskScoreThresholdof 0 no longer blocks everyone, and the cache is capped - Shared data in MySQL is written in the right order. Two saves in quick succession could land the other way round
- The updater only uses https for the update source and the download, and the file has to match the published checksum
- Safer MySQL defaults: an encrypted connection where available and a dedicated user instead of
root. Existing setups are only changed while MySQL is switched off. With MySQL on, the start warns about unencrypted connections,rootand an empty password instead - Auction prices have to be real numbers,
/reporthas a cooldown, and the claim index is rebuilt on/mues reload
Full changelog: https://wiki.mutebefehl.de/docs/muteessentials/changelog
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:twz6Fcn3:d7ijUZeF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:twz6Fcn3:d7ijUZeF"
}

