Ok, did you also turn off "Give tablescan threads highest priority"?
Here's an explanation of the waitlist fix: Before this update, if you had a filter, for example "# of Fish 1-10 AND # on waitlist 0-3", TableScan would of course join the table if it meets these filters. But, when the waitlist went over 3, then TableScan would see that the table no longer meets your filters, and leave the waitlist, you could be first on the waitlist and it would still leave because the table didn't meet your filters. So, I knew that lots of people were using the # on waitlist filter in this way and probably didn't realize that it could backfire like that by removing you from good tables where you're high on the list. So what I did is I changed some logic in the AutoWaitlisting, so that when looking at a table to see if TableScan should leave it, it will ignore any # on waitlist conditions. So, using the above example, if there is 2 fish at a table and the waitlist goes up to 5, TableScan will NOT leave the waitlist now, it will only evaluate the table by the # of fish, and ignore the # on the waitlist condition, when it comes to deciding whether or not to leave the waitlist.
And yes, you're correct about the way the autowaitlist is working, it joins 20+ tables, then after you have 12 open it doesnt leave the waitlists youre already on if they still meet your filters. So other "seat available" popups will show up and TN will automatically click accept if you have it set to do that. I've never really used TN but I believe there's an option somewhere in there to limit the tables open so that when you have 12 open and a seat available popup opens, it will click no for you automatically