| title | Getting started | ||
|---|---|---|---|
| description | Install PyOps, sync your Factorio data, and make your first production plan. | ||
| outline |
|
This walkthrough takes you from a fresh install to a useful production plan. You will choose a project, sync its Factorio data, and make a block for one automation science pack per second.
- Factorio 2.1 installed on the same computer as PyOps.
- The mod set and startup settings you want to plan with already configured in Factorio.
- Factorio closed while PyOps performs the initial data sync.
::: info Optional: connect the companion mod You can complete this walkthrough without the in-game connection. For a plan that follows your current save, connect the Companion mod under Settings → In-game link and start Factorio from Live bridge → Launch Factorio.
The companion mod connects through PyOps' live bridge. It enables the in-game panel, live research and TURD choices, machine and production statistics, and actions such as locating a good or showing a block in-game. The navigation status changes from no game to game linked when the connection is active. :::
Home adapts to the active project. A new project shows these setup steps in order; after you have a working plan, it becomes a command center for the next block problem, factory deficit, build shortfall, data drift, and game-link state.
- Install PyOps.
- Choose or create a project for this factory or mod set.
- Sync game data from Factorio into that project.
- Build your first block and choose its recipe and machine.
- Read the Factory view to decide what to plan next.
::: info What PyOps changes PyOps reads Factorio's prototypes during sync and stores its own plans locally. It does not change your save during this walkthrough. :::
A project is a separate PyOps database, usually for one save or one mod set. A block is a production unit with a target output, selected recipes, and selected machines. The Factory view combines the solved flows from your enabled blocks so you can see what the whole plan produces and still needs.
You do not need to describe the entire recipe chain up front. Start with the product you want, solve one useful block, and use its imports as the next planning decisions.