Skip to main content

Exact matching

Exact mode retains serialized item data and compares complete properties, including the name, lore, enchantments, and serializable custom data. Sample stack size does not define the order quantity or price. Changing durability, name, or other metadata can make an item stop matching.

Sample storage and display

New exact buy orders retain both the real sample and rule fingerprint, validate admission and matching material/fingerprint when published, and normalize the sample quantity to one. The sample is for display; fulfillment still transfers the supplier’s actual items. Historical orders containing only a fingerprint identify the missing display sample instead of guessing or recreating the original item.

Custom items and node consistency

Matching appearances do not make items equivalent. Names, lore, durability, enchantments, custom data and business identity can affect matching or complete-property comparisons. Nodes must have matching Minecraft versions and item profiles. Validate real samples created by your item plugin before enabling player trading.

Business identity bridges through public APIs

With the corresponding plugin enabled, KiteMarket can read real business sources and IDs through ItemsAdder, Oraxen, Nexo and MMOItems public APIs for advanced buy orders and filtering. Failed or unconfirmed identities are never invented from appearance, names, lore or guessed NBT. A business identity adds an explicit semantic condition; it does not relax escrow fidelity, complete EXACT comparisons or other configured rules. Unknown data that a confirmed identity cannot safely constrain still requires a complete exact sample. The advanced editor also supports CustomModelData ranges, up to 32 required PDC keys, and string, number or boolean fields opened through items.exposed-fields. See business identity and exposed fields.
Public API bridges do not certify every item combination. The fixed verified combination is Paper 1.21.11, Java 21 and Oraxen 1.220.0: one real custom pickaxe completed identity lookup, name search, listing, purchase and claims with matching native properties and stack size. This does not certify all Oraxen items or resource-pack appearance. Complete Nexo and MMOItems/MythicLib runtime combinations remain unverified.

Item admission

Exact samples still must pass item admission and serialization round-trip checks. Exact mode cannot bypass these restrictions. Special items and nested data can be traded only if admitted by the current build. An item plugin, SDK or interface theme cannot replace an admission result. If you see UNVERIFIED_SPECIAL_ITEM, UNVERIFIED_ITEM_DATA, or ITEM_ROUNDTRIP_UNSAFE, stop listing that item instead of retrying in exact mode.

Read-only container previews and round-trip fidelity

Admitted containers can open read-only previews from the order contents page, showing the actual stored contents. Clicking a preview cannot remove items or change the container. The container and every internal entry must pass storage, restoration and complete-property comparison. Unsupported nesting or structures, damaged snapshots and properties that cannot safely round-trip are rejected rather than converted into empty containers or stripped of unknown contents. Real items from trades, cancellations and expiry enter claims. Insufficient inventory space leaves them claimable without changing quantities or native stack limits. Follow the operations and migration guide for safe withdrawal of assets already in escrow. See buy-order condition editing for advanced rules.