Skip to main content

Bridge reference

Mod version shipped with FlammiCraft: 1.13.0

Overview · Main instructions

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.

Build and open

Equally oriented Bridges join as a complete rectangular screen and expand horizontally or vertically. Sneak-right-click opens configuration; ordinary right-click operates the screen. Allocate a non-overlapping region per channel; Sneak-right-click with a Wrench to remove AFN blocks.

Frequency, data and activation

Add or select channels on the left. The frequency tab configures both frequency slots, a name, value and output syntax. Ordinary items may be the secondary frequency; hover either type of board and press Space to edit. Use ${ChannelName} in output syntax to read local channels.

Changing a value and activating a channel are separate actions. Enable timers, activate-on-edit or activation conditions as needed. Output strength accepts numbers or output syntax; blank follows the trigger. Long signals use the authentication and quota rules described in Frequencies.

Layout, titles and colors

The screen tab assigns a region and interaction mode. Channel names and standby labels can be hidden separately; controls adapt to the region's dimensions. Middle-drag and scroll zoom navigate the configuration canvas.

Background sets the screen surface, Controls sets primary graphics, and Other sets remaining foregrounds such as text and needles. Lighter and darker control variants are calculated automatically.

Interaction and confirmation

Screen interaction and confirmation are configured per channel. Confirmation appears near the last operation only after an actual value change. Map pan, zoom, favorites and recenter do not change channel data. Disabling interaction also disables dialogue scrolling.

Display Output Syntax presents the channel's derived output and automatically disables screen interaction. Otherwise the raw value is shown. Changing presentation mode never rewrites stored data by itself.

Default / Text

Shows channel content. Configure choices to show buttons below the text; selecting one writes that choice into the channel. Without choices, open the direct value editor.

Switch

Accepts Boolean values, true / false text, 0 / 1 numbers and multiple components. Boolean text arrays may include brackets. Each component becomes a named switch; clicking changes only that component.

[true,false,true]

Bar chart

Accepts a number or comma-separated numeric array, with one bar per component. Configure component names, range and adjustment step. Horizontal display is a Bar option; graphics adapt to the allocated region.

Gauge

Uses the same numeric format, component names and range as bars. Multiple gauges arrange themselves around the region's center; each needle shows its component. Values can be adjusted when interaction is enabled.

12,34,56

Coordinates and point arrays

All coordinates are world x,y,z. Three numbers form one point; repeat groups of three for a flat point list, or use nested arrays. The three independent examples below show a single point, a flat list and a nested list.

0,64,0

0,64,0,32,64,16

[[0,64,0],[32,64,16]]

Named points

JSON points accept x, y, z fields or a position array. The name field is the visible map label. Put multiple points in a points array; unnamed points still render normally.

{"name":"Warehouse","position":[0,64,0]}

Multiple lines and areas

Use points, lines and areas in a root object; polygons is an alias for areas. Each line or area has its own points and name. Lines require at least two vertices and areas at least three; vertex order determines connections. Mix these types or provide just one. Channel length limits and a 256-vertex limit still apply.

{
  "points":[{"name":"Warehouse","color":"#FF7043","text_color":"#FFE0B2","position":[0,64,0]}],
  "lines":[{"name":"Route","color":"#66BB6A","text_color":"#DCE775","points":[[0,64,0],[32,64,16]]}],
  "areas":[{"name":"Work zone","color":"#42A5F5","text_color":"#B3E5FC","points":[[0,64,0],[32,64,0],[32,64,16]]}]
}

When data includes lines or areas, Show Connection no longer creates a device-to-target line. Defined geometry still renders. Coordinates and distance at the lower right use the first point and the device itself.

Geometry and label colors

Points, lines and areas accept color for geometry and text_color for names. Use #RRGGBB; omitted fields use the corresponding Bridge colors. Shape vertices inherit their shape's colors unless explicitly overridden. Also accepts #RGB, 0xRRGGBB, decimal RGB integers and [r,g,b].

Picking and navigation

Clicking still replaces the channel value with one x,y,z coordinate; it does not append to existing geometry. Nearby clicks snap to displayed points, including line and area vertices and enabled entity targets.

Scroll zooms around the cursor; hold the middle button to pan. Favorites and recenter only change map state and never ask for value confirmation. Pending picks keep the view unchanged. After submission, external updates or device movement, the view fits only if the device or target leaves the canvas.

Terrain and marker options

Choose Xaero, AFN or grid terrain, and configure background, coordinates, distance and connection separately. Entity and hostile settings control whether their screen buttons appear. Dynamic mode rotates with the Bridge's Sable structure; the configured rotation can correct its heading.

Stock

