Tags
Creators
Details
Licensed BSD-3-Clause
Published last year
Updated 3 months ago
All versions
3.0.1
Beta
SellGUI 3.0.16 months ago 136
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.6
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Changelog
3.0.1 - 2026-05-10
Added
- Added
menus:support documentation and examples incustommenuitems.ymlso custom menu buttons can be limited to specific sell menus. - Added
worth-lore-whitelist-guiandworth-lore-whitelist-gui-titlestoconfig.yml. - Added worth-lore GUI title normalization for plain titles, legacy hex colors, and MiniMessage-style hex color tags.
Changed
- Updated plugin and Maven version to
3.0.1. - Worth lore can now run in blacklist mode as before, or whitelist mode when
worth-lore-whitelist-guiis enabled. - Price evaluation now stores an explicit
evaluatedmarker alongsidecurrent_price. - Stacking normalization now preserves evaluated item lore and
current_priceinstead of treating them as temporary data.
Fixed
- Fixed sell button lore replacing lines such as
Click to review the total.and causing duplicateTotal Valuelines. - Fixed evaluated/random-price items losing their evaluated lore during stacking normalization.
- Fixed evaluated/random-price items losing sellability when
current_pricewas removed during normalization. - Fixed evaluated item detection so
current_priceis recognized as an evaluated state.
3.0.0 - 2026-05-09
Added
- Added multi-menu sell GUI support through separate files in
gui/sell_menus/. - Added default sell menu:
gui/sell_menus/default.yml. - Added fishing-only sell menu example:
gui/sell_menus/fishing.yml. - Added
/sellgui <menu>support so players can open a specific sell menu. - Added
/sellgui <player> <menu>support for opening a specific menu for another player. - Added tab completion for available sell menu IDs.
- Added exclusive menu item rules so configured items can only be sold in their assigned menu.
- Added item stack normalization after furnace smelting, furnace extraction, player join, player quit, and plugin disable.
- Added
stackingconfig section to control item stack normalization behavior. - Added bundled
libs/shopgui-api-3.1.0.jarso Maven builds work after cloning the repository.
Changed
- Reworked SellGUI core logic around
SellMenuConfigfor cleaner multi-menu handling. - Split the old root
gui.ymlinto agui/folder:gui/sell_menus/default.ymlgui/sell_menus/fishing.ymlgui/price_setter.ymlgui/price_evaluation.ymlgui/autosell_settings.yml
- Updated config loading to merge all GUI YAML files from the
gui/folder at runtime. - Cleaned
config.ymlso core settings stay separate from GUI layout settings. - Updated plugin version to
3.0.0. - Updated Maven configuration to use the bundled ShopGUI API jar.
- Updated sell GUI rendering and confirm flow to respect the active menu.
- Updated autosell settings GUI to fit the cleaned config structure.
Fixed
- Fixed
/sellallselling items that should be locked to an exclusive sell menu. - Fixed autosell selling items that should be locked to an exclusive sell menu.
- Fixed intermittent item stacking problems caused by temporary SellGUI evaluation metadata and lore.
- Fixed evaluated item metadata causing vanilla items to stay split after smelting, join/leave, or server restart.
- Fixed GUI config generation so new installs create the new
gui/folder structure instead of a rootgui.yml. - Fixed build portability by committing the ShopGUI API dependency used by
pom.xml.
Migration Notes
src/main/resources/gui.ymlhas been removed.- Server configs should now use the generated
plugins/SellGUI/gui/folder. - Each sell menu should live in its own YAML file under
plugins/SellGUI/gui/sell_menus/. - Items configured as exclusive to one menu will be skipped by other sell menus,
/sellall, and autosell.
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:RmheYDS5:HX9ak7D9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RmheYDS5:HX9ak7D9"
}

