I understand, and I will definitely put this on the to-do list, but here's the thing: when a table is chosen for collapse, it is actually rarely "random". The software definitely intends to do it randomly, but the main goal is to minimize player movement. So, when it looks for a table to collapse, it first looks for the table that is most eligible, as in the table with the fewest players sitting at it. This will mean that as few players as possible have to physically get up and move. Most of the time this list does not include all of the available tables (which means that many times the table you would like to next be collapsed won't qualify as a table that should be collapsed).
Now that I've gone through this more in my head, and written out a lengthly explanation of table balancing (which I deleted because, believe me, no one really wants to read that crap), here's what I think can feasibly happen:
- Allow a table elimination order to be specified
- If an order has been specified, then when a table can be collapsed, we go through the ordering and eliminate the first table in that list that is still in use and qualifies (tables can be of differing sizes, so it is possible that eliminating a particular table might not balance things)
- If an order has not been specified, do what is currently done, which is minimize player movement
It's "on the list"....