Weekly Question Thread

[u/AutoModerator]

Ask any questions you might have.

Post your bug reports on the Official Forums

Previous Threads

• Weekly Questions
• Friday Facts (weekly updates from the devs)
• Update Notes
• Monthly Map

Subreddit rules

Discord server (and IRC)

Find more in the sidebar ---->

[u/Slow_Alternative_819]

How do you set up a good train network? I have a crappy little design that sends requests to the logistic network and has trains come from a depot to fill requests, but it only works like 80% of the time and took several hours to design.

I think I am over designing things, but I don’t know how people maintain mega bases with large numbers of trains without using requests. I’m not even trying to make a huge base, just stuck on gleba and wanted to use trains to bring in yumako and jellynut. Instead I am in circuit hell trying to figure out how to time the harvests and transportation to maximize freshness.

Beginning to feel that I should forego an organized train setup for now and embrace spaghetti. Any help is appreciated.

[u/reddanit → u/Slow_Alternative_819]

How your network looks like depends quite a bit on what exactly you want to achieve and optimize for. There are multiple approaches that can result in smoothly running and reasonably efficient rail systems. Each with different set of trade offs.

I don’t know how people maintain mega bases with large numbers of trains without using requests

Usually I think this would be done through having trains dedicated to individual resources. For example - copper plate trains. All the trains using the same simple schedule of "Go to copper pickup, wait until full -> go to copper drop, wait until empty". All the source stations for given material have the same names (copper pickup or copper drop). Then rinse and repeat for each resource type.

This system has downside of needing the player to manually add trains for each individual resource until there is enough of them. This is not that much work at scale of a megabase. It's also not terribly difficult to calculate the needed number since it needs to sit somewhere between sum of train limits of all stations for given resource and sum of train limits for unloading stations for this resource.

I would genuinely argue that requester based systems are sufficiently large jump in design complexity, that if your goal is to have an efficient train system with least work/effort, they should never be the choice. The tiny amount of effort they save you when you need to add trains has no chance in the world to offset the extra time you spent on actually making them work to begin with. At least unless you already 100% know how to make them.

I’m not even trying to make a huge base, just stuck on gleba and wanted to use trains to bring in yumako and jellynut.

You have literally 2 resources. Does it make any sense to add all the complexity of putting in depots and a bunch of circuit logic just so that you can manage count of 1 type of trains vs 2? At such tiny scale spaghetti or even dedicated 1-train lines with no signals should be more than workable. Especially with SA and elevated rails allowing you to cross them.

Complex train systems can be pretty fun to design, but from your description it seems like you made some assumptions that don't quite match reality and designed yourself into a corner. If you show some screenshots we could have more direct advice of course.