Tags
Creators
Details
26.10
Compatibility
Changes
AuctionHouse Changelog
Plugin: AuctionHouse (VIP Auctions) by VIP Plugins
Jar: AH-26.10.jar
Minecraft: Paper / Folia / ShreddedPaper 1.21.x
Java: 21
26.10
First monthly release. Item frames stay, and booths can now be glass cases or armor stands, with optional holograms.
Displays
- Glass cases show a floating, spinning item (
ItemDisplay) - Armor stands wear armor or hold other items
- Optional
TextDisplayholograms on frames, glass, and stands - Pair with a sign, a hologram, or both:
/auction connect <buy|bid> [frame|glass|stand] [sign|holo|both] - Click a booth to buy or bid
- Spin speed and hologram height are configurable
displays.unique-listingskeeps the same listing off more than one booth at a time
Experimental (off by default)
plugins/AuctionHouse/experimental.json
rentable-booths— players can rent a connected booth so only their listings show therestand-full-armor— rented stands can display a full armor set
Leave both false unless you want to try rent.
Fixes
- GUI footer no longer writes past the inventory when
gui.rowsis below 6 NaN, infinity, and non-finite prices are rejected- Listing fees are withdrawn before the item is taken
- Item-currency withdraw and deposit now use the same rounded amount
/auction reloadrestarts booth refresh and glass rotation with the new timings- Expired listings and collections are safer on Folia
- Update checker asks Modrinth (
vip-auctions) first, then Spigot (137988)
Config notes
After updating, run /auction reload or restart once so new keys are filled in. Existing comments are kept.
If you still have an old displays.hologram-offset: 1.9, use the new per-type offsets:
- frames / glass:
0.85 - armor stands:
2.55
Set the Spigot and Modrinth version numbers to 26.10 so the update checker matches the jar.
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:M57HTW58:i5YITg2T"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:M57HTW58:i5YITg2T"
}

