Network Monitor
Mod version shipped with FlammiCraft: 0.51.0
The Network Monitor measures confirmed deliveries in item, fluid and energy networks. It carries no resources itself and needs no port configuration on the adjacent bundle. Chemical and redstone networks are not measured.
Placement and controls
- Craft it from five iron ingots, one glass block, two redstone and a comparator, or take it from the mod's creative tab.
- Place it directly beside a conduit bundle and right-click it.
- Choose the direction from the monitor to the bundle, then Items, Fluids or Energy. A missing type or unloaded adjacent bundle produces an explicit disconnected message.
- Select channel 0–15 for items or fluids; hover its button for the color name. Energy has one shared uncolored total.
- Select Endpoints for configured source/target coordinates, the direction from conduit to target and loaded status. Arrows page through six endpoints at a time. Throughput returns to the graph. Escape closes the menu.
The first measurement needs 20 game ticks after the full access check completes. Rates are delivered items, mB or FE per 20 game ticks, rather than wall-clock seconds during lag. Simulations, extractions and retained remainders are not deliveries. Retried retained contents count when actually accepted. The chart holds up to ten completed measurement windows; hover a bar for its value. Bar heights scale to the largest visible value.
Hints from actual transfer decisions
- Source offered nothing: the transfer path obtained no extractable offer. The source may be empty or deny extraction; the monitor does not add inventory probes to distinguish them.
- Filter rejected an offer: an actual extraction or insertion filter rejected the entire offer.
- Target rejected all or part: an offer could not be fully accepted. Full storage, machine rules or access restrictions can cause this; the hint does not claim a unique cause.
- Transfer budget reached: an observed source or path reached its available conduit budget. This alone does not establish a sustained bottleneck.
- No active destination route: a processed source had no active destination route.
Hints describe the last completed measurement window and can concern different endpoints on the same channel. Idle or redstone-disabled sources may produce no transfer attempt. Machines push energy into conduits; empty energy sources and their filters cannot be diagnosed from these calls. No observed hint is not proof that the network has no problem.
Access, unloaded chunks and lifecycle
The view requires normal interaction rights at the monitor and read access to every conduit and attached endpoint in the selected network. TDClaim and interaction vetoes are respected. If any part is protected, totals and history are hidden too. Every new report performs a new access scan without reusing completed permission decisions between scans.
Each open menu checks at most 16 network nodes per game tick. Large networks therefore take longer to show their first report and refresh less often. During a follow-up check the last completed report stays visible until the new result replaces it; if the network changes meanwhile, the check restarts without interrupting the view. The checking state returns only when follow-up checks fail to finish for clearly longer than usual. Changing the side, network type, channel or page always starts a new visible check. No chunks are loaded. Unloaded endpoints use stored descriptions and appear as Not loaded; rates count actual executed transfers. Missing old descriptions hide totals until those chunks have loaded normally and access can be checked.
Viewers of the same network share counters and history but receive separate access checks. The last closed menu stops collection and discards history, which is never saved to the world. Restarting or reopening begins a fresh observation. Topology, port configuration or attachment changes reset history; redstone signal changes alone do not. Breaking or moving the monitor closes its menus. Moving out of reach, changing dimension or losing the monitor also stops observation.
With no open monitor there is no collection, scan, retained history or monitor packet traffic. Transfer paths keep only their active-observation check.
Optional redstone alarm
The top-right switch initially reads Alarm: Off. Players with configuration rights at the monitor and a fully authorized view can enable it. Alarm: On (15) means at least one authorized open view of this block reports one of the hints above from a completed measurement window. The block then emits redstone strength 15 on all six sides and the graph and status lamp on both screen faces turn red. Otherwise the switch reads Alarm: On (0). Click again to disable it.
Each view contributes its currently selected transport type and channel. Multiple players or channels combine with OR. Changing a channel, running a full recheck or losing access withdraws that view's contribution. Closing the last view sets the output to 0. The first measurement window also keeps output at 0. Other authorized views can continue to hold the output active.
The alarm works only while views are open. It starts no continuous background measurement and loads no chunks. Output 0 is therefore not proof of a healthy network. This alarm is not intended for unattended automation. The enabled/disabled mode persists in the block state; measurement data and alarm contributions are never saved. Restarting or reloading starts at output 0 until an authorized open view reports a new hint. Breaking and placing the block starts with the alarm disabled.
The monitor now has a block entity without a ticker for transient alarm contributions. Vanilla pistons therefore cannot move it; break and place it to relocate it. Existing monitor blocks start with the alarm disabled.
Validation status
Automated tests cover counting, partial acceptance and retries, sample windows, access revocation, pagination, multiple viewers, alarm contributions, reload reset and collector release. Runtime acceptance still needs real inventory/tank/energy spot checks, GUI/rendering, alarm wiring, dedicated-server startup, restart, chunk transitions and an MSPT comparison with closed and open monitors. Clients and servers must use matching conduit protocol 10.