` | false | Multiplies sell prices |<\/p>\nExamples:<\/p>\n
“`text
\nsellgui.multiplier.2.0
\nsellgui.bonus.30
\nsellgui.menu.fishing
\n“`<\/p>\n
When adding a new menu, give it its own permission in the menu file, for example `sellgui.menu.mining`, then grant that permission to the ranks that should use it.<\/p>\n
## v3 Configuration Layout<\/p>\n
After the first server start, SellGUI creates files under `plugins\/SellGUI\/`.<\/p>\n
“`text
\nplugins\/SellGUI\/
\n config.yml
\n itemprices.yml
\n mmoitems.yml
\n nexo.yml
\n customitems.yml
\n custommenuitems.yml
\n random-prices.yml
\n messages.yml
\n sounds.yml
\n autosell_data.yml
\n gui\/
\n sell_menus\/
\n default.yml
\n fishing.yml
\n price_setter.yml
\n price_evaluation.yml
\n autosell_settings.yml
\n“`<\/p>\n
The old root `gui.yml` has been removed in v3. GUI layouts and sell menus now live in the `gui\/` folder.<\/p>\n
SellGUI loads and merges all `.yml` and `.yaml` files inside `gui\/`, including files in subfolders. The recommended layout is one sell menu per file under `gui\/sell_menus\/`.<\/p>\n
## Multi-Menu System<\/p>\n
Default menu:<\/p>\n
“`text
\nplugins\/SellGUI\/gui\/sell_menus\/default.yml
\n“`<\/p>\n
Example fishing menu:<\/p>\n
“`text
\nplugins\/SellGUI\/gui\/sell_menus\/fishing.yml
\n“`<\/p>\n
Example `mining` menu:<\/p>\n
“`yml
\nsell_menus:
\n mining:
\n name: “Mining”
\n permission: “sellgui.menu.mining”
\n title: “&8\/sellgui > Mining”
\n size: 36
\n item-filter:
\n allowed-items:
\n – “IRON_INGOT”
\n – “GOLD_INGOT”
\n – “DIAMOND”
\n – “EMERALD”
\n denied-items: []
\n exclusive: true
\n positions:
\n sell_button: [31]
\n confirm_button: [31]
\n filler_slots: [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 17, 18, 26, 27, 28, 29, 30, 32, 33, 34, 35]
\n item_slots: [10, 11, 12, 13, 14, 15, 16, 19, 20, 21, 22, 23, 24, 25]
\n items:
\n sell_button:
\n material: “EMERALD”
\n custom-model-data: 0
\n name: “&a&lCalculate Mining Sale”
\n lore:
\n – “&7Only mining items can be sold here.”
\n – “&eTotal Value: &a$0.00”
\n glow: true
\n confirm_button:
\n material: “GREEN_CONCRETE”
\n custom-model-data: 0
\n name: “&a&lConfirm Mining Sale”
\n lore:
\n – “&fTotal: &e$%total%”
\n glow: true
\n filler:
\n material: “GRAY_STAINED_GLASS_PANE”
\n custom-model-data: 0
\n name: ” ”
\n lore: []
\n no_items:
\n material: “BARRIER”
\n custom-model-data: 0
\n name: “&c&lNo Items To Sell”
\n lore:
\n – “&7Add mining items to this menu.”
\n item_total_format: “&7%amount%x &f%item% &8= &e$%total%”
\n evaluation_required_format: “&7%amount%x &f%item% &cNeeds Evaluation”
\n“`<\/p>\n
Open it with:<\/p>\n
“`text
\n\/sellgui mining
\n“`<\/p>\n
## Item Filters And Exclusive Items<\/p>\n
Each menu can define:<\/p>\n
“`yml
\nitem-filter:
\n allowed-items: []
\n denied-items: []
\n exclusive: false
\n“`<\/p>\n
| Key | Description |
\n| — | — |
\n| `allowed-items` | If empty, the menu accepts any valid item except denied items and items locked to another exclusive menu. If populated, the menu only accepts listed items. |
\n| `denied-items` | Blocks specific items in that menu. |
\n| `exclusive` | When `true`, listed allowed items can only be sold in this menu. |<\/p>\n
With `exclusive: true`, those items are:<\/p>\n
– Blocked from other sell menus.
\n– Skipped by `\/sellall`.
\n– Skipped by autosell.<\/p>\n
## Item Identifier Format<\/p>\n
Vanilla items can be written by material name:<\/p>\n
“`yml
\nallowed-items:
\n – “COD”
\n – “SALMON”
\n“`<\/p>\n
Full identifiers are also supported:<\/p>\n
“`yml
\nallowed-items:
\n – “VANILLA:COD”
\n – “MMOITEMS:SWORD.EXCALIBUR”
\n – “NEXO:CUSTOM_FISH”
\n“`<\/p>\n
| Item type | Format |
\n| — | — |
\n| Vanilla | `VANILLA:MATERIAL` or just `MATERIAL` |
\n| MMOItems | `MMOITEMS:TYPE.ID` |
\n| Nexo | `NEXO:ITEM_ID` |<\/p>\n
## Price System<\/p>\n
SellGUI can read prices from multiple sources:<\/p>\n
– `itemprices.yml` for vanilla items.
\n– `mmoitems.yml` for MMOItems.
\n– `nexo.yml` for Nexo items.
\n– Essentials worth when `use-essentials-price: true`.
\n– ShopGUI+ when `use-shopguiplus-price: true`.
\n– NBT\/PDC prices when `prices.nbt-pricing: true`.
\n– Random\/evaluation prices from `random-prices.yml`.<\/p>\n
Main price config:<\/p>\n
“`yml
\nprices:
\n nbt-pricing: true
\n calculation-method: “auto”
\n default-price: 0.0
\n multipliers:
\n enabled: true
\n permission-based: true
\n default-multiplier: 1.0
\n max-multiplier: 5.0
\n random-pricing:
\n enabled: false
\n variation-percent: 10.0
\n“`<\/p>\n
`prices.calculation-method` values:<\/p>\n
| Value | Description |
\n| — | — |
\n| `auto` | Automatically choose the best available price source |
\n| `config` | Use SellGUI config prices only |
\n| `essentials` | Use Essentials worth only |
\n| `nbt` | Use NBT price only |
\n| `shopguiplus` | Use ShopGUI+ only |<\/p>\n
## Price Setter<\/p>\n
Open the GUI:<\/p>\n
“`text
\n\/sellguiprice
\n“`<\/p>\n
Workflow:<\/p>\n
1. Place an item in the center slot.
\n2. Use the GUI or chat input to enter a price.
\n3. Click save to write the price.<\/p>\n
Quick command:<\/p>\n
“`text
\n\/sellgui setprice 10
\n“`<\/p>\n
In most price-setting flows, price `0` can be used to remove the saved price.<\/p>\n
## Price Evaluation<\/p>\n
Open the GUI:<\/p>\n
“`text
\n\/sellgui evaluate
\n“`<\/p>\n
Use this when items must be evaluated before they can be sold. Related files:<\/p>\n
“`text
\nplugins\/SellGUI\/gui\/price_evaluation.yml
\nplugins\/SellGUI\/random-prices.yml
\n“`<\/p>\n
If `general.allow-player-evaluation-stack: false`, players cannot evaluate a whole stack at once.<\/p>\n
## Autosell<\/p>\n
Open the GUI:<\/p>\n
“`text
\n\/autosell
\n\/sellgui autosell
\n“`<\/p>\n
Autosell lets players toggle automatic selling for priced items. Player data is stored in:<\/p>\n
“`text
\nplugins\/SellGUI\/autosell_data.yml
\n“`<\/p>\n
In v3, autosell skips items locked to exclusive sell menus so category-specific items are not sold accidentally.<\/p>\n
## SellAll<\/p>\n
Commands:<\/p>\n
“`text
\n\/sellall
\n\/sellall confirm
\n“`<\/p>\n
`\/sellall` calculates a preview. The player then confirms with `\/sellall confirm`.<\/p>\n
In v3, `\/sellall` skips:<\/p>\n
– Items with no price.
\n– Enchanted items when `sell-all-command-sell-enchanted: false`.
\n– Items that require evaluation but have not been evaluated.
\n– Items locked to an exclusive sell menu.<\/p>\n
## Item Stack Normalization<\/p>\n
V3 adds stack normalization to fix vanilla items that stop stacking because of temporary SellGUI metadata or lore.<\/p>\n
Config:<\/p>\n
“`yml
\nstacking:
\n enabled: true
\n normalize-on-join: true
\n normalize-on-quit: true
\n normalize-on-plugin-disable: true
\n normalize-smelt-results: true
\n normalize-after-furnace-extract: true
\n“`<\/p>\n
This removes temporary SellGUI metadata such as `current_price`, `evaluated`, and `Evaluated: …` lore when appropriate, then merges similar stacks in the player’s inventory.<\/p>\n
It does not intentionally remove custom NBT or metadata from other plugins, so custom items with real metadata stay intact.<\/p>\n
## PlaceholderAPI<\/p>\n
When PlaceholderAPI is installed, SellGUI registers the `sellgui` identifier and processes PlaceholderAPI placeholders in supported GUI text.<\/p>\n
### SellGUI PlaceholderAPI Placeholders<\/p>\n
| Placeholder | Description |
\n| — | — |
\n| `%sellgui_pricehand%` | Price of the item in the player’s main hand |
\n| `%sellgui_pricehandfull%` | Item name and price of the item in hand |<\/p>\n
### Built-In Placeholders<\/p>\n
These placeholders can be used in SellGUI text\/config values. If PlaceholderAPI is installed, SellGUI lets PlaceholderAPI process placeholders first. If PlaceholderAPI is missing or fails, SellGUI falls back to these built-in placeholders.<\/p>\n
| Placeholder | Description |
\n| — | — |
\n| `%player%` | Player name |
\n| `%player_name%` | Player name |
\n| `%player_displayname%` | Player display name |
\n| `%player_uuid%` | Player UUID |
\n| `%player_world%` | Player world name |
\n| `%player_x%` | Player block X position |
\n| `%player_y%` | Player block Y position |
\n| `%player_z%` | Player block Z position |
\n| `%player_health%` | Current player health |
\n| `%player_max_health%` | Max player health |
\n| `%player_food%` | Player food level |
\n| `%player_level%` | Player XP level |
\n| `%player_exp%` | Player XP progress percent |
\n| `%vault_eco_balance%` | Player Vault economy balance |
\n| `%player_balance%` | Player Vault economy balance |
\n| `%server_name%` | Server name |
\n| `%server_version%` | Full server version |
\n| `%server_bukkit_version%` | Bukkit version |
\n| `%server_online%` | Online player count |
\n| `%server_max_players%` | Max player count |
\n| `%sellgui_version%` | SellGUI plugin version |
\n| `%sellgui_author%` | SellGUI plugin authors |
\n| `%time%` | Current server local time |
\n| `%date%` | Current server local date |
\n| `%timestamp%` | Current server local date and time |<\/p>\n
## Worth Lore Through PacketEvents<\/p>\n
Enable in `config.yml`:<\/p>\n
“`yml
\ngeneral:
\n add-worth-lore: true
\n“`<\/p>\n
PacketEvents is required. SellGUI displays worth lore through packets so the real inventory item is not constantly rewritten with lore.<\/p>\n
GUI titles where worth lore should not be shown:<\/p>\n
“`yml
\ngeneral:
\n worth-lore-blacklist-gui-titles:
\n – “ah”
\n – “Auction House”
\n – “My Chest”
\n“`<\/p>\n
## Migration From Older Versions<\/p>\n
If you are upgrading from a pre-v3 build:<\/p>\n
1. Back up `plugins\/SellGUI\/`.
\n2. Stop the server.
\n3. Install the v3 jar.
\n4. Start the server to generate the new `gui\/` folder.
\n5. Move old GUI layout\/menu settings from `gui.yml` into files under `gui\/`.
\n6. Put each sell menu in its own file under `gui\/sell_menus\/<\/p>\n