Skip to main content

Orders, delivery and collection

Mod version shipped with FlammiCraft: 2.64.0

Handbook overview

Clipboard orders

Orders use the same TDLibrary/LDLib2 panels, buttons, fields and backdrop as the account dashboard and shop editor. Public, created, accepted and finished views are filtered on the server before pagination. Each list entry shows the full quantity, reward and handover type. Opening an order shows its delivery location, description, progress and next action. The main action stays in one position; negotiation, cancellation, clipboard recovery and extra details are under More actions. Long text scrolls with the mouse wheel or Page Up/Page Down. Errors remain in the current view; hover the message or open contextual help to read it in full. Draft fields, search, selected execution and reading position survive applicable server refreshes.

Craft tdeconomy:order_clipboard from three paper, one iron nugget and one plank. A blank clipboard opens one form: choose items or a task, enter its title, quantity and payment, optionally add a description, then review and save. For example, 64 iron ingots for 200 money is one complete delivery. More settings contains requester/payment accounts, partial deliveries and public repetition. The personal account is selected initially. An item request stores 1–4096 items per delivery, 1–4096 deliveries and positive payment per delivery with up to two decimal places. Additional deliveries repeat that quantity and payment; the displayed total includes all of them. Existing package terms are retained without rounding or conversion. A free-text task has one completion and one agreed payment. Closing a changed draft offers save, discard and return.

The clipboard refers to one server-owned order. Passing it to another player does not transfer the requester's identity or account rights. Its tooltip refreshes when saved, opened or recovered. Clear clipboard only removes the held document's link; it does not cancel work, remove goods or release reservations. With a blank clipboard in hand, involved players can recover a document through More actions in their own orders.

Choose the handover route

The editor, order list and detail view identify the handover route:

  • Delivery box: save the draft and right-click a box you manage with the written clipboard before posting it. This binds that box as the destination and keeps the clipboard. Sneak-right-click remains available for explicit binding and still requires the box's publish permission.
  • In-person handover: without a linked box, give the goods to the requester outside the automatic system. The contractor reports completion; the requester checks what was received and confirms payment.
  • Work: report completion and let the requester review and pay for the work. No items are created or consumed.

Give the written clipboard to another player for a private request. Right-click someone else's postbox to submit a request addressed to its player/group owner; the clipboard is consumed only after successful submission. A postbox is independent of nearby shops and its request inbox contains only addressed orders. A public request merely using a box as its destination does not become an addressed order in that inbox.

Right-click a public board with the written draft to post it. Saving or opening a menu never publishes or submits it; these actions require the physical interaction and are checked by the server. Public lists postings, Created by me lists your requests, My work lists active work you may fulfill, and Finished keeps completed and cancelled history. Public listings are also available through /money orders; /money orders mine opens involved requests.

Acceptance, delivery and collection

Only public postings support multiple independent executions. Each acceptance takes the complete original quantity and reward, not a fraction of a shared quantity. The posting limit counts completed executions as well as running ones. Repeated acceptance by the same player is enabled by default, with at most one active execution at a time; the author can instead allow only one completion per player. Accepting reserves the unpaid reward in the paying account. Reserved money stays in its balance but is unavailable to other transactions. Source/infinite system accounts keep their established money modes.

At the loaded matching delivery box, or through your order view within eight blocks of it, choose Hand over goods. The dialog shows matching inventory items, existing prepared stock, remaining quantity and the exact payment. Select complete deliveries and confirm once. The server uses your execution's prepared goods first and takes only the missing plain matching items from your inventory, then advances progress, pays and stores the customer's goods in one recoverable, durable change. Customized stacks do not match plain requests. There is no separate mandatory deposit step.

Existing preparation compartments remain isolated per execution. Take remaining goods back returns unused stock, including after cancellation or manual completion; a full inventory leaves the remainder stored. Preparing or returning goods never pays. The shared 108-stack capacity includes prepared stock, current paid goods and earlier agreement goods. Capacity planning accounts for preparation consumed by the handover. Missing items, stale terms, failed payment, full storage or failed persistence must not leave a partial movement.

At the destination box, the requester opens Goods to collect only their own paid goods with current collection rights. A full inventory allows partial collection and retains the remainder. Outside the box, its location remains visible; goods are not remotely collected through the board.

For personal handovers, Confirm receipt pays only for the selected complete deliveries the requester actually received. For tasks, Confirm completed work releases the agreed payment. These actions do not create collection goods or consume previously prepared items. The same quantity cannot be paid twice.

Ending work and dismantling a box

More actions provides a single cancellation review with explicit choices: end the listing only, or also abort running work. Ending a listing leaves accepted work and reservations intact; aborting work releases its unpaid reservation. Paid money, paid goods and unused prepared items are retained. Removing a public or submitted listing returns exactly one clipboard; if it cannot fit, the entire operation is rolled back.

