Skip to main content

Frequencies 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.

A frequency is an AFN wireless address. Senders transmit to a frequency and receivers listen on the same or a matching address.

Most devices have two frequency slots, primary and secondary. They form one frequency group and match as a whole.

Receivers store literal paths; only senders interpret wildcard and exclusion syntax.

A frequency is a dot-separated wireless address. Its layers form one complete address and do not match separately.

1 / 1.1 / 1.1.1 / site01.room1.gate

On the receiver a frequency is a literal address: the primary, the secondary and every enabled alias together form that device's reception-path set, and wildcards or exclusions are not allowed in it.

On the sender a frequency is a selector: it is still a path, but wildcards and exclusions let one selector cover many reception paths at once.

The match mode compares the whole set: OR (default) activates when the primary or any alias is covered; AND requires the primary and every enabled alias to each be covered by at least one send selector.

Cross-layer response is a receiver option: it accepts shorter parent sender addresses. Enabling it only on the sender has no effect.

A reusable Frequency Board stores a primary frequency and optional aliases. An Authentication Board adds an Owner and ACL for identity checks.

Bounds: at most 128 characters, 16 layers and 48 characters per layer; |, whitespace and control characters are rejected, and localised punctuation is normalised to ASCII.

Wildcards and exclusions belong to send selectors only; receiver addresses must be literal paths, and strings containing a wildcard or exclusion cannot be saved as a reception address.

  • matches any number of characters inside one layer (including zero) but never crosses a dot.

A380.CABIN.* matches A380.CABIN.DOOR_1 but not A380.CABIN.DOOR.1

? matches exactly one character of that layer: not zero, not two.

door.0? matches door.07 but not door.7 or door.007

[A-C] matches one character from the set and supports ranges (start must not exceed end); empty [], nested [ and dangling ] are rejected, as is a leading -.

** must occupy a whole layer and matches zero or more complete layers.

factory.**.chest matches both factory.chest and factory.a.b.chest

*, embedding ** within a layer (such as ab), and adding exclusions to ** are invalid.

Write exclusions as *!VIP!CREW or *.!VIP!CREW; they apply only to the corresponding pattern layer.

*.!VIP!CREW keeps the broad layer but immediately rejects the values VIP and CREW

An exclusion is a literal value in one layer: it cannot be empty, contain a dot, or be **. Exclusions cannot be added to a literal-only layer without *, ? or [..].

Matching is case-sensitive; wildcards do not use regular-expression syntax.

Rule of thumb: receivers pin addresses, senders describe ranges; * covers one layer, ? one character, [..] a character set, ** many layers, and .! adds exclusions inside the previous layer.

A frequency board stores one complete wireless address in a reusable item; right-click to edit its primary frequency and optional aliases.

One board replaces the two frequency items a Create redstone link terminal would need.

Auth boards use the same editor but must be bound to an owner before use.

Bind once in the GUI; the server treats the owner UUID as authoritative and only shows the name.

Only the owner edits the ACL; READ allows viewing and permitted identity actions, WRITE also edits frequencies, titles and device sender configuration.

An unbound auth board is not a valid credential and cannot initialise protected devices.

Two plain frequencies keep their native order; swapping the whole group no longer matches.

When either side contains an AFN board the two frequencies may swap positions as a group.

Relaxed ordering does not ignore content: every path in the group must still match.

Plain receivers add no identity lock and may accept authenticated senders when paths match.

Auth receivers reject plain senders without an owner; the sender owner must be the receiver owner or on its ACL.

With multiple auth slots on the receiver, one sender owner must be allowed by every lock.

Signal strength is 0-15; distance and angle attenuate it, and directional mailboxes receive by incidence angle.

Frequency field hint:

Send: * one layer, ** many layers, *.!X!Y exclude the previous layer

Long signals: unlimited range without manually loading chunks; configure them with an Authentication Board.

Long signal keeps the chunk or physical structure loaded and consumes owner quota; devices enable it only after confirmation.

Mailboxes have receive, transmit and transceive modes; transceive does not loop received signals straight back.

Timed sending only ticks while the chunk is loaded; disabling it falls back to manual sends.

Long-signal devices must reconfirm custody after switching modes.

A bridge groups a named channel with a frequency and value: primary, secondary, match mode and reception mode.

A channel value may be empty (no value), "" (empty text), true/false, a comma-separated real array, or plain text.

Named channels are readable as ${channel} inside the structured output syntax to combine data across devices.

These are bounded matchers, not Java regex: empty exclusions, *** and invalid character sets are rejected.

[A-C] matches one character restricted to A, B or C; SECTION_D is not in the set.

1 / 1.1 / site01.room1.gate

.!X!Y attaches layer-local exclusions to the previous pattern layer: *.!VIP!CREW stays broad but rejects VIP and CREW immediately.

Dots split an address into layers: 1.1 has two layers, 1.1.1 has three. Layers are part of the address, never matched on their own.

? matches exactly one non-dot character, so door.0? can reach door.07.

A send selector matches only when it lands on a literal path the receiver exposes.

  • matches any number of characters within one layer and cannot cross a dot; A380.CABIN.* does not match A380.CABIN.DOOR.1.

** occupies a whole layer and may span zero or more layers.

Enabled aliases add complete reception paths instead of replacing the primary frequency.

In AND mode the receiver's primary and every enabled alias must each be covered by at least one send selector.

AND compares the reception path set with the sender selector set; aliases are never concatenated into one long address.

Without cross-layer reception a deeper receiver (site01.room1.gate) does not accept the shorter sender address site01.

Enabling cross-layer reception on the receiver lets parent sends arrive; it is a reception rule and enabling it only on senders changes nothing.

The exact send selector 1.1 reaches the literal receiver address 1.1.

In the default OR mode a receiver fires when the primary or any enabled alias matches.

What a frequency is

Frequency boards and auth boards

Bridges and named channels

Frequency format

Device modes

How frequencies are organised

Layers, aliases and match modes

Signal and long signal

Slot order and identity

Wildcard rules