Create:Advanced Frequency Network

Create: Advanced Frequency Network (AFN)

Video tutorials (Bilibili） · AFN WIKI

MC百科 · CurseForge

Update for 1.1.5 ：

For server stability, temporarily remove the Carrot Signal Terminal.

About the mod

Added channel configuration for no-distance-limit dynamic chunk loading based on signal strength and physical device loading.）

Create: Advanced Frequency Network extends Create's wireless redstone system with more flexible frequency editing, matching, and management:

1. Use English letters, digits, and Chinese characters to define frequency bands, with compatibility for wireless redstone devices in Create and its add-ons.

2. Use dots to organize hierarchical frequency bands, and provide a personal history library.

3. Use wildcards, character sets, and local exclusion rules to match signals.

4. Introduce a complete signal permission control system to prevent signal hijacking.

5. Introduce wireless information transmission into Create, allowing, beyond the traditional 0–15 discrete integer values for wireless strength, the transmission of text, real-number arrays, Boolean values, and Synaxis-mappable structured data, offering great development potential.

6. Compatible with Synaxis, Aeronautics, and CC:Tweaked, and adapted to Aeronautics' physicalized devices.

7. In any GUI, press the spacebar to edit the frequency band, faster and more convenient.

8. Added channel configuration for no-distance-limit dynamic chunk loading based on signal strength and physical device loading.

Frequency network

• Organize large wireless networks with hierarchical frequencies such as factory.production.line_01. English letters, numbers, and Chinese characters are accepted; dots separate levels.
• A regular frequency board stores one primary frequency and up to five aliases. Aliases can be evaluated with OR or AND logic.
• Supported matching syntax includes ?, single-level *, cross-level **, character sets such as [A-C] / [0-9], and local exclusions ! that apply only to the immediately preceding level.
• The history library stores literal addresses by hierarchy. After one character is entered, it suggests entries from the current level.
• An authenticated frequency board provides an Owner, READ / WRITE ACLs, and an optional installation lock. Players without permission cannot view the hidden primary frequency.
• With Create Engineer's Goggles equipped, players can see frequency labels that they are allowed to read in the world.

Local exclusion example

1.2.[1-9].!1!2!3![4-8].[2-4].!2!3

Each ! excludes only the shorthand item in the immediately preceding level, so the expression above ultimately matches only 1.2.9.4. Character sets are case-sensitive; [A-Za-z0-9] combines upper-case letters, lower-case letters, and digits.

Mailbox

The mailbox is a single-channel wireless device with the same signal receiving and sending abilities as a wireless redstone terminal. While carrying a signal, it can also retain an attached value on the receiving side.

The mailbox can read from or write to the sources and targets supported by Create's Display Linker.

Optional output targets

Output target	Output target	Output target	Output target
Glow display	Flap display	Sign	Lectern

Optional input sources

Input source	Input source	Input source
Seat	Depot	Glow display
Stockpile switch	Smart Observer	Andesite Tunnel
Brass Tunnel	Train Observer	Train Station
Cuckoo Clock	Stressometer	Speedometer
Fluid Tank	Factory Gauge	Conveyor Belt
Enchanting Table	Respawn Anchor	Command Block
Target	Jar	Display Stand
Globe	Notice Board

After automatic writing or automatic output is configured, the mailbox can read information from its attached block or write its stored information to that block. The two options cannot be enabled at the same time. In send or send/receive mode, powering the mailbox with redstone sends the current value on its configured frequency.

The mailbox uses AFN frequency matching and supports wildcards, character sets, local exclusions, aliases, and authentication.

AFN Bridge

The bridge is a standalone multi-channel controller. Each bridge stores up to 64 channels and can combine player interaction, redstone input, CC:Tweaked, Synaxis, and wireless sources. The standard bridge has a built-in CRT; the 2×1×2 Big Bridge exposes the same functions as a touch-operated world display.

Each channel uses one unified structure:

channel name + primary frequency + optional secondary frequency + optional value + activation state

• With no primary frequency, a channel can still be stored, displayed, and edited locally, but it does not join the wireless network.
• The secondary frequency has three modes: none, manual frequency, and auth board. If the selected auth board is invalid, wireless registration fails closed.
• A channel value can be text, a boolean, or an array of 1–7 finite real numbers. Text is limited to 1,024 Unicode code points and 4,096 UTF-8 bytes.
• No value and the empty string "" are different: clearing a value removes the payload; an empty string is a real, present text value that can be synchronized.
• Writing a value does not activate a channel, and activation does not require a value to exist.

Tickets and access control

• The invoice machine uses an auth board to batch-issue or unbind tickets; tickets from the same batch stack up to 64.
• A ticket displays its title and issuer. The primary frequency required for validation is never shown in the item tooltip.
• The ticket validator checks the frequency and ACL first, then stores the ticket in its 27-slot retained-ticket inventory. If the inventory is full, the ticket is not consumed and access is not granted. The inventory can interact with hoppers and Create chutes.
• The ticket validator, auth card reader, and identity pillar can output a 20-tick redstone pulse and can send an unordered dual-frequency signal composed of a regular frequency and auth identity.
• Status lights remain dark while idle, glow green on success, and glow red on failure.

Wireless value boundaries

• AFN Bridge → AFN Bridge: activation strength and an optional value travel across the same permitted wireless connection.
• AFN Bridge → regular Create device: regular devices process only strength 0–15 and ignore values.
• Regular Create transmitter → AFN Bridge: can activate a matching channel, but cannot overwrite its value.
• Wireless input is not automatically retransmitted, preventing an A → B → A relay loop. Wireless TX is driven only by local sources such as redstone, players, CC:Tweaked, or Synaxis.
• When several sources are active, the highest strength wins. For value-bearing sources, a stable source identifier selects one winner using the strength and arbitration rules.

CRT and world display

Default, switch, bar chart, gauge, and map are five interpretation views, not five storage types. If a value cannot be interpreted by the selected view, the view falls back visually: a switch shows off, charts show 0, and a map shows only the device position. A normalized value is written only after the player actually touches the control.

The screen can use the system activation list or a saved custom display order. The detailed map supports zooming, point selection, and favorite points. It reads client-loaded terrain at a low frequency and never generates or force-loads chunks just to draw the map. Integer interaction affects only player screen input; it does not change the precision of regular GUI, CC:Tweaked, Synaxis, or wireless writes.

Redstone bindings use front, back, left, right, up, and down relative to the front of the screen. An all-directions option is also available, as is an exact-strength or all-strength option. One input can activate multiple channels at the same time.

Optional integrations

CC:Tweaked 1.118+

An adjacent computer or a wired network can connect to the afn_bridge peripheral. The four physical blocks of a Big Bridge map to the same peripheral instance. The mod provides:

local afn = require("afn")

-- 15 strength, 20 ticks; sends wirelessly when a primary frequency is valid
local pulse = afn.pulse("door")
assert(pulse.success, pulse.error)

-- A simple overwrite does not require reading revision first
local changed = afn.set_value("door", "OPEN")
assert(changed.success, changed.error)

-- No value and empty text are different
assert(afn.set_value("door", "").success)  -- present empty text
assert(afn.clear_value("door").success)    -- remove the value

Pass revision only when using a read → compute → write sequence and you do not want to overwrite a concurrent update:

local current = assert(afn.value("counter"))
local changed = afn.set_value("counter", current.value + 1, current.revision)
if not changed.success and changed.error == "revision_conflict" then
  printError("The value changed; read it again")
end

Without an auth board, every non-negative ComputerID is admitted. After an auth board is installed, the bridge checks the auth-board ComputerID allowlist; an empty allowlist rejects every computer. Read, activation, and configuration capabilities remain independent. Policy changes are pushed to connected sessions; ordinary function calls read an O(1) session cache instead of scanning the world, NBT, ACL, or allowlist each time.

Lua cannot submit an Owner, ACL, hidden auth frequency, or forged authentication identity. Auth secondary frequencies and temporary authenticated transmissions use only the bridge's own valid auth board.

afn function index (43 functions)

Every function accepts the optional CC peripheral name bridge_name as its final argument; omit it when only one bridge is connected.

Discovery and reads

1. afn.find([name])
2. afn.channels([bridge_name])
3. afn.active([bridge_name])
4. afn.display_channels([bridge_name])
5. afn.get(channel[, bridge_name])
6. afn.state(channel[, bridge_name])
7. afn.value(channel[, bridge_name])
8. afn.channel_value(channel[, bridge_name]) (value alias)
9. afn.information(channel[, bridge_name]) (legacy read)
10. afn.frequency(channel[, bridge_name])
11. afn.last_error(channel[, bridge_name])

Activation and values

1. afn.set(channel[, strength[, bridge_name]])
2. afn.pulse(channel[, strength[, ticks[, bridge_name]]])
3. afn.toggle(channel[, strength[, bridge_name]])
4. afn.clear(channel[, bridge_name])
5. afn.clear_all(channel[, bridge_name])
6. afn.set_value(channel, value[, revision[, bridge_name]])
7. afn.set_channel_value(...) (set_value alias)
8. afn.set_information(...) (legacy alias)
9. afn.clear_value(channel[, revision[, bridge_name]])
10. afn.clear_channel_value(...) (clear_value alias)

Primary frequency, secondary frequency, display, and configuration

1. afn.set_primary_frequency(channel, frequency[, bridge_name])
2. afn.set_secondary(channel, mode[, frequency[, bridge_name]])
3. afn.get_display_channel([bridge_name])
4. afn.set_display_channel(channel[, bridge_name])
5. afn.next_display_channel([bridge_name])
6. afn.previous_display_channel([bridge_name])
7. afn.set_channel_displayed(channel, displayed[, bridge_name])
8. afn.set_display_channels(channels[, bridge_name])
9. afn.create_channel(definition[, bridge_name])
10. afn.update_channel(channel, changes[, bridge_name])
11. afn.remove_channel(channel[, bridge_name])
12. afn.set_channel_type(...) (legacy projection)
13. afn.set_information_subtype(...) (legacy projection)

Synaxis, redstone, and temporary sending

1. afn.set_synaxis_activation(channel, enabled[, format[, x, y[, bridge_name]]])
2. afn.set_synaxis_receive(channel, enabled[, format[, x, y[, bridge_name]]])
3. afn.set_synaxis_publish(channel, enabled[, format[, x, y[, bridge_name]]])
4. afn.bind_redstone(channel, side, strength[, bridge_name])
5. afn.unbind_redstone(channel, side[, bridge_name])
6. afn.transmit_temporary(frequency[, strength[, attach_auth[, bridge_name]]])
7. afn.pulse_temporary(frequency[, strength[, ticks[, attach_auth[, bridge_name]]]])
8. afn.clear_temporary(handle[, bridge_name])
9. afn.clear_temporary_all([bridge_name])

All channels are always valid. receive_enabled=false disables wireless input only; true allows both sending and receiving. New channels default to receive_enabled=true and displayed=true. New programs should read schema_version, receive_enabled, primary_frequency, secondary_mode, secondary_frequency, value_present, value_kind, channel_value, and value_revision. The legacy type/subtype/value/attach_auth snapshot fields and information functions remain for a compatibility period, but cannot fully represent a channel that has both a primary frequency and a value. Raw peripheral methods use indexes 0–38.

Synaxis

Each channel can independently expose three stable port types:

• Activation input: controls only 0–15 activation strength; supports Real / Boolean.
• Value input: writes the channel value; does not activate the channel.
• Value output: publishes the channel value; does not activate the channel. If conversion is impossible, the selected Schema's safe default is published.

Value ports support Real, Boolean, Vec3, and Quaternion. Synaxis requires the schemas at both ends of a connection to match, so select the port format before wiring. A short array overwrites the front of the existing array and preserves its tail; a longer array extends the value. Output truncates extra components and fills missing components; a missing Quaternion w is filled with 1. Pose / Twist remain save-compatible only and cannot be created; Bundle is not supported yet.

Dependencies and compatibility

• Required: Minecraft 1.21.1, NeoForge, and Create 6.0+.
• CC:Tweaked and Synaxis are optional integrations; AFN's core features remain available without them.
• AFN extends Create's public dual-frequency wireless link. Third-party devices that bypass that link and implement a separate communication system are outside the automatic compatibility scope.