All versions
1.4-Release
Release
Release 1.44 months ago 80
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
Platforms
Bukkit
Paper
Spigot
Changes
Release 1.4
1. Points Pay System
- The recycling point payment system has been added; now by typing /trash pay (player) (amount) you can pay recycling points to other people.
2. Coupons
- Coupons have been added. Administrators with the trash.admin permission can now use
/trash coupon create (number of points)to create a points coupon with the specified amount. Claiming it is as simple as right-clicking. These coupons can then be placed in crates or wherever you like. Regular users with the trash.trash permission can also use/trash coupon withdraw (number of points)to convert points in their account into a coupon, which they can then sell or use as they wish.
3. Give Points (ONLY ADMINISTRATORS)
- Now admins with the trash.admin permission can give recycling points to users or themselves with the command
/trash givepoints (player) (amount).
4. Stats
- Now with /trash stats you can see your statistics, that is, you can see your total items destroyed, your points, your eco rank (still to be fixed, coming soon in a new update), the collective server goal and your active boosters.
5. Multipliers
- Multipliers are based on ranges; depending on your range, you'll have a different multiplier. Configuring them is very easy. In your config.yml file, go to the multipliers section, and you'll see the default multipliers. You can change their names, values, and everything else. Then, to assign a multiplier to a range, you need to grant the range the following permission: trash.multiplier.(multiplier name)
If you have any questions, bugs, or problems with the plugin, you can contact me in either Spanish or English through this website
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:aldSLIFU:NgchpbV5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aldSLIFU:NgchpbV5"
}