A cancelled single-contractor order is terminal and does not silently reopen. Aborting a public execution leaves its open posting available for another complete execution. Finished history alone does not occupy a box. Box removal or reassignment is blocked by running work, an open request still using it, paid goods waiting for collection, or prepared goods waiting to be returned. The box view and break denial name the actual blocker. After those obligations are gone, its manager may dismantle the empty box without separately closing historical records.

TDClaim may call de.taker.tdeconomy.api.OrderBoxAccess.allows for SUBMIT, MANAGE, DELIVER or COLLECT. Loaded-world, reach, party/account permissions, account modes, funding, revisions and self-trade checks remain server-authoritative; the UI and the audit service cannot authorize an operation.

SavedData schema 22 retains durable title entitlements while retaining existing order state. Supported existing orders, preparation compartments, paid goods, reservations and earlier agreements are retained. Previous agreements remain accessible through /money orders previous or More actions in the own-orders list. Network protocol 60 requires matching updated client and server builds. Run the manual acceptance checks after a full restart; a unit test or local build is not gameplay acceptance.

Previous order agreements

The item-shop editor opens this same picker through its Select item button; it does not require a separate hotbar selector. The shop preview shows the selected item, while the button keeps its action label.

The following describes the stored agreements from earlier versions, accessible through /money orders previous. New publications cannot be created here.

Choose an item through the existing inventory and searchable all-items picker. Quantities range from 1 to 4096; named, enchanted or otherwise customized stacks do not match plain-item requests. Receipts and clipboards cannot be ordered. There are no player, group, supplier or server quotas for publications or proposals. Lists and account choices are paginated to keep individual network messages bounded.

Negotiable — I am looking for is the default. The buyer publishes an item and quantity, with an optional maximum unit price and total budget (zero means no limit). Suppliers propose a quantity, positive unit price and receipt account. The proposal records the supplier's consent; the buyer must review and confirm the same final terms. Fixed — I offer lets a supplier publish item, quantity, unit price and receipt account, and choose whether buyers may accept partial quantities. A buyer selects their identity and payment account and confirms a proposal; the supplier then confirms the fully specified agreement again. Fixed offers do not retain the optional price or budget limits of negotiable requests. Switching the creation form to a fixed offer clears the budget, and the server excludes these limits from fixed publications.

Publication, proposal and agreement identities and revisions persist across reopening and restart. Editing a publication before its first delivery resets every affected consent; changing agreement quantity, price or account also resets both parties' consent. Fixed prices are changed by editing the publication. Either party can revise its own money account for an undelivered agreement, subject to current payment or receipt permissions. This changes only that agreement; the publication's default account and other agreements remain intact. Once deliveries have begun, use withdrawal and a new publication instead of rewriting paid terms. Confirmation dialogs show items, quantities, unit/total prices, both parties, both money accounts and the delivery destination.

Only Deliver now, followed by explicit review, transfers items and pays for the requested delivery quantity. Agreements support multiple partial deliveries. Publishing, proposing and confirming never reserve or move money. Confirmed agreements occupy their remaining quantity but have no delivery deadline, even after the original publication closes. Either party may withdraw without consent, penalty or payment; paid goods remain available. Closing a publication prevents new proposals and cancels unconfirmed proposals while preserving confirmed ones.

Personal, group and system identities and money accounts are selected separately. Current group publish/confirm/collect/cancel rights and payment/receipt permissions are checked on the server, including the original confirmers before delivery. System use requires an operator with active admin mode; source accounts can pay, sink accounts can receive, and finite/infinite accounts retain their existing money rules. Self-trading cannot be bypassed by selecting another controlled account or by acting as a supplier to one's own group.

Missing funds, overflow, insufficient matching items or destination capacity reject the whole requested delivery. Collection takes only as many goods as fit in the collector's main inventory and preserves the rest and their buyer identity. Order proposals, buyer/supplier acceptances, declined proposals, withdrawals, publication closures, changed terms and paid deliveries also enter the persisted notification inbox in the same durable SavedData change as the order event. Both eligible parties receive offline updates, with current group rights checked again when displayed. Notification pagination does not limit orders or offers. Shop price algorithms are unchanged.

Orders, market volume and notifications use SavedData schema 22. Explicit migrations preserve earlier test-world orders, paid goods and recovery images; old buy requests become negotiable publications without inventing a supplier's or buyer's agreement consent. Mutations are durably saved. Deliveries and collections record the resulting inventory and a player marker. Before releasing that inventory for further interaction, the server saves and reads back the player checkpoint, including the singleplayer owner's embedded player data in level.dat. A failed checkpoint disconnects the player; the durable recovery image is retained for the next login. Quest and order deliveries share inventory encoding and supersede previous recovery snapshots in one durable change. Order requests are limited to four per second and mutations to two per second, across clipboard and block reopenings. Audit events remain optional and never authorize an order or determine funds.