Tags
Creators
Details
Licensed ARR
Published 6 months ago
Updated last month
All versions
1.0.17
Release
MuteEssentials 1.0.17last month 17
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
Platforms
Paper
Purpur
Changes
TL;DR for admins
- No manual changes required
- No permission that worked before loses its effect
- Extensive fixes around rollback and containers
- Several duplication and exploit paths closed
- New teleport and toggle commands
- Data and configuration are written atomically now
Compatibility
- Paper 26.3 is cleared for use
- Full in-game testing on 26.3 is still running, and Paper itself has no stable 26.3 build yet. If something behaves oddly there, please report it on Discord: https://discord.gg/7ZUdU7eXzb
- Everything from 1.21 upwards stays supported, 26.1 and 26.2 are unchanged
Critical fixes
- Fixed: Containers came back empty from a rollback. The block was restored, the items were written into a snapshot that was thrown away right afterwards. Every chest, barrel, furnace and shulker box was affected
- Fixed: Container protection failed open. A lock database that could not answer read as "this block is not locked", so every locked chest on the server was free to open and break. Turning the ChestLock module off in the admin menu was enough to cause it
- Fixed:
/invseecould duplicate and delete items. The view was written back in full on close, so anything the player picked up in the meantime was erased and anything they dropped came back - Fixed: Any team member could wreck the team. Deleting all claims, removing trusted players and flipping claim flags were possible straight from the menu, while the same actions on the command line required leader or officer
- Fixed: A menu whose title an operator had restyled stopped cancelling clicks, which turned every decorative item in it into a free item. Menus are identified by their inventory holder now
- Fixed: TNT and fire could not be rolled back by player. Both were filed under
#tntand#fire, so a rollback of the griefer undid none of it. They are attributed to whoever lit them now - Fixed: A theft out of a container can be rolled back. The before and after contents were recorded all along and never used
- Fixed: Paintings, item frames, bone meal, trees and sponges are logged and restored. None of them could be undone before
- Fixed: Rolling back a broken container no longer duplicates its contents, and the drops next to it are cleared with it
- Fixed: An action another plugin cancelled is no longer written to the log, so a rollback stopped deleting blocks that were never placed
- Fixed:
/mues update downloadno longer overwrites the jar the server is running from. The download is staged in the update folder and applied on the next restart, the backup of the replaced version is kept, and the source is read again for every download instead of reusing what an earlier check happened to see - Fixed: Messages arrive in the language of whoever reads them. Around a hundred of them always came in the server default
- Fixed:
Home.Permission,TPA.Permission,Msg.Permission,ClanSystem.PermissionandUpdate.Permissionare asked now. They were documented and configurable but never checked. All four player nodes ship withdefault: true, so nothing changes until you revoke them
New
- New:
/tpahere <player>asks a player to teleport to you, the counterpart to/tpa - New:
/tptoggle [on|off]blocks incoming teleport requests,/msgtoggle [on|off]blocks incoming private messages, replies included. Staff still get through withmuteessentials.tptoggle.bypassandmuteessentials.msgtoggle.bypass - New: The first operator who joins after an update is told about it and gets a link to the changelog and to the support Discord
More fixes
- Fixed: Block log: double chests, pistons, beds and doors, crops on farmland, rollback order, rollbacks that found nothing after a rename, a rollback that could wedge itself,
/bl purge 0, andBlockLog.RetentionDaysinstead of a fixed thirty days - Fixed: AntiVPN checked nothing. The default API address had moved and answered with a permanent redirect, which the HTTP client does not follow, so every lookup failed silently and no connection was ever blocked. Existing configurations are corrected on the first start
- Fixed: Chest locks: a lock left behind by a container that disappeared without a break event, the trusted list of a double chest, and a lock that silently failed to be written
- Fixed: Auction house: duplicating an item when cancelling a listing, losing one when a listing failed, and prompts that swallowed the next chat message a player sent
- Fixed: Moderation: a ban kick replaced by the version warning,
/muteon a nickname missing the real account, an automatic ban that wiped the warnings it was based on,/custombanreading a duration as a reason, and/maintenance onkicking the admin who ran it - Fixed: Vanish: advancements,
/vanishmessages, tab completion and client detection all revealed vanished or nicked players - Fixed: Economy: cents rounding and a stale connection in MySQL, and a balance cache that takes the sidebar off the database
- Fixed: Data: configuration and data files are written atomically, offline messages survive a quick relog, a kit is only handed out once its cooldown is stored, and a config upgrade that cannot be written says so
- Fixed: Config: every command can be switched off now, twenty-three had no entry at all, and
General.BlockUnknownCommandscan be turned off on a proxy network - Fixed: Smaller things in
/stats,/speed,/team unclaim,/mues update,/unbantab completion, the scoreboard after a reload, and a few leaks that grew with the server's uptime
Changed behaviour
- Note: Container actions are refused while the lock database is unreachable; the protection stays closed rather than open
- Note: A kit is refused instead of handed out when its cooldown cannot be stored
- Note: With MySQL across several servers a balance can be up to three seconds old in the sidebar
- Note: Turn
General.BlockUnknownCommandsoff on a proxy network - Note: The four player permissions ship with
default: true, so revoke them explicitly if you want to restrict them
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:cQ9DQX8C"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:twz6Fcn3:cQ9DQX8C"
}

