Tags
Creators
Details
V2.2.1
Compatibility
Changes
A fix for Folia servers. If you run Paper or Spigot, nothing in this release changes anything for you and you can update whenever it suits you. If you run Folia, this one is worth taking.
The Folia support shipped in 2.2.0 left two windows open where a player disconnecting at the wrong moment could make an item, or a payment, disappear. Both are closed.
Items lost on a disconnection
When a player cancelled one of their own auctions, bought an item, took back an expired item or put one up for sale, the item was removed from the database before being handed over. If the player disconnected during that short moment, the item was never handed over and was gone for good.
The operation is now undone cleanly instead: the auction goes back on the market, an expired item goes back to the expired items, and an item taken for a sale that could not be saved is placed in its seller's expired items. The player finds their item again when they log back in, and every case is logged to the console.
Sales blocked by the duplication protection
After such a disconnection, the item's signature stayed stuck in the anti-duplication filter. From then on nobody could put a visually identical item up for sale, server-wide, until the next restart. The signature is now released in every case.
Pending payments in XP and LEVEL mode
Payments held for a seller who was offline were credited from the wrong thread under Folia, which Folia does not allow. They now go through the player's own region thread. A payment that does not go through stays owed to the player instead of being cleared.
Updating
Replace the jar and restart. No configuration change, no database change, and nothing for your players to do.
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:xvzE8bYg:EpAwPwKW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xvzE8bYg:EpAwPwKW"
}

