Tags
Creators
Details
1.21.11
Compatibility
Changes
How it works:
When a player joins, they are automatically added to the mod's database (ourdiscount_players.txt).
When someone interacts with a cured villager, the discount is applied to everyone in that database.
Offline support: Unlike older versions, the original player does not need to be online. Since we store the UUIDs, friends who are offline (or haven't joined yet) will still get the discount.
Great for SMPs to avoid repetitive curing for every single member.
Commands (Console only):
/ourdiscount check <name> - Checks if a player has a discount active on nearby villagers (works for offline players too).
/ourdiscount reapply - Forces the discount update on all loaded villagers globally.
Contact: Discord: lukysgaming
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:NkCzh5Pg:AWVHgvZJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NkCzh5Pg:AWVHgvZJ"
}

