Logistics reference
Mit FlammiCraft ausgelieferte Mod-Version: 1.13.0
Diese Detailseite ist derzeit auf Englisch verfügbar.
Detailed reference retained from the original AFN help. Integration-specific entries apply only when the corresponding mod is installed. Examples describe mod behavior; pack recipes and settings may differ.
Default item slots keep independent counts. Omit count to retain those quantities; supply count to give every selected item that quantity. General's default count fills omitted counts in direct-item commands and JSON rows. Changing it does not overwrite existing slot quantities.
A new mailbox has incomplete item, count and address defaults. Omitted counts do not automatically become 1. Before ordering, every row needs a resolvable item, a positive integer quantity and a non-empty destination.
address=Workshop
A command can supply only the missing or overridden fields. With default apples ×16, bread ×8 and address Canteen, this keeps both quantities and changes this request's address to Workshop:
With those default items, count=4 requests 4 apples and 4 bread. If the default selector is a saved group, count=4 instead requests four copies of that group.
On General, choose a default item group or add up to 9 default item types, and set the default address. A valid selected default group takes priority.
Create a group on Item Groups, double-click its name to rename it, expand it and add items with the plus slot. Scroll over an item to change its quantity; right-click its slot to remove it. Items are not consumed. Set a shared or per-item address.
For example, save Lunch with 16 apples, 8 bread and 1 cake, and set its shared address to Canteen. Send this group name and activate once to request those quantities:
The equivalent JSON uses name to select the saved group:
{"name":"Lunch","count":2,"address":"Workshop"}
For a saved group, count multiplies every configured quantity. Omitting it means one group, regardless of General's default count. This requests two lunches—32 apples, 16 bread and 2 cake—and sends all of them to Workshop:
Lunch
Lunch,count=2,address=Workshop
A group's address priority is: command override → shared group address → that row's address → General default address. A shared group address therefore overrides every row address.
Quantities and group multipliers must be positive integers. In JSON, write 16, not "16" or 16.0. Each final row may request up to 1,000,000 items; the whole request may total up to 4,000,000.
Item Groups holds up to 64 groups with 9 item types each. A JSON items array accepts up to 32 rows per request. Group names may contain up to 48 characters, addresses up to 128.
Field names must be lowercase. Select a saved group with name, one item with item, or multiple items with items; do not combine these selectors. Unknown, repeated and internal protocol fields invalidate the command.
Order syntax allows up to 2048 characters and also follows the server channel-text allowance when sent wirelessly. Save long lists as supply groups and send the group name.
Each row can override the outer address with its own address. If both are omitted, General's default address applies. This example sends apples to Canteen and bread to Workshop:
{"address":"Canteen","items":[{"item":"minecraft:apple","count":16},{"item":"minecraft:bread","count":8,"address":"Workshop"}]}
A row's count overrides the outer count. If both are omitted, General's default count applies. An outer count supplies that quantity for each row; it is neither a total nor a multiplier.
{"address":"Canteen","items":[{"item":"minecraft:apple","count":16},{"item":"minecraft:bread","count":8},{"item":"minecraft:cake","count":1}]}
Write one object per item in a JSON items array. Send the entire JSON as one channel text value.
An items row accepts only item, count and address. Stock Mailbox rows using id/name cannot be pasted directly; change their item selector to item first.
One activation requests 16 apples, 8 bread and 1 cake, all for Canteen. The outer address supplies the shared destination.
One command can request several item types with independent quantities. Lines sharing an address form one order; different addresses are planned separately. Multiple packagers and packages may fulfil the request.
A Logistics Mailbox receives an item request and asks its bound Create logistics network to package it. A Stock Mailbox reads inventory counts. Put the request in the sending channel's content; the Logistics Mailbox has no item storage.
General defaults and omitted fields
Save and call an item group
Field rules and input limits
Request several items and quantities
Purpose and order flow
Set up the network and frequency
Request one item type
Activation, repeated orders and retries
When items do not arrive
address is the package delivery address, not the AFN frequency or logistics network name. Replace sample addresses with the actual destination.
Match the sender's and mailbox's primary/secondary frequency slots. AFN frequency selects which mailbox receives the command; the bound Create logistics network selects where items are requested. Configure these separately.
Before placing the mailbox, hold it and right-click a Packager Link or another node on the target logistics network without sneaking. Once the item shows its tuned glint, place it to retain the binding. The network needs working packagers and stock.
Put an example below in a sending Mailbox's or Bridge's channel content as text, then activate it once at strength 1–15. A complete item, count and address needs no saved group or General-page defaults.
The compact form is item,count,address, separated by commas:
minecraft:apple,16,Canteen
item selects the item, count is the number of individual items, and address is the destination. All three examples below request 16 apples for Canteen.
JSON is also supported. Counts are integers; items and addresses are double-quoted strings:
{"item":"minecraft:apple","count":16,"address":"Canteen"}
item=minecraft:apple,count=16,address=Canteen
Use a registry ID or an unambiguous item name, such as Apple. If a name is unknown or matches several items, use its complete ID, such as minecraft:apple.
While active, a different received text command executes once. Selecting a group or editing configuration alone does not transmit a new wireless command.
Default request: finish configuring General's default items or group and the final destinations, then give the Logistics Mailbox a rising redstone edge. A positive wireless activation without text also attempts that default request. Completing the network binding or previously incomplete defaults while redstone is already on also attempts one request immediately; keep redstone off while configuring.
An unchanged, sustained positive signal executes only once. To order the same batch again, drop the signal to 0 and activate it again.
Insufficient stock or a busy packager does not trigger automatic retries. Fix the cause, then send a fresh activation pulse; keeping the signal on does not retry the order.
Wireless request: write the command into the sender's channel content, then activate it. Changing an inactive channel's content alone does not place an order.
Invalid configuration or statement: check item IDs, group names, positive integer counts, final destinations, JSON quotes and commas. An items row uses item, not id or name.
No response: check both frequency slots, authorization and signal strength. Send a fresh positive activation; writing text alone or leaving the previous signal on is insufficient.
Request submitted means Create has accepted the request. Packages leave the network's packagers and still need your transport route to reach the destination; items do not appear inside the Logistics Mailbox.
Logistics network unavailable: check stock, Packager Links, packagers and busy packagers. If any item lacks stock or any destination cannot be planned, the whole request is rejected before dispatch.
No logistics network bound: check that the mailbox was tuned to the target network before placement. Installing frequency boards does not bind a logistics network.