this post was submitted on 20 Sep 2024
45 points (97.9% liked)

Satisfactory

1364 readers
1 users here now

The unofficial Lemmy community for Satisfactory, the factory-building and exploration game.

Useful Links:

Looking for Group?

@[email protected] started a dedicated server and welcomes Fediverse users, find out more by DMing them or joining this steam chat

Rules

  1. No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
  2. Be respectful, especially when disagreeing. Everyone should feel welcome here.
  3. No NSFW content
  4. No ads/spamming

founded 1 year ago
MODERATORS
[email protected]
[email protected]
45
What methodology do you prefer? Monolith factory or microfactories (self.satisfactory)
submitted 2 months ago by notnotmike to c/[email protected]
33 comments fedilink hide all child comments
 

My friend and I routinely have conversations about factory design.

His ideal factory ships every ore in its raw state to a single building, which can then move the ore to different floors/sections for processing. He goes further than most and separates each product into its own "room", so all steel bars are made in one room then shipped to the steel beam and steel pipe rooms. Importantly the factory should be designed so that you can "infinitely" expand a room if you need more of that resource.

I prefer what I call "microfactories", where each component is created in a small, independent factory and the result is shipped to a main repository for builder use and for the space elevator construction. If you need modular frames, for example, you would find a group of ores and build a small factory on it and build every sub-component you can in it. Ideally, it would not rely on any other microfactory's outputs, but sometimes that's easier said than done. Often I will have a small cluster of microfactories all dedicated to shipping their output to a final microfactory for processing.

So what do you all use?

Note: He claims his design is more analogous to microservices (from software architecture) than mine, and that mine is something apparently called "pirate architecture". I think he's out of his mind on that one.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 month ago* (last edited 1 month ago)

I very much lean towards the microfactory approach - locate a cluster of resources within reasonable belting/piping distances, design a factory which can consume the cluster's entire production of the limiting resource (clocking others to match) to make 1 output or maybe 2, then provide that output to the rail network. Some production chains make it easier to have certain inputs taken from the rail network.

Within one of these factories, items are refined further for each floor they ascend but I rarely enforce a 1 product/floor rule - in particular I find it convenient with many Assembler/Manufacturer recipes to have an input that is directly fed from a single Constructor using clock speed to match production with consumption. This usually means each microfactory underclocks its most power hungry buildings a fair bit which keeps their consumption moderate. Each microfactory ideally has a single priority power switch to turn off its entire production chain if its consumption is becoming a problem and I set up a priority sequence for them.