[–] 5 points 8 months ago* (1 child)

More generally, just remember to always use even numbers for both lanes and gaps. I usually template out where the spaces will be with stone bricks early on, spaced so there's always an alignment guide on screen.

  • source
  • parent
  • context
  • [–] 3 points 8 months ago

    I've written down in my notes to always build out one side of the bus first before doing the other side. I never remember why, so I ignore the rule. Then this happens. Every single time.

  • source
  • [–] 13 points 8 months ago (2 children)

    I always wire the final inserter to the roboport and set it to only function when the amount of available bots in the network is 0.

    Same effect, but doesn't add in excessive bots.

    I do the same for construction bots and repair packs, although repair pack logic is local, not network-based.

  • source
  • parent
  • context
  • [–] 10 points 8 months ago (3 children)

    I never really had a 'main bus' like this.

    My main production centers were all more dendritic in nature -- from raw resource to finished product, never sharing anything with any other finished product's production line. If two different finished products needed, say, green circuits, then I would have two green circuit production lines to feed each of those independently, and so on and so on, all the way to raw resource extraction.

    (And on my second playthrough, also just an absolute ton of logistics bots flying around. Thousands of them. Did you know that you can make an assembly line for them feed right into a robo-port? I just constantly had more logistics bots being added to the logistics system at all times. Anytime something needed to get from somewhere to somewhere else in relatively low volumes, it was provider/requester chests to the rescue, and then just let the massive bot network handle it.)

    But I suppose one big benefit of doing things this way is that I would rarely have huge lines of parallel conveyors like this. Most conveyors were only singles or doubles, at most.

  • source
  • [–] [S] 2 points 8 months ago

    The main problem would be the power draw dilemma and it unfortunately buffing small poles (which suck because they need wood and thus can't be automated gracefully).

    It could be solved by just removing the power draw of lights, of course. Handwave it by saying it's powered by whatever powers belts.

  • source
  • parent
  • context
  • [–] [S] 2 points 8 months ago

    It absolutely would be illogical. So is the ability to carry 50 nuclear reactors in your backpack, each of which was crafted faster than a car engine. Green chips are made out of exclusively copper and iron (both conductors).

    Fuck logic. Tell me if you think it's a good gameplay idea.

  • source
  • parent
  • context
  • [–] 4 points 8 months ago (1 child)

    Would that not be illogical? These are all machines that do not care about "seeing", and do not even need a human to be around on the same planet to operate. We do need lights to navigate around the place, that is what the torchlight on your helmet is for.

  • source
  • [–] 2 points 8 months ago

    It's one of the nice features of space age that it encourages sushi in a few situations, Fulgora probably being the obvious one that most players will recognise.

    Congrats on completing the game, you're ahead of me in that regard!

  • source
  • [–] 5 points 8 months ago

    For those curious, they used a neat trick to pick the "tail" up quickly:

    Rotate the two oldest belts in parallel. Put down a splitter to replace the two belts. Put down a single belt to replace the splitter.

    This effectively removes one belt instantly.

  • source
  • parent
  • context
  • [–] 10 points 8 months ago (1 child)

    Requiring lights near all buildings is the same gameplay problem as fitting power poles in your designs. Why not kill two birds with one stone by having medium and up power poles have integrated "streetlights" that light up an area.

  • source
  • view more: ‹ prev next ›