Parses Stock Mailbox JSON / Map into adaptive item icons with amounts at the lower right. Vanilla and modded items resolve by ID, short path or unique localized name. The two independent examples below are equivalent.

{"minecraft:apple":8,"create:brass_ingot":16}
{"items":[{"id":"minecraft:apple","count":8},{"id":"create:brass_ingot","count":16}]}

Logistics

Configure several item, amount and address groups. Choose a group on the screen, then Send to notify a Logistics Mailbox through this channel. These groups are independent of received channel content. Choosing a group alone does not place an order.

Text and Pager JSON

Accepts plain text or Pager JSON. avatar is the image, name the sender and message the text. messages also accepts text, Stock JSON / Map or arrays mixing them; items and amounts render as inline stickers. Item avatars use item:mod:item.

{"avatar":"item:minecraft:apple","name":"Warehouse","messages":["Arrived ",{"minecraft:apple":8}," Please collect"]}

Pager map messages

messages can mix text, stock icons and map cards. Send a map terminal's points/lines/areas object directly to a pager, or place it in messages; no wrapper is required. The explicit type:"map" and geometry format also works. Click a card in the pager to inspect it. Bridge conversations and DP radios show a map summary.

{"points":[{"position":[0,64,0],"name":"Warehouse"}],"lines":[{"points":[[0,64,0],[32,64,16]],"name":"Route"}]}

{"name":"Dispatch","messages":["See the route",{"type":"map","title":"Work route","dimension":"minecraft:overworld","geometry":{"points":[{"pos":[0,64,0],"name":"Start","color":"#ff8800"},[32,64,16]],"lines":[{"points":[[0,64,0],[32,64,16]],"name":"Route","color":"#66bb6a"}],"areas":[{"points":[[0,64,0],[32,64,0],[32,64,16]],"name":"Work area","color":"#42a5f5"}]}},"Supplies",{"minecraft:apple":8}]}

Coordinates are numerical [x,y,z] triples. Points may also use position or pos, with name, color and text_color for labels and colors. A line needs at least two vertices; a polygon needs at least three, in connection order. title names the card; dimension is a dimension registry ID and defaults to the current dimension. Each map allows 128 vertices and 16 lines/polygons in total; each message allows four maps and 256 vertices in total. The server channel-text allowance also applies. Invalid geometry remains text.

Client settings choose Xaero, then the AFN exploration map, then a grid. Unexplored locations and other dimensions use a grid. Chat only draws low-resolution previews for visible cards. Click for details, use the wheel to zoom, left- or middle-drag to pan, and reset to fit all geometry. Map messages never load distant world chunks.

History and replies

Configure avatar and name visibility separately. Show Latest Message displays only the latest entry, centered. Disable it for a history list; scroll while pointing at its region.

Write one quick reply per line. Set the outgoing avatar and name; blank fields use an anonymous identity. Clear Chat adds a lower-left button that clears chat history and the channel value.

Synaxis and computers

The Synaxis tab configures rear input, output and activation ports. The CC:T tab manages computer-visible channels. Ports and the screen share channel state; see CC:T help for computer methods.

Import and export

Use the import/export control beside the left-hand plus button to exchange channel settings, data, screen layouts and colors as .bridge files. Regions are restored where they fit; overflowing or overlapping regions are skipped. Older files preserve local layouts. Check frequencies, authentication and interfaces after importing.

Click the AFN icon above the left controls on the Xaero M-key map to open a popup. Add, name and select up to 16 channels on its left. Each channel independently configures two frequency slots, enabled, minimap and long-signal settings; multiple channels receive and display together. Older single-channel settings become the first channel. At least one slot needs an AFN frequency board. Slots reference inventory items without consuming them; hover a board and press Space to edit it. Receives the bridge map coordinate, point, line and area formats, including names and colours. Settings and the last received content are saved per player and persist after broadcasts stop and across relogs. Disabling reception hides the content; re-enabling it restores the display. No handheld device is required. Multiplayer needs the same AFN build on the server; server-side Xaero mods are not required. If the server-side AFN is missing or outdated, the button reports this instead of opening the popup.

World-map nodes, outlines and labels follow Xaero’s Waypoint Scale. Minimap nodes and outlines follow On-Map Waypoint Scale; labels follow UI Scale. Auto and Minecraft modes use Xaero’s own scale calculation. Geometry positions and coverage still follow world coordinates and map zoom.

Long signals use the existing authentication-board and Owner quota rules. Each player’s Xaero receiver counts as one device, shared by the world map and minimap; reopening the screen does not add another charge. Turning long signals off removes the registration. Otherwise, normal wireless range applies.

Screens and channels

Settings shared by every mode

Dialogue

Interfaces and files

Stock and logistics

Map: points, lines and areas

Bars and gauges

Text and switches

Xaero map receiver