Tags
Creators
Details
1.0.2
Compatibility
Required content
Changes
-
Lucky Perms connectability added, and more!
-
Command rewards (your claim blocks / LuckPerms use case) Any
/servershopentry can now run console commands on purchase. Inconfig/viper-economy/prices.json:
"minecraft:nether_star": {
"category": "rewards",
"stack": 1,
"unit_buy": 5000,
"unit_sell": 0,
"give_item": false,
"commands": ["claimblocks {player} add 1000"]
}
"minecraft:enchanted_golden_apple": {
"category": "rewards",
"stack": 1,
"unit_buy": 10000,
"unit_sell": 0,
"give_item": false,
"commands": ["lp user {player} parent add vip"]
}
Plus a "rewards" category (display_item: minecraft:nether_star). {player} becomes the buyer's name, commands run as console, give_item: false means perks only with no physical item, and unit_buy: 0 disables a reward without deleting it. Reward items show a ⚡ Grants perks on purchase lore line. Works from both the GUI and /buy.
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:CbHYhwPO:VQCIQ189"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CbHYhwPO:VQCIQ189"
}

