Preparing existing market data
Back up and check migration in an independent copy before switching an existing environment. Do not mix builds or overwrite currency identities.
- Prepare the environment
Prepare a target server and Java runtime and real network-license credentials. One server can use bundled SQLite; a shared market needs MySQL 8 or MariaDB 10.11. A market network shares one database, Minecraft version, currency definition, and item profile. Node IDs must be unique.
Place one appropriate KiteMarket distribution JAR in plugins/; do not install multiple distributions together. Start once to generate plugins/KiteMarket/config.yml, then stop before editing.
- Network and database
This config.yml example is for a new single-server installation. The database file is stored in the plugin directory:
.db file of an active WAL database is insufficient. Changing the network, currencies or database requires a planned stop rather than routine hot reload.
Enable only the trading modes you need
market.enabled-types accepts any nonempty subset. For an auction-only market:
/km reload on each node, new trades follow the updated modes; existing orders can still be cancelled, expire, settle and deliver their assets.
Quantities and prices
market.minimum-purchase-quantity is the default minimum for sale drafts, initially 1. Sellers can set it from 1 to the listed quantity on the terms page.
Single-item sales and buy orders use per-item prices; indivisible bundle sales use whole-lot prices, and auctions use whole-lot starting totals. Single-sale remainders below the purchase minimum must be bought together; bundles do not support partial purchases.
Bulk publication produces independent orders, each confirmed separately. A mixed bundle is one order traded as a whole. See sales and auctions.
Language and fees
language accepts zh_CN, en_US, or auto; language files are in plugins/KiteMarket/lang/.
tax-bps uses basis points, so 100 is 1%. Without an enabled matching new fee rule, fees are deducted from the recipient’s income and listing fees default to zero.
market.taxes.<buy/sell/auction>.<currency-id> overrides that type’s default, then falls back to market.tax-bps. Values range from 0 to 9999 basis points.
Orders retain their fee settings captured at creation. New rules can configure listing, buyer and seller fees separately, allocating fixed charges and rounding over cumulative partial fills. A charged listing fee is not refunded on ordinary cancellation. See fees and restrictions.
- Currencies
Set the provider, precision, gateway and safe limit under currencies. Choose Vault, PlayerPoints, CoinsEngine, ExcellentEconomy, vanilla experience points, levels or a complete item-currency sample. Currency definitions must match throughout a network; do not expose the same external currency twice.
For external economy adapters, keep certified-versions empty until the specific version is verified; an empty list disables transfers. Choose either experience points or levels in one network. Item currencies require an actual serialized sample and positive integer denomination, not just a material name.
Currency configuration
Configure PlayerPoints, experience or item currencies, including minor units, complete identities and display names.
- Network license
Retain these values and supply your own key; never substitute a product name or private key.
The client appends
/api/v2/license/activate or /api/v2/license/heartbeat to the service root. Remote endpoints require HTTPS and first activation requires online verification.
Purchase a license on the product page, then find the key under your licenses.
- Restart and check the deployment
Restart and verify plugin initialization, database, sessions, and licensing.
Use isolated test players to check the enabled trade modes, transfers and claims. For a shared deployment, also check competing operations on two nodes. Verify each enabled provider; a loaded JAR does not prove transfers work. Confirm amounts, fees and asset destinations, preserving real failure or reconciliation states.
Restarts and reloads
Restart fully after changing network, database, currency, license or quantity/duration limits. Therisk, notifications, developer, automation, integrations, imports and items configurations are also fixed at startup and require a normal restart.
/km reload validates and updates presentation settings, new-order fees, policy and market.enabled-types; invalid candidates leave current settings intact. Update and reload every node in a shared market. Server /reload and hot plugin unloading are unsupported.
See commands and operations.
- Menu configuration
The default vanilla interface uses a warm 54-slot layout without a resource pack. gui controls renderers, general slot layout, home selection, and player preferences.
Players choose a backend and installed theme from their profile or /km ui. An unavailable pack or theme never triggers market wind-down.
Interface and layout
See the gui example, compact home slots, item help, and ItemsAdder pack configuration.
Customize the vanilla GUI
Server owners usemenus in config.yml to customize market, publication, community, automation and management pages. Edit the file, run /km reload, and reopen the page; invalid candidates preserve the previous working configuration.
Appearance and placement do not change existing actions, permissions, trading rules or assets, and cannot add trading buttons.
Vanilla menu customization
See bilingual titles and Lore, real-item protection, source slot swaps, and all page IDs.
- bStats basic metrics
KiteMarket enables standard bStats basic metrics by default under plugin ID 34434. The legacy, modern, and current distributions share this ID; it is not a network license ID.
KiteMarket adds no custom player, transaction, license, or database metrics. It does not submit transaction records, player identities, license keys, network tokens, database connections, or credentials as custom statistics.
To disable metrics for KiteMarket only, set this in plugins/KiteMarket/config.yml:
true. Alternatively, set the global enabled value to false in plugins/bStats/config.yml to disable bStats collection for plugins that honor that server-wide setting.
Either disabled switch prevents the corresponding collection. Restart fully after changing it. Metrics settings do not change trading features or license rules.
- Runtime, configuration and SDKs
Choose one matching Legacy, Modern or Current JAR on the download page, named KiteMarket-legacy-<version>.jar, KiteMarket-modern-<version>.jar or KiteMarket-current-<version>.jar. API, sources and Javadoc JARs are not server plugins. The download component lists actual public assets without substituting another JAR for a missing file.
Chinese and English configuration packages are labeled zh_CN and en_US. Retain their production product ID, license endpoint and trusted public key, filling in your license, database and economy configuration.
Back up and merge changes into an existing configuration rather than overwriting its network, database or currency identity.
Verify files using SHA256SUMS.txt and record the installed version. Isolated test signing keys and credentials are not production configuration.
The public repository also provides SDKs and runnable examples; see market API, interface development, and the compatibility scope.
- Configure by task
Trading and items
Set advanced buy conditions, publish single items or bundles and inspect real contents before delivery.
Wallets and automation
Check actual limits, shortfall top-ups, income reservations and opt-in automation.
Community and discovery
Favorites, saved searches, subscriptions, notices, sellers and same-currency reference prices.
Administration and risk review
Confirm reasoned management actions, exports, actual asset operations and human-reviewed risk signals.