Tags
Creators
Details
All versions
4.0.0.8
Release
zAuctionHouse 4.0.0.84 months ago 1,652
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
Platforms
Folia
Paper
Purpur
Spigot
Changes
- Fixed Critical item duplication in multi-server (Redis) setups - when a player removed a selling item via the selling inventory, the item was correctly given to the player and marked as
DELETEDin the database, but other servers received a genericLISTEDremoval message and incorrectly recreated the item in theirEXPIREDcache, allowing it to be claimed a second time on another server - Fixed
ItemRepository.select(int id)not filteringDELETEDitems - single-item database queries returned items already marked asDELETED, while the bulkselect()method correctly excluded them. This allowed the RedisItemRemovedListenerto reload deleted items and re-add them to cache - Added
destinationStorageTypeto cluster bridgeremoveItemmethod - theItemRemovedMessagenow includes the exact destination storage type (DELETEDorEXPIRED) so other servers know exactly what happened instead of guessing. Backward compatible via adefaultmethod onAuctionClusterBridge - Fixed
ItemRemovedListener(Redis addon) rewritten with defense-in-depth - uses the explicit destination from the message first, falls back to database state verification, and never blindly assumes an item should go toEXPIRED - Fixed
CreateOptionsMigrationfailing on MySQL witherrno: 150 "Foreign key constraint is incorrectly formed"- theplayer_unique_idcolumn useduuid()type which could produce a different collation than the existingplayerstable (especially on MySQL 8.0+ with changed default collation). Changed tostring(36)to match all other foreign key columns referencingplayers.unique_id
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:lVAWIzaG:C7SD1DxW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lVAWIzaG:C7SD1DxW"
}

