Factorio Dashboard Exporter


Exports live factory statistics (power, machines, production, trains, logistics, resources, platforms, research) for an external dashboard. All work is spread across ticks with a hard per-tick budget, so it does not stall the game like /silent-command polling does. Data is written to script-output/fdash/ and is also available via a remote interface for RCON.

Utilities
a month ago
2.0
32
Logistics Trains Fluids Logistic network Power
Owner:
CryptoJunky11
Source:
https://github.com/boehla/factorio-dashboard
Homepage:
https://github.com/boehla/factorio-dashboard
License:
MIT
Created:
a month ago
Latest Version:
0.2.2 (a month ago)
Factorio version:
2.0
Downloaded by:
32 users

Factorio Dashboard Exporter streams live factory statistics to a second-screen dashboard — without stalling the game.

Why it exists

The usual way to pull data out of Factorio is RCON /silent-command. Every poll runs the whole query inside a single game tick: on a large modded base that means walking hundreds of thousands of entities several times a minute, all in one tick. The result is stutter.

This mod inverts the arrangement. It keeps its own view of the factory, updates it a little bit every tick under a hard budget, and hands out finished snapshots. Reading the data costs nothing, because by then there is nothing left to compute.

What it collects

  • Power: grids, satisfaction, accumulators, biggest producers and consumers
  • Machines: status per recipe — running, waiting for ingredients, output full
  • Production & consumption per item and fluid, with deficit, ratio and trend
  • Ore patches: remaining amount, depletion estimate, drill coverage
  • Trains: trains by state, station queues, goods carried (provider/requester stations)
  • Logistics: robots, logistic-network and container inventories
  • Research: running technology, queue, science-pack throughput
  • Problems: detected bottlenecks with suggested fixes, alerts, stalled entities
  • Fluids and tanks; optional container scan
  • Space Age: platforms and orbital requests

Output

Snapshots are written to script-output/fdash/ as rotating files (read via index.json, so a reader can never catch a half-written file) and are also available over RCON. The companion dashboard (ASP.NET Core API + React frontend) and an MCP server let you browse the data — or have an AI plan production and diagnose bottlenecks.

Performance

  • Hard per-tick entity budget (default 400, configurable) — the UPS cost stays where you put it
  • Entity lists maintained from build events — no repeated full-surface scans
  • Rolling ore scan, a few chunks per tick
  • Internally consistent snapshots: each collector publishes only when a full pass completes

Links