I didn't reply in the last FFF. In fact I was just waiting to see if I could think of something to provide my 2cents.
On the «Bots vs. Belts aftermath» of Twinsen:
I'm a bit surprised about some of the reactions of the last FFF because, at least for me, it was clear that the bots would stay. I mean, who would remove them from the game at this point?
I think that some people need to put themselves in the shoes of the others before saying anything.
On the «Bots vs Belts aftermath» of Kovarex
Its true that after setting up the bots you have like a «strong spell» that you can use but I think that the costs are in a different dimension.
Just from the example provided with the express belts its clear that you need an incredible amount of bots (and that's also a lot of resources).
I would prefer the belt over the bot because is cheaper, easy to set up and it does its job.
Setting up the bots in this situation requires lots of resources and power and quite frankly it looks bad compared to belts.
In paper the bots are overpowered, so what?
Belts and bots are two different systems with different mechanics and different limitations. Both can carry items around and do it well.
In terms of cost the belts win and you can lay them down fast and don't need electricity.
In terms of throughput the bots win, the reason is that you can have an incredible amount of it and they work well in relatively short distances it cannot go long distances without recharging, it costs more resources to set it up, etc. It also gives you simpler factory designs.
Two systems, same purpose, different limitations, pros and cons.
On the «Belt throughput improvements» of V453000
From the list of seven options I only see a few that could work out and I'm not quite sure either. Maybe the problem requires a new option for transporting items with different characteristics than the belt so instead of trying to force a solution maybe the solution is to not touch the belt itself.
I wouldn't mind having a belt transporting containers full of items really (I assume the container will occupy the two belt lanes). The container management will be part of setting it up.
I would limit it making that the inserter wouldn't be able to transfer the containers from the belt and use an assembler machine to do the loading/unloading process connecting a belt directly into the assembler machine.
If we want to go further we could make a new entity to be a «plastic tube» that would be able to transport containers (or a new type of container) through it at incredible speeds (greater than the trains).
Limitations:
- Can only go straight
- Cannot have underground versions (so they block paths)
- Need an assembler machine at each end (which sends/receives the container)
- The assembler can «route» the container to another tube connected to it or can load it through a belt (directly) or unload it to a belt (directly with full compression) (assembler 1 can compress to yellow belt, assembler 2 to fast belt and assembler 3 to express belt)
- The assembler must be supplied with the container through an inserter (the sender) and the receiver must take care of the container too. (and the bots could get the empty containers and put them back into the sender container of containers so it can be reused)
On the «Belt buff» of Kovarex
Awesome, now I feel more confident that I can try to do belt mixing. It simplifies some designs that I would rather maintain but I think that the change is really good.
Could it be possible to configure the splitter through the circuit network?
So you can configure when you can make those priorities and supply a list of items to be filtered?
You know, asking is free so... just giving ideas
