Skip to main content
Renderers read current page snapshots and registered actions. The server continues to control page identity, quantity ranges, quotes and transaction results.

Pages, actions and lifecycle

UiPage.key() identifies the logical page; UiPage.template() selects theme configuration. Vanilla menus uses page IDs, while IA pages uses template IDs. This list covers common flows and specialized pages. “Same” means the template equals the page ID. Always render actual current snapshots and registered actions.

Market and publishing

Wizard templates follow the step: wizard-type, wizard-item, wizard-terms (buy order), wizard-sale-terms, wizard-auction-terms, then wizard-confirm.

Input and conditions

Assets and administration

V1.1 additions

These specialized pages use their page IDs as template IDs and share menus, snapshots and action handling. Never guess keys, templates or button positions from display text.

Bundles, bulk listings and containers

Single items, mixed bundles and separate orders require distinct displays. Unpublished bulk plans persist only in the current session, without automatic continuation after restart.

Claim sources and current-page confirmation

The existing assets page uses source 46 for categories, 50 for select/clear current page, 51 for claim selected and 52 for details; 0..35 selects entries. Confirmation covers at most 36 current-page assets. Items that do not fit remain available; uncertainty, changed sessions or disconnects stop subsequent entries.

Business-item rules

Validate each independent candidate before updating the draft. Fields come only from items.exposed-fields; OR and EXACT notices are read-only. Themes cannot add arbitrary scripts or rewrite actual matching values.

Community, notifications and sellers

Chat delivery does not automatically mark notifications read. Sellers use 1/7/30 UTC calendar days; public prices use rolling 24-hour/7-day/30-day windows. Keep these distinct.

Prices and risk review

Public prices require browse permission; other risk pages require audit permission, with administration additionally required for state, training and cloud writes. Case states do not punish players. Themes cannot resend in-progress or unknown requests.

Automation and income reservations

Disabling future-income withdrawals does not release existing reservations. Externally executing or unknown entries differ from ordinary available balances; preserve host status and pause notices.

Administration write tools

Tools use actual existing money and items. Export retention removes only this network’s expired generated exports, preserving financial records and unresolved operations.

Complete source-slot reference

Individual source slots, list mapping and functional configuration examples.
Vanilla menus uses source slots; SDK snapshots and IA slot-icons use final physical slots. Never apply the default list mapping twice. Entries without registered actions are informational and cannot gain transaction callbacks through themes.

Home and profile slots

Default compact home source slots are 0 player head, 4 help, 8 claims, 20/22/24 trading categories, 31 create/edit draft, 45 wallet and 53 my orders. profile uses 20 interface preferences, 22 review queue, 24 history, 29 community, 31 administration, 33 automation, 35 risk and 49 back. Administration/risk entrances depend on permissions. The review list reuses history. Disabled market.enabled-types are hidden from home and publishing without rearranging source slots. Themes render only registered available actions and cannot re-enable modes. Select home content with gui.home-layout: auto|compact|legacy; an existing menus.home preserves the legacy home under auto. See vanilla GUI customization for migration. Read current snapshots and actions instead of assuming all home layouts share one slot set.

Quantities, amounts and results

Quantity maxima use actual wallet funds, available inventory items, policy and currency limits. The basic main-hand single-item auction uses that stack; multi-slot publishing reads the explicitly selected complete single lot, mixed bundle or independent groups. Transfers use actual balances and known backend receive capacity. Changed quotes require another choice, and final submission rechecks limits; a theme must not raise them independently. Receipts provide a separate “View / copy operation ID” action that sends the complete ID and copy control in chat. Summaries stay concise; inspect and the read-only API retain IDs.

Transaction display

Single-item sales support partial purchases at a per-item unit price. Their per-order minimum defaults to 1 and can be set from 1 to the listed quantity; a remainder below the minimum must be bought together. Buy orders use unit prices for partial fulfillment. Both single and bundle auctions use whole-lot starting prices. Bundle sales use a whole-bundle price without partial purchase; bulk sales remain separate unit-price orders. Render host amounts, input ranges, publication-time fees and item descriptions. Quantity, total and traded amounts are separate, with real item properties intact. Bundles also distinguish lot count, entry count and actual total item quantity. Display timestamps and countdowns do not replace database deadline checks. Claims use actual item stack limits, leaving assets in claims when inventory space is insufficient. Bundle confirm uses source 30 to confirm and 32 to cancel. Claims, automation and administration confirmations use 30 to cancel and 32 to confirm; risk-cloud-confirm uses 30 to send and 32 to cancel. Dispatch actual page tokens instead of assuming one slot always means confirmation.

Actions and input

The current page.actions() slot-to-opaque-token map is the action list. Entries without a token are informational. Never fabricate action strings or reuse a previous page’s tokens. Every open/update replaces identity, tokens and callbacks. Input returns through UiCallbacks.input(raw) and closure through closed(). Returning false from prompt() retains the host’s validated chat input and drafts.

Provider lifecycle

Registration can wait for database initialization. If lookup is null, listen for ServiceRegisterEvent; discard old registrations and views when replaced. Unregister on owner disable; the host handles safe fallback. Never manipulate player inventories from Folia’s global thread. The example does not claim Folia certification.

Java renderer development

Provider registration, page updates, display refresh and resource state checks.