When I add the World Collider to the build queue, it shows how many segments are remaining (in that queue item), and two times - one for building the current/next segment, and another for completing the whole queue item. This is the same for building the Bioseeder Ship and probably other things that I've forgotten about or not yet discovered in the game.
However, when I add an ARPA project to the queue (like a Supercollider or a Stock Exchange), it shows as one item and only one time. I would prefer to see this the same way as other multi-segment items show with a count of how many "segments" are remaining, and a time for both the next/current segment and the total item.
I think it makes sense that there still only be one item in the queue per full project, not broken down into smaller parts. I mean to say that when adding a project to the queue, there should be 100 segments remaining or fewer for the item at the front of the queue if the project isn't at 0%. This may get complicated when changing the order of items in the queue, as the first queue item should always have the possibly-lower count, whereas all others should stay at 100.
Implementing this should reduce the complexity in the queue processing logic as it should remove the special handling of ARPA projects there.
When I add the World Collider to the build queue, it shows how many segments are remaining (in that queue item), and two times - one for building the current/next segment, and another for completing the whole queue item. This is the same for building the Bioseeder Ship and probably other things that I've forgotten about or not yet discovered in the game.
However, when I add an ARPA project to the queue (like a Supercollider or a Stock Exchange), it shows as one item and only one time. I would prefer to see this the same way as other multi-segment items show with a count of how many "segments" are remaining, and a time for both the next/current segment and the total item.
I think it makes sense that there still only be one item in the queue per full project, not broken down into smaller parts. I mean to say that when adding a project to the queue, there should be 100 segments remaining or fewer for the item at the front of the queue if the project isn't at 0%. This may get complicated when changing the order of items in the queue, as the first queue item should always have the possibly-lower count, whereas all others should stay at 100.
Implementing this should reduce the complexity in the queue processing logic as it should remove the special handling of ARPA projects there.