Dynamic filters reference
Mod version shipped with FlammiCraft: 1.13.0
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 dynamic filter rule set can be written by a channel pulse; the rules combine attributes, item names, item ids and tags.
The default rule set is empty and matches nothing. A written rule set is stored in the item and travels with the device.
Shorthand: one item per line — write a display name (Apple) or a registry id (minecraft:apple) directly. Use braces only to list several different items on one line, e.g. {Apple, Bread}. name:/id:/tag: prefixes pin down a type, lines starting with # or // are comments, and a mode: line switches the matching mode.
Apple
minecraft:apple
{Apple, Bread}
tag:forge:ingots/iron
mode:disj
Full form is one JSON object: {"mode":"disj","names":[...],"items":[...],"tags":[...],"attributes":[...]}. Each array may list different targets; attribute entries match Create's attribute filter format.
{"mode":"disj","names":["Apple","Bread"],"items":["minecraft:carrot"],"tags":["forge:ingots/iron"]}
Stock-data rule documents switch the filter to quota passthrough: only the listed references pass, counted down as items move, and exhausted entries stop passing.
Shorthand: write reference:count inside braces, separated by commas, for example:
{apple:2, minecraft:bread:1, #minecraft:logs:5}
Stock JSON: counted entries in the items array; an optional total acts as the global budget and truncated is ignored:
{"items":[{"id":"minecraft:apple","count":2}],"total":2}
Attribute quotas: write attr:<attribute entry JSON>:count to only pass items matching that attribute, for example 64 items dyed black:
attr:{"attribute":{"type":"create:has_color","value":"black"},"inverted":false}:64
total is optional; every pass decrements both the matched entry and the total budget.
A single request must fit the remaining budget (for example set the funnel extraction amount accordingly); oversized requests are rejected instead of overshooting.
Writing the rules again over the channel (or re-applying them) resets every budget; legacy rule sets without counts keep their old behaviour.
disj: whitelist, accept when any rule matches. Shorthand: mode:disj.
conj: whitelist, accept only when every rule matches. Shorthand: mode:conj.
deny: blacklist, reject when any rule matches. Shorthand: mode:deny.
With no rules the filter behaves like an empty whitelist: nothing passes. An empty blacklist also rejects everything.
Click an attribute on the dynamic filter’s left to copy its full rule JSON. Copy selected preserves the current matching mode and inverted conditions. Combine attribute objects in the attributes array; quotas use attr:<entry JSON>:count.
name: item display name, case-insensitive; quote names containing spaces. Chinese and English names both match.
id: full registry id, e.g. minecraft:iron_ingot.
tag: item tag such as forge:ingots/iron; a leading # is optional.
The filter only receives channel content after it is installed in a device filter slot; a held filter does not update.
When the device receives new channel text, the text is parsed as a rule document and replaces the whole rule set; a failed parse keeps the old rules.
The last write status is stored with the filter; hold shift to list the written rules.
One rule document holds at most 4096 characters.
Number fields accept decimals truncated toward zero; JSON enums accept ordinals 0/1/2.
At most 32 names, items and tags each; one name holds up to 64 characters.