When minStats is not nil, sort records descending just like maxStats

[TheCodeSinger]

I've added pagination support (locally) for Next/Previous Page. However, the previous page doesn't feel right because I do this by setting minStats equal to the total Stats of the first record in current list. Then the next list comes and the sort order is reversed. We should keep it consistently descending so the pagination feels right.

OR should I just reverse the list myself?

I realize it made sense when minStats was an isolated query. Calling this a bug just to give it more visibility. :)

[TheCodeSinger]

Hm.. actually something has changed. Did you remove support for minStats?

[TheCodeSinger]

Actually, when I pass minStats=0 then I get a list of the 10 lowest stat targets, but any non-zero number returns me a list of the highest.

Or if I start fresh with
http://tctools.club/app/targets/json?maxStats=183300&targetCount=10
I get a proper list. Then if I do
http://tctools.club/app/targets/json?minStats=183300&targetCount=10
I get exactly the same list as the prior query. Is it being cached somehow?