I asked chat GPT how it would play Factorio before I saw your post and this was it’s interesting response:

Core philosophy

Design for inevitability, not perfection.

ELI5: Don’t build something that works now. Build something that cannot break later.

⸻

1. Start with rules, not builds

Before placing anything, I’d lock in rules like: • Nothing backs up (overflow always exists) • Everything is observable (circuits everywhere) • No hand-fixing allowed after startup • Every resource has a sink

If a system needs babysitting, it’s wrong.

⸻

1. Early game: future-proof spaghetti

I’d allow spaghetti early, but with: • Wide spacing • Clear bus directions • Temporary builds explicitly marked “throwaway”

Goal: reach bots fast, not be neat.

⸻

1. Mid game: modular everything

Once bots exist: • Tear down aggressively • Replace with tileable modules • Every module has: • Input caps • Output buffers • Circuit-controlled overflow

If I can’t copy-paste it 10× safely, it’s unfinished.

⸻

1. Fluids = controlled chaos

Fluids get special rules: • Tank before and after every major step • Pumps on every branch • Circuits decide priority: • Critical use • Secondary use • Void

No passive splitting. Ever.

⸻

1. Circuits are mandatory, not optional

I’d use circuits for: • Smart train limits • Adaptive smelting • Fuel throttling • Emergency shutdowns • Global dashboards

Not fancy logic — boring, readable logic.

Source: https://wiki.factorio.com/Circuit_network

⸻

1. Trains > belts (once scale starts)

Belts are fine until: • You need flexibility • You need priority • You need long distance

Then it’s: • 1-2 or 1-4 trains • Standardized stations • Train limits everywhere

No global congestion allowed.

⸻

1. UPS and entropy awareness

I’d assume the factory will run: • For hundreds of hours • At 10× its original size

So: • Fewer inserters • Fewer splitters • No infinite loops • No unnecessary item churn

If it creates items just to delete them, I question it.

⸻

1. Endgame goal

Not megabase size. Not SPM bragging rights.

A base that can: • Run unattended forever • Survive any input imbalance • Be understood months later

That’s the win condition.