[2.0.19] Vehicle ammunition bot order overwritten by standing logistics request
Posted: Sun Nov 17, 2024 9:10 pm
I think this is more unintended behavior than true bug, but it's for a use case that happens often enough that I hope it's worth adjusting.
1. What did you do?
Have a deployed tank with loaded ammunition of one type. The loaded ammunition has a logistics request for a minimum of the current amount. Use bots to swap to a different type, such as from Cannon Shell to Uranium Cannon Shell - by ghosting the latter over the former's position in the ammo slot.
2. What happened?
Bots unload the stack of Cannon Shells, then bots load back a stack of Cannon Shells.
3. What did you expect to happen instead? It might be obvious to you, but do it anyway!
My naive expectation was first that the outgoing ammo would be loaded to the Trunk instead of to the loginet - since that would keep it at the minimum requested count, though I'm not very surprised that they unload to the loginet instead. More crucially, I expected the request to load the new ammo to the ammo slot not to be overwritten by the standing logistics request for another item. I'm sure the outgoing ammo is replaced first because there is a nearby buffer for it but not the new ammo.
4. Does it happen always, once, or sometimes?
Always. Also replicated by replacing uranium rounds with piercing rounds in the same manner - so I think it's a generic problem. I think it can also happen with fuel, such as a nuclear fuel ghost in a fuel slot but you deconstruct a tree on your way back to base, but I haven't tested it.
Sorry if the soapboxing is unwelcome, but I see one "fix" and one related feature request. I would guess a reasonable fix is to prevent "refills" from an item other than that specified by a ghost request, except when done by the player.
The related feature request would be a more reasonable way to swap ammo types in remote vehicles. It seems strange that for all a tank can accomplish on its own with a loaded grid and bots, it doesn't have a reasonable way to just swap ammo, and it's something I wish for several times a session.
That said, thanks for all you do <3
1. What did you do?
Have a deployed tank with loaded ammunition of one type. The loaded ammunition has a logistics request for a minimum of the current amount. Use bots to swap to a different type, such as from Cannon Shell to Uranium Cannon Shell - by ghosting the latter over the former's position in the ammo slot.
2. What happened?
Bots unload the stack of Cannon Shells, then bots load back a stack of Cannon Shells.
3. What did you expect to happen instead? It might be obvious to you, but do it anyway!
My naive expectation was first that the outgoing ammo would be loaded to the Trunk instead of to the loginet - since that would keep it at the minimum requested count, though I'm not very surprised that they unload to the loginet instead. More crucially, I expected the request to load the new ammo to the ammo slot not to be overwritten by the standing logistics request for another item. I'm sure the outgoing ammo is replaced first because there is a nearby buffer for it but not the new ammo.
4. Does it happen always, once, or sometimes?
Always. Also replicated by replacing uranium rounds with piercing rounds in the same manner - so I think it's a generic problem. I think it can also happen with fuel, such as a nuclear fuel ghost in a fuel slot but you deconstruct a tree on your way back to base, but I haven't tested it.
Sorry if the soapboxing is unwelcome, but I see one "fix" and one related feature request. I would guess a reasonable fix is to prevent "refills" from an item other than that specified by a ghost request, except when done by the player.
The related feature request would be a more reasonable way to swap ammo types in remote vehicles. It seems strange that for all a tank can accomplish on its own with a loaded grid and bots, it doesn't have a reasonable way to just swap ammo, and it's something I wish for several times a session.
That said, thanks for all you do <3