[2.0.11] Conflicting Logistics Requests and "Any Quality" Limit

[Lhoto]

To start: discovery of what I can only assume to be a bug here began with me assuming that an item in a logistics request group with "any quality" selected as the filter would have a higher priority than a specific quality's upper limit in the case of a conflict. With that out of the way, here we go down the rabbit hole:

First, whenever you have multiple requests of the same item at the same quality level, the maximum amount set for that item is treated additively. So, if I have 50 max items in one request, 30 in the next of the same kind, boom we're now requesting up to 80 of that item. However, this entire system seems to be wildly inconsistent the moment you bring "any quality" into play.

10-26-2024, 19-12-10.png (32.84 KiB) Viewed 228 times

If I start the list with an 'any quality' maximum, it clamps everything below it. Max value set to 10? Yup, you're only ever getting 10 of them. Not a single one more.

10-26-2024, 19-12-59.png (29.98 KiB) Viewed 228 times

Now, let's just do something as simple as taking that any quality request and shifting it down the list by one position. Any guesses as to what happens? Yup! That's right, now you're getting 60 of them. Take that limit of 10 you just set and throw it directly out the window, never to be seen again.

10-26-2024, 19-14-56.png (41.23 KiB) Viewed 228 times

Up until now I could write off as a design decision or a difference in prioritization, but here's where it begins to be wildly inconsistent: Add another conflicting logistics request into the list with 'any quality' as the filter. When it's at the top of the requests, it behaves similar to the original behavior and adds the upper 'any quality' limit to all following 'any quality' limits. So, here you'd end up with 23 chests. Move that top request down a single position? Now your 'any quality' filtered logistic requests may as well not exist.