It's supposed to be the following displayed pet in the queue.How does one tell the difference between the pet below the top pet and the next pet? I didn't notice a visual indicator of the next pet as all I can see is the list as Rematch is displaying it (which is not the order it is selecting pets). The next pet can be anywhere in my queue of 20 pets, but I can't tell what that will be until Rematch auto chooses it.
Pet A
Pet B
Pet C
If Pet A gains xp, Pet B swaps in; if Pet B gains xp, Pet C swaps in; if Pet C gains xp, Pet A swaps in.
For unsorted and descending sorts it should always behave that way. The next displayed pet will load.
However, after some testing I see that in a descending sort, there's an issue.
If pets start this way:
A(lvl 11.5) -> B(lvl 10.3) -> C(lvl 10.2) -> D(lvl 9.5)
If C gains .3 lvl (30% xp), it dutifully sorts and now the next displayed pet is B:
A(11.5) -> C(10.5) -> B(10.3) -> D(9.5)
And it will swap to pet B instead of D, and if pet B gains .3 lvl:
A(11.5) -> B(10.6) -> C(10.5) -> D(9.5)
The next displayed pet is C, and B and C swap places in the queue until one of them is above A and then A will get in the mix.
So that behavior is unintended. I'd like it to traverse down the queue like it does on the unsorted queue. It's fixable but the code is being deleted so it's not a high priority. However with pets moving as they gain xp, it may not be obvious which pet is next. So it may make sense to disable auto rotate for descending sorts.
But I would very much like to keep that behavior for the unsorted queue. Auto rotate is intended to cycle through pets in the queue. The only time I personally use auto rotate is with an unsorted queue.
I'm afraid I don't understand this. The <- and -> buttons don't move pets within the queue. If it's not going to the previous/next displayed pet in the queue, then that's a bug.The hard part about this is I can't see where the <- and -> effectively move the pet through the list since the displayed list doesn't match the select list. When my level 24 waterfly levelled to 25, for example, it randomly picked a level 1 soul of the forge which was 2/3 of the way down the list (not even near the waterfly). I had no indication the soul of the forge would be next. From the displayed list, I expected my 24 moonshell crab to be picked next but it wasn't. That make sense?
If a pet levels to 25 and it's picking something unexpected from the queue, that's a separate bug. (Pets leveling to 25 and auto rotate don't have any relationship with the <- and -> buttons.)
That said, the entire queue backend, including how leveling slots are declared for loaded pets, is being rewritten. Like, the code totally removed and replaced. The queue code as it exists was written before auto rotate and sorted queues were a concept. The new queue will be written with auto rotate, sorting, min hp/max xp and multiple leveling slots all kept in mind.
TL;DR: Don't sweat existing bugs in the queue. The offending code is going to be gone soon. I'm still very much interested in how people feel the queue should work. I can disable auto rotate on descending sort, but it will remain for an unsorted queue since I use that myself.