All versions
1.2.0.2
Release
StormPatrikCZ’s autosell chest 1.2.0.2last month 34
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
AutoSell - Changelog
Version 1.2.0.2
Added
- Money now arrives even when you're offline - If your chest sells while you're away, the earnings are waiting for you when you log back in (previously the items were sold but the money was lost)
- Correct update checks - The plugin now knows its own version, so it no longer announces a non-existent update on every startup
Changed
- Smoother holograms - Chest holograms now update without flickering
- Fairer
/autosell sell- The command now requires permission and respects the distance set in the config /autosell listis now private - Regular players see only their own chests, the full list stays admin-only/autosell pricenow actually saves - Changed prices take effect immediately and survive a restart- More items sellable out of the box - Fixed several item names in
sellables.ymlthat didn't match the current Minecraft version - Your translation edits now apply - Edits to the language files in the plugin folder are actually used instead of being ignored
Fixed
- Double chests no longer sell twice per cycle - Linked chests are now processed as one, as intended
- Double-chest holograms no longer duplicate
- Holograms no longer disappear when the chest owner logs out
- Chunk loading no longer deletes holograms belonging to other plugins
- Upgrade menu no longer breaks on a typo in the config
- Upgrade GUI no longer blocks villagers, enchanting table and anvil - inventory clicks are cancelled only while the player actually has the upgrade GUI open (previously any click in the top inventory of any GUI was cancelled, so enchanted items couldn't be taken out, villager trades and anvil were blocked)
- Shift-click into upgrade GUI no longer possible
- More stable startup when multiple old plugin files are present
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:yRNa2BNZ:9G3bSeAt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yRNa2BNZ:9G3bSeAt"
}
