1.0.2
Compatibility
Changes
What’s New? Trash Summary Added Players now receive a clean disposal summary after closing the trash menu. The summary shows exactly what was disposed of and the total amount of items removed.
Protected Item Improvements Blocked items are now safer and more reliable. MythicTrash can check protected items by:
• Material type • Item display name • Item lore • Coloured text using & color codes • Plain text fallback, even if colours are stripped
If a blocked item is placed into the trash menu, it will be returned to the player instead of being deleted.
Admin Bypass Permission A bypass permission is available for server owners who intentionally want staff/admins to be able to dispose of protected items.
[code]mythictrash.bypass.blockeditems[/code]
Please note: OP players usually receive all permissions automatically, so they may bypass blocked item protection unless this permission is negated through your permissions plugin.
Fully Configurable GUI The trash GUI is now much more customizable. You can configure:
• GUI title • GUI size • Decorative/protected button slots • Button materials • Button names • Button lore • Button glow • Custom Model Data • Confirm menu buttons • Cancel/confirm button slots
Confirmation Menu Improvements The confirm disposal menu can now be customized separately, including filler items, confirm button, cancel button, materials, names, lore, glow, and Custom Model Data.
Auto Config Updater MythicTrash now includes an automatic config updater. When new config options are added in future updates, the plugin can add missing paths without wiping your existing settings.
A backup is created before config changes are applied.
Fixes
• Fixed blocked lore/name checks not matching properly with color codes. • Fixed protected items being deleted when mixed with normal trash items. • Fixed disposal summary formatting issue. • Fixed trash logic being split between listener and manager. • Improved final safety checks before items are permanently deleted.
Recommended
After updating, restart your server and check your config for the new GUI and blocked item options.
If you are testing protected items while OP, remember that OP players may automatically have the bypass permission.
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:40jnsAKM:ytOti9iq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:40jnsAKM:ytOti9iq"
}

