Skip to main content

Features

Detailed documentation of the QuickBuy Addon's feature set.

Real-Time Auction Purchasing​

The addon never uses a static price list. When a player clicks a configured slot, the addon:

  1. Calls AuctionManager.getActiveListings() for a live snapshot
  2. Filters to listings matching the slot's material, currency, price cap, and enchantment requirements
  3. Sorts by price-per-unit (cheapest first), excluding the buyer's own listings
  4. Attempts AuctionManager.buy() on the cheapest candidate — the same code path as a normal auction purchase
  5. If the targeted listing was just bought by someone else between the snapshot and the buy attempt, silently falls through to the next candidate instead of surfacing an error

This fallback chain means a busy auction house with concurrent buyers produces transparent, reliable results rather than failed clicks.

Dialog-Based Item Picker (1.21.6+ Java clients)​

Configuring a slot on a modern Java client opens the Minecraft Dialog API — a native, client-rendered UI surface introduced in 1.21.6, accessible via Paper's API from 1.21.7+.

Single-Screen Search + Scroll​

The results screen embeds a search text box and the full material list on one screen:

  • All shopable materials (1 000+) load at once in a single scrollable 3-column grid — the client scrolls natively, so the server never re-pushes the dialog and the cursor never recentres between pages
  • Typing in the search box and pressing Search filters the list server-side and re-renders the dialog with the filtered subset

Vanilla Sprite Icons​

Real item textures render inside each button label via Adventure's sprite object components (Component.object(ObjectContents.sprite(...))). The atlas is resolved against icons/valid-icon-sprites.txt, extracted directly from the 1.21.11 client jar — so only textures that actually exist are requested (no missing-texture boxes). Items with no flat sprite (slabs, stairs, fences, doors — anything rendered from a 3D block model) fall back to text-only.

No resource pack is required.

Icons need a newer client and server

Sprite icons are an Adventure "object" component, which only exists from 1.21.9. The addon shows them only when the client's real protocol is 773 (1.21.9) or higher, the server is 1.21.9 or higher, and the server's Adventure has the class. The client version is read through ViaVersion when it is installed, so an old client joining a new server through ViaBackwards is recognised correctly. A 1.21.6–1.21.8 client still gets the Dialog picker, with plain text labels instead of icons.

Enchantment Requirement Picker​

