menus in plugins/KiteMarket/config.yml to customize home, market, publishing, condition, wallet, claims, community, automation and administration pages. Every page uses the same configuration mechanism, without a resource pack or IA.
Edit the file, run /km reload, then reopen the page. Reload validates a candidate first; invalid settings preserve the previous working configuration.
Appearance and placement do not change existing actions, permissions, trading rules or assets, and cannot add trading buttons.
See interface and layout for renderer and home settings.
Titles, backgrounds, and controls
This example retains the legacy “My orders” source slot32, so it explicitly selects home-layout: legacy.
Merge it into the existing gui and menus sections without duplicating root keys. Omitted fields retain their defaults:
Configuration fields
Source slots and placement swaps
Menu slots are0..53, excluding the player’s inventory.
buttons, slots and icons use source slots, not the final visible position after the new layout remaps them. List sources 0..35 become physical 9..44, so additional help for the first product uses buttons.'0'.
Legacy home source 32 is “My orders” and 34 is “History”; the compact home uses the slot table in interface and layout.
Placement changes must swap both sides rather than moving only one. This example explicitly retains the legacy home:
buttons.slot and slots share one placement mechanism; do not configure a source twice. Existing syntax may instead use slots: {'32': 34, '34': 32}.
Custom placement requires gui.vanilla.layout: auto to select the compatibility layout, where source and physical slots match; do not simultaneously force warm.
Existing home settings
Legacygui.home-slots remains readable; migrate to the corresponding new home slots when choosing compact.
Existing menus.<page>.switch settings remain readable without injecting a button. Use the profile or /km ui to reach interface preferences.
Text and default help
Titles and names accept a shared string or bilingual text map; Lore accepts a shared list or bilingual list map.&/§ support vanilla colors and formatting. Generated names default to gold and Lore to gray, with italics disabled unless explicitly requested.
{default} preserves original title/name text; a Lore line containing only '{default}' expands the default market help.
Omitting lore preserves help; lore: [] clears only additional help.
${field-name} reads an existing read-only page field, such as ${wizard.step}; missing fields display — without executing scripts.
Raw money fields use minor units, so prefer {default} to retain formatted amounts and asset destinations.
Publishing policies and bundle fields
lot-editor and lot-batch-item expose read-only publication bounds for the current player:
Single/bulk sales use a unit price; auctions/bundles use a lot total. Policy fields do not guarantee inventory quantity, space or final admission. Violations retain the draft, and each confirmation rechecks the original request without automatic repricing or minimum-quantity reduction.
Bundle confirmations also expose
lot.mode, lot.entries, lot.quantity and goods.quantity: mode, entry count, number of lots and total item count. A bundle has one lot, which does not mean it contains only one item.
Preserve default confirmation help to show totals, fees, net income and asset destinations together. Do not recalculate published-order fees from current theme settings.
Real products and assets
Functional controls may change material and name. Products, samples, selected inventory items and claim assets retain their actual material, name, enchantments and original Lore;material/name cannot disguise them as another item.
Only their placement and additional market help can change, without altering inventories, escrow snapshots or transaction subjects.
All page IDs
These are the common pages; the groups below list the remaining configuration pages. Every key may be used inmenus:
assets/confirm for claims/wizard-confirm.
Bundle, bulk and container pages
lot-editor source 12 selects single/bundle/bulk mode, 14 selects sale/auction, and 32 opens a preview or bulk plan. Source 52 starts individual confirmation in the bulk plan and requests the next manual confirmation in results; neither completes the whole batch automatically.
Bundle confirm uses 22 for the summary, 24 for actual contents, 30 to confirm and 32 to cancel. lot-contents, container-preview and order-contents display real contents read-only.
Business-item condition pages
items.exposed-fields. OR and exact-sample notices remain read-only; appearance settings do not grant arbitrary script editing.
Community and notification pages
29 opens community. Favorites and search results retain real orders. The saved-search editor has separate currency, price-range, source, category, sorting and subscription controls. Seller day windows and price rolling windows retain their distinct server-provided descriptions.
Price and risk pages
risk-cloud-confirm, source 30 sends the request and 32 cancels, unlike ordinary claim confirmation. Shared in-progress or unconfirmed requests expose no resend action.
Automation and reservation pages
33 opens automation. automation uses 20/22/24 for future-income withdrawals, login withdrawals and automatic claims, and 40 for income reservations. Disabling future-income withdrawals does not release existing reservations. Confirmation uses 30 to cancel and 32 to confirm; review-required entries must not appear completed.
Administration write-tool pages
52 opens the permission-dependent tools. Money transfers, item transfers and listings on behalf of a player use actual existing assets. admin-tools-confirm shows the target, reason and consequences; 30 cancels and 32 confirms. Configuration cannot add punishment or asset-creation actions.
See pages, actions and lifecycle for individual source slots and SDK action semantics.
Validation and troubleshooting
Text entries are limited to 512 characters and Lore lists to 64 lines. Materials must exist on the current server. Unknown settings, invalid slots and incomplete swaps invalidate a candidate;command, action, scripts and expressions are not style settings.
On failure, fix the field path identified by the response and logs. If changes are missing, reopen the page and check source slots, layout and whether a third-party theme uses its own template.
These settings do not install or download IA resources.
v1.1: bundle and claims pages
Claim categories and batch confirmation
Configure claims using actual page IDs and source slots:
The existing
assets page adds 46 categories, 50 select/clear the current page, 51 claim selected and 52 selected details. Sources 0..35 select current-page assets; 45/53 page, 48 refresh and 49 back. claims remains an IA template alias, not the assets page ID.
order-contents, claims-details and assets use list remapping; claims-categories and claims-confirm retain their source positions. Manual claiming processes only the confirmed current page, at most 36 entries. Items that do not fit remain available; uncertain outcomes or changed sessions stop subsequent entries.
List sources 0..35 default to physical 9..44; tool sources 37/46/47/48/50/51/52 map to 5/0/1/7/2/3/4. Non-list pages retain their source positions. SDK and IA snapshots already contain final physical slots; never remap them again.