What do you mean with no luck? Did it work at all when using Stars to pop up tables? Did it fail in the same way when things get 'busy'?
Here's the thing:
I'm fairly certain that nothing is jumping the queue, because if it were, then it would be happening all the time.
My guess? When things get 'busy', you enter a pot with call/bet and the table leaves the stack and moves into grid. Once this happens, the next table underneath in the stack becomes visible to you. However, this table is not necesarily the next most urgent table in the queue. The stack just HOLDS all the tables. That's it. SaT will keep track of the next table needing action, and will bring that table to the top of the stack. And when it does, you perceive that something has jumped the queue, when in fact it was SaT simply bringing up the next table in line. You tried to act on the other table simply because it became visible when the top table moved out, while SaT was in the process of bringing up the next most urgent table.
If this is in fact what is happening, then one solution would be to speed up SaT's scanning speed, which would bring the tables up faster, hopefully before you attempt to act on a table in the stack that is not the most urgent. The default engine speed is 300ms when using DWM scan mode. You can try faster speeds using this setting in your config file:
Code:
[settings]
engine_delay=150
Try that and see how it goes. That would cut the delay between scans in half from the default, essentially doubling the scan speed. Keep in mind, the shorter the delay, the more CPU usage you will encounter.