For enchantable materials, the picker advances to an enchantment requirement dialog with one SingleOption dropdown per applicable enchantment:

  • Options: None, I, II, III, ... (up to the enchantment's max level)
  • Defaults to None (no requirement) — players only configure the enchantments they care about
  • Selecting at least one level means purchased items must carry that enchantment at or above the chosen level

Delete with Confirmation​

When reconfiguring an existing slot, a "Delete Slot" button appears in the material picker. Clicking it opens a separate confirmation dialog before removing the slot's configuration.

Automatic Client Fallback​

The addon detects clients that cannot render Dialogs and automatically routes them to the chest-GUI fallback picker — no manual command or player choice involved.

Detection logic:

  1. If Floodgate is installed and the player is a Bedrock client (FloodgateApi.isFloodgatePlayer(uuid)), use fallback
  2. If ViaVersion is installed, read the real client protocol via ViaAPI.getPlayerVersion(uuid). If below 771 (pre-1.21.6), use fallback
  3. If ViaVersion is not installed, read the Bukkit-reported protocol. Note: with ViaBackwards, this may report the server's own protocol rather than the client's real version — installing ViaVersion is recommended for accurate detection
  4. Anything that cannot be determined is treated as "too old", which safely selects the chest picker

Chest-GUI Fallback Picker​

The fallback picker is a fully independent implementation — it shares no code with the Dialog flow.

Material Selection​

  • Paginated chest GUI (36 slots per page) showing every item the auction accepts (not spawn eggs, command blocks, barriers or anything else on the auction blacklist)
  • Each item rendered as its real Minecraft icon with an &e formatted display name
  • Search button closes the GUI, prompts in chat (type a name, all to clear, cancel to abort), then reopens the filtered list. A search with no results says so in chat
  • Only plain clicks are needed anywhere, so Bedrock touch and controller players can use every button

Enchantment Selection​

  • If the selected material is enchantable, opens a second chest GUI showing applicable enchantments as books
  • A plain click cycles the level: none → I → II → … → max → none, so a tap alone can raise, and finally clear, a selection (Bedrock has no right-click or shift-click)
  • Java shortcuts remain: right-click lowers the level and shift-click removes it
  • Enchanted book icon (glowing) for set enchantments, plain book for unset

Deleting a Slot​

  • When reconfiguring an existing slot, a delete button appears. The first click arms it (it turns red and says "Click again to delete"); a second click deletes the slot. Clicking anything else disarms it
  • Shift-click still deletes in one go for Java players

Price Input​

  • After enchantment selection (or directly for non-enchantable items), the GUI closes and the player is prompted in chat
  • A title/subtitle overlay (&6Enter Price / Max price you wish to buy {item} for) stays on screen while the player types, so the instruction doesn't scroll away in chat
  • Chat cannot send an empty message, so type none (or unlimited, or -) for no price limit; type cancel to abort
  • Prompts give up after 60 seconds (the overlay is cleared, and the player is returned to the item list for a search or to the shop for a price) so a player is never left with their chat swallowed. Running /quickbuy or reopening the picker also cancels a pending prompt

Edit Mode​

Editing a configured slot used to need Shift-click, which Bedrock does not have. Edit mode does the same thing with plain clicks, for every client:

  • Turn it on with the lever in the shop's last slot (shown only when that slot is locked for the player, so it never uses up a shop slot) or with /quickbuy edit
  • While it is on, clicking a configured slot opens the item picker for that slot instead of buying
  • Configured slots show a short "Click to edit this slot" line in place of the usual edit hint
  • It is one-shot: it turns off when the shop is closed or when a slot editor is opened

Price Input​

The Dialog price box and the chat prompt share one parser:

You typeResult
1500, 12.5, 0.01That price per item
1,500, 1,234,567Thousands separators are understood
12,5A comma decimal is understood
10k, 2.5m, 1b, 1tThousand / million / billion / trillion suffixes
$250A leading $ is ignored
empty, none, no limit, unlimited, -No limit
0, negatives, NaN, Infinity, 1e3, textRejected with the invalid-price message

Prices above 1e15 are rejected. Earlier versions accepted NaN, saved it, and then silently dropped the slot on the next restart.

Permission-Based Slot Allotments​

The number of usable slots is determined per-player based on permissions:

  • slot-permissions.default-slots applies to players with no matching override
  • slot-permissions.overrides defines a list of {permission, limit} pairs
  • If a player matches multiple overrides, the highest limit wins — never the first match, never summed
  • This mirrors the conflict resolution used by the core plugin's own order-limit permissions

Slots beyond the player's allotment are displayed as locked red glass panes and cannot be interacted with.

Optional Price Cap​

Each slot can be configured with or without a price cap:

  • With cap: only listings priced at or below cap per item are considered
  • Without cap: the cheapest listing is purchased regardless of price — shown as "No Limit" in the slot's lore
  • The price is per individual item, not per listing stack — a listing of 64 diamonds at 6400 total has a per-unit price of 100

Enchantment Requirement Matching​

A slot's required enchantments filter the candidate listing set:

  • For regular items: ItemStack.getEnchantments() is checked
  • For enchanted books: EnchantmentStorageMeta.getStoredEnchants() is checked
  • The listing's actual enchantment level must be ≥ the required minimum — higher is fine, exact match is not required
  • All required enchantments must be present simultaneously; partial matches don't qualify
  • The enchantment step offers every enchantment for enchanted books (vanilla's anvil accepts any of them), and lists enchantments from the enchantment registry, so custom and datapack enchantments appear too

Custom enchantments and missing enchantments​

Requirements are saved with the full namespaced key (for example minecraft:sharpness or myplugin:vein_miner), so custom enchantments survive a restart. If a saved requirement cannot be found when the shop loads (its plugin was removed, for example):

  • The slot is kept, not deleted, and the requirement is written back unchanged
  • The slot never buys until the enchantment exists again — dropping the requirement would make it buy unenchanted items
  • Its lore shows a red "Unknown enchantment" line, and a warning is logged

Manifest-Based Version Policy​

Like the other Sigma Orders addons, the QuickBuy Addon fetches a small JSON manifest from GitHub on every startup:

  • Checks Java version, Minecraft version, and plugin version against configured rules
  • A block rule disables the plugin (e.g. incompatible Java, a known-bad build)
  • A warn rule logs a warning but lets the plugin continue
  • An info rule for update availability triggers a delayed async log warning 1 second after startup so it appears after all other startup messages
  • The manifest is cached locally (manifests/policy-cache.json) — if GitHub is unreachable, the last successful manifest is used instead

Resilience​

  • Concurrent purchase safety — a structural re-entrancy guard (ConcurrentHashMap processing set) prevents a single player's purchase from being processed twice before the first attempt finishes
  • Stale GUI prevention — the shop GUI refreshes its lore immediately after every purchase attempt, so the displayed availability and price are always current
  • AuctionManager reconnect — if SigmaOrders-Auction reloads, the addon listens for PluginEnableEvent and re-acquires a fresh AuctionManager reference automatically
  • Session cleanup — all in-flight picker state (editing slot, pending material, pending enchantments, awaiting chat) is cleared on player quit so nothing accumulates for players who disconnect mid-flow
  • No items lost to the GUI — clicks are cancelled and so are drags, so a held stack can no longer be dragged into the shop or picker slots (where it used to vanish when the GUI closed)
  • Inventory identity — the shop and picker screens are identified by an inventory holder object, not by title, so an unrelated container that happens to be named "Quick Buy" or "Choose an Item" is never touched
  • Safe saving — a shop is written to a temporary file under a per-player lock and then moved into place, so two quick saves can no longer corrupt the file
  • Picker only offers what can fill — the item list is filtered through the auction's own allowed-item rules

See Also​