Tags
Creators
Details
All versions
4.0.0.9
Release
zAuctionHouse 4.0.0.93 months ago 659
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
Platforms
Folia
Paper
Purpur
Spigot
Changes
- Fixed Sales history spamming
Item not found for log IDwarnings in console - logs migrated from V3 are created withitem_id = 0(no direct mapping to V4 items), causing the history service to log a warning for every V3 entry. The history now filters out logs with invalid item references at the SQL level - Added History configuration in
config.yml-history.max-entrieslimits the number of history entries displayed per player (default: 500, 0 = unlimited),history.expire-after-dayshides entries older than the specified number of days (default: 0 = never expire). Useful for servers with large transaction volumes to reduce database load and improve history loading times - Added Admin log management commands -
/ah admin logs purge <days>deletes all logs older than the specified number of days,/ah admin logs player <player>deletes all logs for a specific player,/ah admin logs clear-migrateddeletes all V3 migrated logs (entries withitem_id = 0). All operations run asynchronously and report the number of deleted entries - Fixed Ghost items in
/ah sellingon multi-server (Redis) setups - when a player removed a selling item on server #1 and switched to server #2, the item could still appear with "being purchased" lore and could not be removed, blocking selling slots. Three fixes applied: (1)ItemRemovedListenernow removes the item from in-memory storage immediately on message receipt instead of waiting for an async DB query, (2)RemoveServiceno longer restores the item status via Redis when the local removal already completed (preventing ghost items from reappearing as AVAILABLE on other servers after a cluster notification timeout), (3)getPlayerSellingItemsnow filters out items withDELETEDstatus as defense-in-depth - Changed Discord webhook
%expires_at%placeholder now outputs a Discord dynamic timestamp (<t:unix_seconds:f>) instead of a pre-formatted date string. Discord renders it in each viewer's own local timezone (e.g.12 June 2026 18:55), making it easier to read and timezone-agnostic. Items with no expiration still fall back to the formatted date - Added Per-item custom images for Discord webhooks - a new
custom-imagessection indiscord.ymllets you override the%item_image_url%for specific items. Each entry pairs arule(same format ascategories.yml/rules.yml:material,name,lore,custom-model-data,oraxen,itemsadder,nexo,mmoitems, etc.) with an image URL. The first matching rule wins; items matching no rule fall back to the material-baseditem-image-urlpattern. Ideal for custom items whose generic material does not represent the real item. Dominant color extraction caches the color per image URL so custom items sharing a material no longer collide
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:jHdZ0IM6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lVAWIzaG:jHdZ0IM6"
}

