TL;DR
1. Allow players to select the item first without an error message preventing it when setting up logistics requests for multiple qualities of the same item.2. Allow players to configure ship logistics requests for the same item from multiple worlds rather than being required to use multiple logistics groups for the same item.
3. Allow us to copy wait conditions between trains, train groups, or spaceships for different stops without bypassing the wait conditions with circuits. Currently we cannot copy wait conditions if we want to use the same wait conditions but for different stops (different worlds, or stops for different items).
1.1 What? Quality Logistics Requests
The workflow of Quality selection in Logistics feels unintuitive when setting up multiple quality requests of the same item.Choosing the item first when setting up logistics requests for multiple qualities of the same item (as in Image 1a) returns an error if you choose the item first (Image 1b), forcing you to change the Quality first, and then choose the item, to setup something like the screenshots below. The entire process is shown in the gif (Image 1c).
Image 1a
- 10-31-2024, 17-40-37.png (42.73 KiB) Viewed 872 times
- 10-31-2024, 17-40-00.png (182.95 KiB) Viewed 872 times
Image 1c
1.2 Why? Quality Logistics Requests
I believe a more intuitive implementation would be to allow the player to choose the item but only return the error of a duplicate entry when they click the checkmark to complete setting up the logistics request. That way the player is able to select the item first if they choose to.See gif Image 2c, below, where the error does not prevent creation of the request until you click the checkmark, not at the start when selecting the item.
2.1 What? World Origin Logistics Requests
The "Import from" World Selection prompt only allows requests from a single world. The same item can be requested from multiple worlds by setting up multiple logistics requests for the same item, one from each world. Because logistics groups do not allow duplicate requests, each request of the same item must be in a different group. I believe it would be more intuitive to allow the player to select multiple worlds in the "Import From:" box.We are currently unable to setup requests of the same item from multiple worlds, or in the alternative, multiple requests of the same item from different worlds in the same logistics group. For example, if I want to make a spaceship request repair packs from *any* world, the requests have to be set up in different logistics groups in order to work (Image 2a). Attempting to bypass this limitation by changing the Quality, changing the World, and then changing the quality back does not actually allow us to create the request, though it does show how my suggestion in 1. might work in regards checking for duplicate requests only when the player clicks the checkmark to complete setup (Image 2b, note error message on top of the checkmark rather than on the item in the item list).
Image 2a
- 10-31-2024, 17-50-04.png (14.69 KiB) Viewed 872 times
- 10-31-2024, 17-53-07.png (291.57 KiB) Viewed 872 times
Potential implementations that I think would be more intuitive would be:
a) *any* as an option in the "Import From" box, so that the request can be fulfilled from any stop;
b) allowing the player to select multiple worlds in the "Import From" box, which would be better than a);
c) allow the player to setup duplicate logistics requests for the same item under one section in spaceships as long as the world they're importing from is different. But this would lead to issues related to logistics groups when those groups are used on surfaces other than the spaceships.
2.2 Why? World Origin Logistics Requests
I believe allowing players to select multiple worlds in the Import From selection box would simplify certain logistics requests and feels more intuitive than setting up multiples of the same one. As a side note, allowing players to make the "Import From" selection for an entire logistics group rather than by item would be greatly appreciated.3.1 What? Spaceship Scheduling and Wait Conditions
As far as I am aware, we are not able to copy wait conditions between spaceships if we modify the stop (this is also true of train I believe).For example, if I have a spaceship with the stop below (Image 3a), and I want to create a new ship that has the same wait conditions but goes to Gleba or Vulcanus instead, I am not able to modify the stop while keeping those wait conditions. I have to readd each condition, or use circuits to send a ready signal after checking for those conditions on its own. While that is a viable workaround, I'm not sure whether requiring a circuit ready signal fits with the design of allowing players to set up those wait conditions in the first place.
Image 3a
- 10-31-2024, 18-01-51.png (60.24 KiB) Viewed 872 times
Image 3b
Meanwhile, creating a new spaceship means players have to copy each wait condition separately unless the new spaceship is using the exact same stop. For example, in the gif below (Image 3c), I attempt to use the same wait conditions that my ship to Vulcanus uses, but for Gleba. Without completely bypassing the wait condition system to setup checks with circuits sending a ready signal, there's no way to copy the settings for different stops. The same is true for train groups, and it's something that would not be solved by using the same station names because the use case is for different stations that might still have a set of uniform wait conditions you want to copy.
Image 3c