Tags
Creators
Details
Licensed MIT
Published last year
Updated 8 months ago
All versions
2.5.4
Release
PlayerAuctions 2.5.49 months ago 1,000
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
Platforms
Paper
Purpur
Spigot
Changes
Added - Broadcast Notifications System
-
Global Broadcast Notifications for auction events
- Broadcast when players list items for auction
- Broadcast when players purchase items
- Clickable "View Auction" link in listing broadcasts
- Beautiful hex-colored messages with emojis
-
BroadcastManager Service
- Centralized broadcast management
- Configurable broadcast ranges (GLOBAL, WORLD, NONE)
- Individual toggles for listing and purchase broadcasts
- Smart player name resolution for offline sellers
- World-based broadcasting support
Configuration Options
auction:
broadcast:
enabled: true # Master toggle
on-listing: true # Broadcast new listings
on-purchase: true # Broadcast purchases
range: GLOBAL # GLOBAL, WORLD, or NONE
Broadcast Messages
- Item Listed: Shows player, item name, quantity, and price with clickable link
- Item Purchased: Shows buyer, seller, item, quantity, and price
Technical Implementation
- Integrated BroadcastManager into PlayerAuction main class
- Broadcasts triggered from AuctionCommand (/ah sell)
- Broadcasts triggered from AuctionService (purchase completion)
- MiniMessage support for rich text formatting
- Click events for interactive messages
- Proper thread handling (main thread for Bukkit operations)
Benefits
- Server Activity: Players see active marketplace
- Price Discovery: Players learn market prices
- Engagement: Encourages trading and competition
- Transparency: All trades are visible to community
- Configurable: Can disable per feature or globally
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:Mp3J39aH:VvDFzuBS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Mp3J39aH:VvDFzuBS"
}

