All versions
1.2
Release
StormPatrikCZ’s autosell chest 1.2last month 8
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
AutoSell - Changelog
Version 1.2
New features
- Upgrade GUI - New graphical interface for upgrading AutoSell chests with visual tier selection
- Shift + Right Click - Open upgrade GUI by shift-right-clicking on your AutoSell chest
Changed
- Direct tier upgrade - Players can now upgrade directly to any faster tier without having to upgrade sequentially through intermediate tiers
- Localized holograms - Hologram text is now fully translatable via language files (en.yml, cz.yml, sk.yml)
- Localized tier names - Tier names are now translatable (e.g., "Fast" → "Rychlý" in Czech)
- Improved translations - Czech and Slovak translations are now more accurate
Fixed
- Update notification - Admin update notification now only shows "downloaded" message when auto-download is enabled
- Duplicate language keys - Removed duplicate
hologram-enabledandhologram-disabledkeys in all language files (en.yml, cz.yml, sk.yml) - Duplicate sellables keys - Removed duplicate
MOSS_CARPET,AZALEA,FLOWERING_AZALEA, andSHULKER_BOXentries in sellables.yml - Language file warnings - Language files are now only saved on first run; subsequent startups skip saving if files already exist
- Upgrade GUI clicks - Fixed upgrade GUI items not being clickable by using persistent data container for item identification instead of unreliable title matching
- Localized tier names in GUI - Tier names in the upgrade GUI are now translated via language files (tiers.fast, tiers.faster, etc.)
- Localized item label in hologram - The "items" text in hologram is now translatable via hologram.item-label in language files
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:4NJuc00z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yRNa2BNZ:4NJuc00z"
}
