If you don’t add auxiliary logistics mods such as AE, BC, EIO, etc., you will encounter a very troublesome problem when building the automatic ore processing system of GT6: you need to divert a large amount of ore into different processing flows, which is a very troublesome thing for the logistics system of GT6. Although there are filters, it will be difficult to set up. Especially for crushing ores, the crushed ores need to be separated from the stone powder first, and then enter four ore processing lines according to different needs: mercury, persulfate, firestone and sluice. The classification here is the most troublesome, especially for the sluice. Due to the large number of ores without “special processing”, it is impossible to label so many minerals in the filter. Therefore, it is generally necessary to filter out other specially procressing ores before sending the remaining minerals into the sluice. To illustrate how troublesome it is to perform this type of diversion, we will use pictures as an example below:
When you want to separate two different types of items, you usually think of a filter block (because the cover can only be marked with one), which uses a restricted logistics pipe to set priority, allowing the branch with the filter to pass first. This way, items that can enter the branch will enter the branch first, while other items cannot enter the branch and can only enter the main road:
There is a flaw in doing this: if the branch is blocked, causing items to be unable to enter the branch, the main road becomes the only feasible path, and the filtering becomes ineffective:
The only way to prevent this situation is to place a reverse filter on the main road to prevent items that should enter the branch road from entering the main road (I think this is the only way):
So, to conduct a thorough diversion, two filters need to be used each time. This will make the wiring of the logistics system very complicated. Here is what I think is the simplest classification system for crushed ores. Let’s see how troublesome it is (especially if the same list needs to be marked twice):
My opinion is that perhaps we can add an input item and output from the front if it meets the criteria, and output from the side if it does not meet the criteria, similar to a “router” block, to solve this complex filtering requirement. Given the complexity of its functionality, I believe a higher level of technology is required (requiring circuit boards and possible robotic arms, but not necessarily using crystal processors). But I’m a bit unsure if it’s realistic to add such complex blocks at the moment, and if it will make the original filter blocks less useful.
Perhaps there will be a better setting than what I have now? I’m not sure either.
Another annoying thing is various tiny ore. Due to the fact that you cannot allocate a large storage for each ore, and the boxinator is prone to getting stuck due to less than 9 remaining tiny ore, there is currently no good solution to this problem. Do you have any suggestions?
