Skip to main content
KiteMarket provides the complete vanilla GUI plus ItemsAdder v4 compatibility. Third-party developers may freely create, modify, use, distribute or independently sell their own configuration or Java interfaces without an additional KiteMC theme license. Public SDKs and examples have independent MIT licenses; IA theme resources are not bundled.
Version and downloadsBase rendering interfaces retain v1.0.0 usage. Public repository main now contains the v1.1 interfaces and examples; consult its additions for new pages. Runtime, SDK and example availability follows actual public versions on downloads.The pinned Paper 1.21.11 / Java 21 / ItemsAdder 4.0.16 combination has real openings of community configuration and Java examples; the recorded scope does not certify other versions or Folia.

Quick start

For vanilla appearance changes, use file configuration without writing a plugin. A built-in IA renderer only needs your resources and theme declaration; use Java only for custom rendering logic.
1

Get the example

Get examples/ui/themes/example-ia configuration or the Java adapter in examples/ui-java from the public repository. Use source or an actual Release bundle matching the host, and select files by version.
2

Install resources and the theme

Follow IA integration to install your namespace and theme, rebuild the pack and register its actual UUID and SHA-1.
3

Load configuration or the plugin

Java providers also require their JAR in plugins/ and a normal restart. Configuration-only themes use /km reload.
4

Select and verify

After the player successfully applies the pack, use /km ui itemsadder example-ia; the Java example theme is example-ia-java. Confirmation buttons act on the real market, so develop with isolated characters and orders.

Java example: GitHub Packages

Java projects reference the UI SDK with compileOnly. The public SDK targets Java 11; the real IA example adapter targets Java 21.

Java example dependencies

Gradle, Maven, Packages authentication and Release-download fallback.

Player selection and server defaults

/km ui displays the requested preference, actual interface, theme, and fallback reason. Select a backend and optional theme with:
Selection stores a preference. Without an actual provider, ready client, or resources, vanilla remains available with an explanation. “Choose a theme” in the settings lists registered themes with their backend and availability reason and can restore the server default. Preferences persist across the market network. Switching retains drafts and cannot submit a trade twice. For example:
Player buttons, command help and completion show only auto/vanilla/itemsadder. Old germ/dragoncore preferences, settings and SDK enums remain readable as existing extension positions. Developers may register, maintain and validate their own actual providers. Without a matching registered provider, the interface reports UI_BACKEND_RETIRED, falls back and retains the saved preference.

Own theme declarations

Configuration themes declare font backgrounds, page overrides and actual pack identity in themes/*.yml. Validate and load them with /km reload.

Configuration themes and IA resources

Full YAML example, theme ID rules, state backgrounds and pack-load confirmation.

Resources and provider implementations

The built-in IA renderer uses configuration themes; Java extensions register their own providers. Both use actual market pages and server-registered actions.

Install resources

Namespaces, pack rebuilds, sending and actual pack identity.

Implement a Java provider

Registration, page updates, display refresh and the real example.

Custom IA functional icons

Functional buttons may use your own registered IA items. Actual subject() trade items stay intact.

Functional icon configuration

Material defaults, physical-slot overrides and read-only icon bindings.

Pages, actions and lifecycle

Vanilla menus uses logical page IDs; IA pages uses template IDs. Renderers read the current snapshot, action tokens and input ranges.

Page and action list

Complete page and template IDs, home slots, inputs, actions and lifecycle contracts.

Theme the complete trading workflows

Themes can cover single items, bundles, individually confirmed batches, container contents, source-based claims, business conditions, community, risk, automation and administration pages. Read page and template IDs from the current snapshot rather than guessing them from titles or button labels. Home has a direct publishing entry; the profile groups favorites, subscriptions, history, review and permission-filtered administration entries. Configuration themes retain schema: 1. pages.'*' supplies a general background; individual templates can override font images, offsets and functional icons. Results may use state-font-images selected by the host’s result.status. Quantities, fees, asset destinations and genuine goods remain host data, not static balances or completion messages baked into textures. IA renderers reuse the protected 54-slot inventory and registered actions. Item slots in UiPage are final physical positions: do not shift list slots again. Actual subject() goods retain their complete properties. Themes replace functional icons and backgrounds; input continues to use host ranges and chat fallback.

New pages, updates and safe fallback

An update replaces the token, pageVersion, actions and all callbacks together. Same-page countdown refresh retains page identity. Theme changes, return and refresh preserve session drafts; late results cannot overwrite a newer page and old actions cannot submit again. Own Java renderers may call read-only itemsAdderUnavailable(player, page, theme) to check this page’s resources; only null means ready. It neither sends packs nor changes preferences or checks an additional theme license. Missing resources, unavailable pages and unloaded providers fall back to vanilla while retaining the player’s backend and theme choice. When updating a theme, check the complete page and action list, including confirmation and cancellation positions on different pages. Invalid theme or configuration candidates preserve the existing valid configuration. Third-party providers remain responsible for their actual engine compatibility; declarations and SDK registration do not certify real-server behavior.

Troubleshooting

Check the theme, provider and actual pack-load status first. Reopen stale pages instead of replaying their actions.

Troubleshooting table

Themes, resources, placeholder titles, callbacks and reload failures.

Installation and scope

After creating or obtaining a third-party theme, follow ItemsAdder integration to install its resources and register the actual pack identity. No official DLC product ID, signature or entitlement is needed. The plugin does not supply a commercial IA theme by default; unavailable themes retain the vanilla interface. The base plugin still follows network licensing for trading and asset exit. Compatibility records evidence for the base plugin, providers, and individual themes separately. Public SDKs and provider registration do not replace actual runtime acceptance.