Links
Tags
Creators
Details
All versions
5.0.0
Release
WorldListTrashCan 5.0.02 years ago 51
Compatibility
Minecraft: Java Edition
1.21
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
5.0.0
- Fix the bug in Paper and Folia where dense entity restrictions cannot restrict non live entities. Dense cleaning fully supports clearing dead entities (such as various ships, mining carts, armor frames, and even arrows shot by skeletons on the ground)
- Support RGB color anywhere in the plugin, remade all places with RGB color on the default language file for a more aesthetically pleasing appearance
- Compatibility has been made on lower versions of servers that do not support RGB. The plugin comes with language files specific to higher and lower versions, and will automatically switch based on the server version (please delete the original language files for updates)
- If the server is a Paper or Folia server, the plugin will automatically determine and adapt to better APIs to improve the plugin's response speed
- Optimize various algorithms (such as dense entity cleaning) and decouple them appropriately
- Attempt to fix the issue of the plugin not displaying colors properly on the console (there are many functions in the plugin body that cannot be checked one by one, and there are still residues)
- Add default permissions: WorldTrashCan Main, If you ban this permission, players will not be able to create a world trash can. If you are only interested in the powerful features of this plugin (except for the world trash can)
- Abandoned the step of the server owner using the configuration file to determine whether it is a Folia server on their own, and the plugin will compare the API class names that the server can use to determine the server characteristics on its own (this supports all Folia and paper branches)
- Fix the bug where the plugin works on the mohist end, causing players to be unable to chat normally due to the anti swipe system that comes with the plugin registering chat events deleted on the mohist end
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:nILG1dtG:r4IQgU8n"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nILG1dtG:r4IQgU8n"
}

