Quote:
Originally Posted by Burnss
What, really? lol. if it is your program which is causing constant R's this is the easiest thing in the world to fix. After script decides to leave table, move it to another stack where it constantly checks for R's, once theyre all gone on that table, move it back to scripting stack. It didnt affect performance for me at all, hope you do it cause its a **** pain in the ass.
It takes one hour to code. its basically copying the code you got already but changing a few variables. Please do it.
When the player, who first reserved the table leaves, our script will unjoin the table and move it back and also ignore it for a few seconds.
After that it will start scanning the table again. Sure, we might ignore it untill all Rs have left, but that is not always a good solution, because sometimes a new fish can join relativelly quickly.
Just think about it: there would be no problems, if everyone used our system: a player reserves the table, he decides to leave, all scripters immediatelly leave, ignore the table for even only a few milliseconds untill Pokerstars RAM has updated everywhere and the table is empty again.
It is not our fault, that everyone i reserving the table for as long as they can and that regulars join even 10 seconds after the fish has left.
In my opinion, we are certainly not responsible for the tables full of Rs, it's mostly slower scripts or scripts that will never unjoin.