![]() |
|
#21
|
|||
|
|||
|
With the advent of SixthSense, I want to get more serious about my mining. Can someone give me a primer on how to use this with multiple users / multiple party processes to mine 2 or 3 dozen tables at a time?
|
|
#22
|
|||
|
|||
|
[ QUOTE ]
With the advent of SixthSense, I want to get more serious about my mining. Can someone give me a primer on how to use this with multiple users / multiple party processes to mine 2 or 3 dozen tables at a time? [/ QUOTE ] [ QUOTE ] To use SafeMine, just follow these simple steps: 1) Open a copy of PartyPoker and navigate to the limit you wish to mine. 2) Set a filter inside of PartyPoker for the types of tables you wish to mine. 3) Run SafeMine.ahk (make sure you have AHK installed) and you should see SafeMine open the required number of tables for you. 4) In as many user areas (or networked PCs) as you wish, repeat steps 1-3. SafeMine will make sure that it only opens a table ONCE throughout all of the user areas, and if it happens to accidentally open the same table multiple times, it will auto-detect/auto-correct this for you. [/ QUOTE ] |
|
#23
|
|||
|
|||
|
[ QUOTE ]
Yes, atm it can't tell if a table is empty (unless it's a SNG), but if Party ever closes table it will fire up a new one (and you could use PT to filer based on >X players at the table). I agree though this might need fixing eventually, but atm I'm just trying to keep it as simple as I possibly can (it's not meant to be a new iWitness, just something to fall back on if you have problems with iWitness like I did for mining SNGs). [/ QUOTE ] Seems like a quick solution to this might be to just close all the tables and reopen every hour, or something along those lines. A check would need to be put in to not close SnG tables prematurely, but seems like a reasonable solution that I wouldn't think would add too much complexity to the script. |
|
#24
|
|||
|
|||
|
I don't think it's a good idea because:
1. Most tables will be active when closed, making you lose some of the history (hands in progress will have a gap.) 2. Dead tables DO get removed by the Party system eventually, and this will selectively remove them. I think continues collection on games in progress is more valuable than one or two extra 'dead table' slots which would get scrapped soon anyway. The burning question for #2 is: how long to finished tourney tables stay open? For limit, I know the big question is how long it has been since someone sat down for a moment. Otherwise, Party shuts down excess open tables until there is exactly one empty table available - but it makes sure there is always one empty table. This forces an "open all tables" strategy to have one empty table open. Anyway, if the Party closes the tables in a reasonble period - 15 minutes, half hour - then a "close all" approach once an hour will save very little time (it will cut the table death time in half, on average) while disrupting live games frequently. |
|
#25
|
|||
|
|||
|
Party SNG tables don't get closed ever automatically. Or at least in any reasonable (< several hours) timeframe.
(This was a month or so ago, I haven't re-tested this recently) |
|
#26
|
|||
|
|||
|
[ QUOTE ]
Party SNG tables don't get closed ever automatically. Or at least in any reasonable (< several hours) timeframe. (This was a month or so ago, I haven't re-tested this recently) [/ QUOTE ] Safemine will close SNGs automatically, but as Mogobu pointed out Party does eventually close the ring game tables on it's own. I can add this to it, but if I'm not careful it will end up very complex. Also the great thing with AHK is it's very easy to edit the code - with a bit of reading up, iWitness features can be added to SafeMine very easily. [img]/images/graemlins/smile.gif[/img] Juk [img]/images/graemlins/smile.gif[/img] |
|
#27
|
|||
|
|||
|
[ QUOTE ]
4) In as many user areas [/ QUOTE ] This is the part I don't understand. |
|
#28
|
|||
|
|||
|
I think it's a great script, thanks Juk. It can also be easily modified to create a table opener of sorts.
|
|
#29
|
|||
|
|||
|
[ QUOTE ]
[ QUOTE ] 4) In as many user areas [/ QUOTE ] This is the part I don't understand. [/ QUOTE ] Some people use Windows XP's "fast user switching" to log in to their machine more than once with different User name. Each logged in User's programs run at the same time. So you can observe tables from more than one instance of Party at a time, in different User areas. If you want to know how to set it up, look up 'Fast User Switching' in your system's help or over at Microsoft. |
|
#30
|
|||
|
|||
|
[ QUOTE ]
I think it's a great script, thanks Juk. It can also be easily modified to create a table opener of sorts. [/ QUOTE ] Yeah, that's exactly what I did! It's the quickest way to open my first set of tables to consider. But I didn't actually mod the script. I just start my session by running it, and then I kill the script. |
![]() |
|
|