Code: Select all
TL;DR:
If custom minimum payload is enabled, mixed rockets should also respect it.This applies to both mixed and exclusive rockets:
- in a mixed rocket, the most requested item can fill the remaining free capacity
- in an exclusive rocket, there is only one item, so that item fills the whole rocket
The part that feels inconsistent is when custom minimum payload is enabled. Right now it seems to act like a real minimum payload for exclusive rockets, but not for mixed rockets.
For example, if I request 1 red circuit, I may receive either:
- 1 red circuit in a mixed rocket
- 1000 red circuits in an exclusive rocket
Because of that, I think the checkbox should be treated as an override away from auto behavior:
- unchecked: auto behavior, as it works now
- checked: the selected value is respected as an actual minimum payload
The setting should also be renamed to something like “use minimum payload”, since there is no real default minimum payload anymore in the old sense.
Why is that needed?
Example 1: controlling which item gets the exclusive rocket
Let’s say I have a ship going from Nauvis to Gleba and back repeatedly. When I leave Nauvis, I want at least 500 iron in the ship inventory to craft ammo during the flight. Additionally, I want one-time deliveries of exactly 500 copper and 500 solid fuel.
I set the requests to:
- 500 iron, custom minimum payload: 1000
- 500 copper
- 500 solid fuel
Because mixed rockets do not respect the custom minimum payload, two items get combined in one mixed rocket, and the last pseudo-random item gets sent with an exclusive launch of 1000.
So it is not guaranteed that the exclusive rocket is the iron rocket, even though I specifically set iron to a custom minimum payload of 1000.
Expected behavior:
Iron should require an exclusive rocket, because a payload of 1000 cannot fit into a shared rocket. Copper and solid fuel can still use the automatic mixed rocket logic.
Example 2: custom minimum payload below full rocket capacity
I set the requests to:
- 500 iron, custom minimum payload: 800
- 500 copper, custom minimum payload: 800
- 500 solid fuel, custom minimum payload: 800
Two of them can still get combined in one mixed rocket, and the last pseudo-random one gets sent with an exclusive launch of 1000. Effectively, two items are delivered below their custom minimum payload.
Expected behavior:
None of them should be sent as a 500-item delivery in a mixed rocket. I would expect three deliveries that each respect the configured minimum payload, so in practice three exclusive rockets.
Example 3: one-time delivery workaround
I want to deliver 815 red circuits once: 800 to craft 400 logistic bots on my Gleba ship, and 15 to drop to Gleba afterwards.
Previously I could work around missing one-time deliveries by requesting 1 red circuit, setting the custom minimum payload to 815, and keeping 15 red circuits in cargo so the request stayed fulfilled afterwards.
In 2.1 this no longer works if the request is handled by a mixed rocket, because it can deliver only 1 red circuit instead of respecting the custom minimum payload of 815.
Expected behavior:
If I request 1 red circuit with a custom minimum payload of 815, the delivery should still be at least 815 red circuits. If that does not fit into the current mixed rocket, the request should not be included in that mixed rocket.
Overall, I think the new auto behavior makes sense. But when custom minimum payload is enabled, I would expect it to override auto behavior. Otherwise the setting does not really behave like a minimum payload.
