Thanks..
In each cases of these logs, it shows the new betsize amount:
So for the Bodog Allin hotkey, what SaT does is send a 10,000 bb betsize. Its unlikely that a user will have larger than a 10,000 bb stacksize, so this should be safe. The log calculates the new betsize as 6,000,000 and then tries to send that amount to the box. That means on this table, the blinds must have been detected as 300/600. Now, Bodog doesn't allow you to bet an amount larger than your stacksize, and if you tried to click Bet now, the Bet button would fail and bet the wrong amount. So, then SaT sends a click to the increase bet + button, which causes the software to round down the betsize to your max stack.
If you're just seeing a +1 bb betsize, instead of the allin size, then something is failing between when SaT clears the betbox and sends the new amount. The click of the increase bet + button is what is causing the +1bb bet amount that your seeing. But the problem must be occurring before that. From your logs, the other table that worked sent a 25,000,000 betsize, so the problem is not large numbers being rejected by Bodog
Deleting the line, or setting it to 0, both will work. But it doesn't take effect until you close and reopen SaT (or just click the Save button on the Layout tab, which also reloads the software). And the log file deletes itself every time you press Stop/Start in the software
It would be helpful if you left your email or skype name so I can communicate with you quicker. I'd really like to solve this issue.
In each cases of these logs, it shows the new betsize amount:
(02-19-2018, 06:23 PM)Guest Wrote: this one didnt work/just added +1bb:
[20180218224456] SaT loop - checking for New Tables
SaT loop finding urgents.. tablequeue=64097014621-23374187_0x81272
SaT loop finding urgents.. smartscanlist=0x81272,0x181410,0x611fa,0x2a1454,0x712be
SaT loop finding urgents.. smartalreadyscannedlist=0x81272,0x181410,0x611fa,0x2a1454,0x712be
ActionRequired(0x81272)=true | variation=0
SaT loop finished updating urgents..
tablequeue=64097014621-23374187_0x81272
nonurgents=0x712be,0x2a1454,0x611fa,0x181410
[20180218224456] SaT loop - sorting timestamps
[20180218224456] SaT loop - parsing most_urgent into grid
handling 0x81272 - movetogrid=not_preflop
tablequeue=64097014621-23374187_0x81272
[20180218224456] SaT Loop took 16 ms
[20180218224456] hotkeyAllin started on 0x81272
[20180218224456] SetBetBoxBBAmount - BBs to bet: 10000 - new betsize: 6000000
[20180218224456] SetBetBoxBBAmount - clicking and clearing betbox
ClickSiteCoordinate clicking at scaled: 864 by 687 on 0x81272 of BodogIgnition
ControlClick clicking at x864 y687 on 0x81272
[20180218224456] hotkeyAllin clicking increasebet button
ClickSiteCoordinate clicking at scaled: 768 by 689 on 0x81272 of BodogIgnition
ControlClick clicking at x768 y689 on 0x81272
[20180218224456] hotkeyAllin finished
[20180218224456] SaT Loop started
So for the Bodog Allin hotkey, what SaT does is send a 10,000 bb betsize. Its unlikely that a user will have larger than a 10,000 bb stacksize, so this should be safe. The log calculates the new betsize as 6,000,000 and then tries to send that amount to the box. That means on this table, the blinds must have been detected as 300/600. Now, Bodog doesn't allow you to bet an amount larger than your stacksize, and if you tried to click Bet now, the Bet button would fail and bet the wrong amount. So, then SaT sends a click to the increase bet + button, which causes the software to round down the betsize to your max stack.
If you're just seeing a +1 bb betsize, instead of the allin size, then something is failing between when SaT clears the betbox and sends the new amount. The click of the increase bet + button is what is causing the +1bb bet amount that your seeing. But the problem must be occurring before that. From your logs, the other table that worked sent a 25,000,000 betsize, so the problem is not large numbers being rejected by Bodog
(02-19-2018, 06:23 PM)Guest Wrote: PS do i need to change logging=1 to logging=0 to get logging to stop, just deleting the line didn't stop the log file from being generated/updated and i don't wanna leave stack and tile running and accidentally find out how long it takes to write a 1 TB .txt file
Deleting the line, or setting it to 0, both will work. But it doesn't take effect until you close and reopen SaT (or just click the Save button on the Layout tab, which also reloads the software). And the log file deletes itself every time you press Stop/Start in the software
It would be helpful if you left your email or skype name so I can communicate with you quicker. I'd really like to solve this issue.
