1.0.0
Compatibility
Required content
Changes

Pixel Loot Changelog - 1.1 Release
New Additions (+)
- Dynamic Reward System: Implemented a new reward system triggered by winning raids.
- Added /pixelloot givereward command.
- Added new configurations for raids in config.yml
- Added new configurable messages in lang.yml
Fixes and Balances (=)
- Optimized Reward Distribution: Rewrote percentage calculator on reward checks.
Removals (-)
- None
/Pixelloot givereward command functions as way server admins can give rewards from the config to players.
Usage: /Pixelloot givereward {rewardtype} {player} {rewardID}
the permission pixelloot.command.givereward is required to use this command.
VAULT IS NEEDED FOR PERMISSIONS TO WORK!
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:LLnUOqzn:qu4Hm1Kr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LLnUOqzn:qu4Hm1Kr"
}

