Tags
Creators
Details
2.0.0
Compatibility
Changes
Customers 2.0.0 release - Architectury, Performance, Fixes, & Tightening Up
Important: New Required Dependency
Customers now requires Architectury API.
Architectury allows Customers to share more code across Minecraft versions and mod loaders while supporting:
- NeoForge - Minecraft 1.21.1 & 1.21.11
- Fabric - Minecraft 1.20.1, 1.21.1, & 1.21.11
- Forge - Minecraft 1.20.1
Install the Architectury API version matching your Minecraft version and loader.
New Configuration and Behavior
- Quick Sell is now enabled by default.
- Added the Customers are Invulnerable option, enabled by default.
- Protects customers, customer pets, and suppliers from all damage.
- Includes attacks, falls, fire, lava, drowning, lightning, and other damage sources.
- Customers and suppliers no longer turn into zombie villagers. If killed while vulnerable, they die normally.
- Vulnerable customers give up and leave if damaged while buying.
- Customers are healed when they enter the buying state.
- Suppliers now leave when all their trades are out of stock instead of waiting until nighttime.
- Suppliers announce when they are out of stock before leaving.
Performance Improvements
- Added efficient caches for Customer Spawners, Leaderboards, and customer counter positions.
- Removed repeated world scans for nearby spawners and customers.
- Pickup Counters now reuse cached nearby spawner results until the cache changes.
- Customer Spawners now cache counter locations and invalidate them only when relevant blocks change.
- Leaderboard lookups are cached and refreshed only when the leaderboard cache changes.
- Empty Pickup Counters skip unnecessary periodic validation work.
- Pickup Counter validation is distributed across ticks instead of every counter running on the same tick.
- Reduced tick spikes caused by active customers, Pickup Counters, Leaderboards, and newly spawned customer pathfinding.
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:wPxoHrff:5dFrMP3h"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wPxoHrff:5dFrMP3h"
}

