bodog/ignition allin hotkey increacing betsize by one bb on only some tables

[Guest]

Can you click File->Current Layout, and paste me everything?

[settings]
table_width=1008
table_height=751
total_slots=12
slot1x=0
slot1y=0
slot2x=1008
slot2y=0
slot3x=2016
slot3y=0
slot4x=3024
slot4y=0
slot5x=0
slot5y=722
slot6x=1008
slot6y=722
slot7x=2012
slot7y=722
slot8x=3026
slot8y=722
slot9x=0
slot9y=1409
slot10x=1008
slot10y=1409
stack_slot=0
newtables_slot=grid
move_to_grid=never
oldtables_duration=10
oldtables_slot=0
scan_mode=DWM
play_mode=tile
slot11x=2015
slot11y=1409
slot12x=3026
slot12y=1409
activate_most_urgent=1
activate_table_under_mouse=0
highlight_active_win=1
move_mouse_to_most_urgent=0
move_mouse_if_not_over_table=0
left_click_detection=1
stack_when_clicking_call_or_bet=0
stack_table_at_end_of_hand=0
drag_drop_swap_slots=1
drag_drop_mode=Logical
minimize_to_tray=0
show_table_count_while_running=0
show_session_timer=0
move_888_popups=1
close_bovada_popups=1
stars_include_logged_in_as=0
notify_new_tables=1
notify_old_tables=1
notify_keep_in_grid=1
notify_ignore_table=1
notify_move_to_grid=0
notify_end_of_hand=0
notification_duration=3
hotkeys_fire_on_release=0
allow_action_hotkeys_on_ignored_tables=1
click_bet_for_allin_hotkey=0
click_bet_for_betsize_hotkeys=0
click_bet_for_betxbb_hotkeys=0
also_keep_in_grid_when_move_to_slot_x=0
fold_checkbox_setting=Fold
also_stack_table_for_betsizeX=0
also_stack_table_for_allin=0
focus_betbox=0
detect_hidden_windows=0
auto_accept_stars_waitlists=0
auto_accept_wpn_waitlists=0
click_stars_info_tab=0
[general]
show_walkthru=0
gui_x=2211
gui_y=903
last_tab=
filename=12(4096).ini
is_reloading=0
version=2.95
win_ver=10.0.16299
v=fu
v295_msg=0
[sites]
WinningPoker_included_executable_path=C:\BlackChipPoker\BlackChipPoker.exe
WinningPoker_included_resized_table_width=1008
WinningPoker_included_resized_table_height=751
WinningPoker_included_fold_color=0x6a3501
WinningPoker_included_call_color=0xa85b0e
WinningPoker_included_bet_color=0xaa5c0e
number_of_sites=3
included_sites=WinningPoker,Chico,BodogIgnition
Chico_included_executable_path=C:\Program Files (x86)\BetOnline\GameClient.exe
Chico_included_resized_table_width=1008
Chico_included_resized_table_height=766
Chico_included_fold_color=0x3635ee
Chico_included_call_color=0x3635ee
Chico_included_bet_color=0x1f1f1f
BodogIgnition_included_executable_path=C:\Bovada\Lobby.exe
BodogIgnition_included_resized_table_width=962
BodogIgnition_included_resized_table_height=751
BodogIgnition_included_fold_color=0x40405
BodogIgnition_included_call_color=0x40405
BodogIgnition_included_bet_color=0x40405
[general]
gui_x=1121
gui_y=1509
last_tab=
filename=true4k-12.ini
is_reloading=0
version=2.95
win_ver=10.0.16299
v295_msg=0
show_walkthru=0
v=fu
[hotkeys]
number_of_hotkeys=9
hotkey1action=Ignore table
hotkey1key=`
hotkey2action=Fold
hotkey2key=S
hotkey3action=Call
hotkey3key=D
hotkey4action=Bet
hotkey4key=F
hotkey5action=All-in
hotkey5key=R
hotkey6action=Disable Hotkeys
hotkey6key=+Tab
hotkey7action=Sit Out all tables
hotkey7key=NumpadSub
hotkey8action=Bet 2.5 bb
hotkey8key=G
hotkey9action=Bet 3 bb
hotkey9key=V
send_table_under_mouse=1

Can you also click File->Current Layout, and add this line directly underneath [settings]

Code:

[settings]
logging=1

and then save the file and the close and reopen SaT. Then use the allin hotkey and trigger it to fail. As soon as it fails, press Stop. Then send me this file:

C:\Program Files (x86)\StackAndTile\logg.txt

let me know where to send the files if you need everything but this seems to be complete cycles regarding the hotkey

this is from a logfile for the (previous) version which i triggered a fail before updating to 295k

[20180218213226] SaT loop - checking for New Tables
SaT loop finding urgents.. tablequeue=52167128700-19023687_0x230594
SaT loop finding urgents.. smartscanlist=0x230594,0x2f1162,0xf0624,0x1125e,0x2804be
SaT loop finding urgents.. smartalreadyscannedlist=0x230594,0x2f1162,0xf0624,0x1125e,0x2804be
ActionRequired(0x230594)=true | variation=0
SaT loop finished updating urgents.. 
tablequeue=52167128700-19023687_0x230594
nonurgents=0x2804be,0x1125e,0xf0624,0x2f1162
[20180218213226] SaT loop - sorting timestamps
[20180218213226] SaT loop - parsing most_urgent into grid
handling 0x230594 - movetogrid=not_preflop
tablequeue=52167128700-19023687_0x230594
[20180218213226] SaT Loop took 15 ms 
[20180218213226] hotkeyAllin started
[20180218213226] hotkeyBetXbb - BBs to bet: 10000 - new betsize: 2500000
ClickSiteCoordinate clicking at scaled: 864 by 687 on BodogIgnition
ClickSiteCoordinate clicking at scaled: 768 by 689 on BodogIgnition
[20180218213227] hotkeyAllin finished
[20180218213227] SaT Loop started

Can you please try this version v2.95k and see if it makes any difference? I've changed the click method on Bodog to not move the mouse, maybe that will help.

http://www.stackandtile.com/sat/tmp/Stac...p-295k.exe

And if it still fails, can you do the logging steps above and send me the log?

for ver 2.95K the first table below worked while the second below didnt work

this table worked:

[20180218224433] SaT loop - checking for New Tables
SaT loop finding urgents.. tablequeue=64034523336-23351390_0x611fa
SaT loop finding urgents.. smartscanlist=0x611fa,0x181410,0x2a1454,0x712be,0x81272
SaT loop finding urgents.. smartalreadyscannedlist=0x611fa,0x181410,0x2a1454,0x712be,0x81272
ActionRequired(0x611fa)=true | variation=0
SaT loop finished updating urgents.. 
tablequeue=64034523336-23351390_0x611fa
nonurgents=0x81272,0x712be,0x2a1454,0x181410
[20180218224433] SaT loop - sorting timestamps
[20180218224433] SaT loop - parsing most_urgent into grid
handling 0x611fa - movetogrid=not_preflop
tablequeue=64034523336-23351390_0x611fa
[20180218224433] SaT Loop took 47 ms 
[20180218224433] hotkeyAllin started on 0x611fa
[20180218224433] SetBetBoxBBAmount - BBs to bet: 10000 - new betsize: 25000000
[20180218224433] SetBetBoxBBAmount - clicking and clearing betbox
ClickSiteCoordinate clicking at scaled: 864 by 687 on 0x611fa of BodogIgnition
ControlClick clicking at x864 y687 on 0x611fa
[20180218224434] hotkeyAllin clicking increasebet button
ClickSiteCoordinate clicking at scaled: 768 by 689 on 0x611fa of BodogIgnition
ControlClick clicking at x768 y689 on 0x611fa
[20180218224434] hotkeyAllin finished
[20180218224434] SaT Loop started




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


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  

[Guest]

v2.95k also crashed bovada on first run and i do have a log of that but it ran while i tried to restart and get all my tables back so its alot larger than the others, just mentioning it in case its relevant or recurs

[SaT_Admin]

Thanks..

In each cases of these logs, it shows the new betsize amount:

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

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.

[SaT_Admin]

Can you please try this version v2.95L

http://www.stackandtile.com/sat/tmp/Stac...p-295L.exe

i've increased the delays between sending the keystrokes which should help reliability, and also changed the sending method

And does the failure only happen on tournament tables? Can you test on some cash game tables and tell me if these hotkeys work correctly all the time?

[Guest]

i think 2.95l has solved it, tested in play money cash and zone as well as a dozen tournaments and havent had an instance of the issue. ill update you if that changes but i think its sorted.

Thanks Greg!

[SaT_Admin]

i think 2.95l has solved it, tested in play money cash and zone as well as a dozen tournaments and havent had an instance of the issue. ill update you if that changes but i think its sorted.

Thanks Greg!

Ok please continue to monitor it and let me know.

[SaT_Admin]

So I think I've found the problem.

Try clicking the betbox on Bodog with your mouse, with SaT completely off.

On play money cash everything works: I can click anywhere in the betbox, and the betbox will get focus. As soon as I mouse over the betbox, the mouse cursor changes from the pointer to the bar, and it allows me to click. As soon as I click the betbox, the betbox clears itself and gets focus.

On play money SNG, I cannot click anywhere in the betbox. The mouse cursor stays as the pointer, and the betbox prevents me from clicking it in most locations. I have to move the mouse all over it and try to find a place where it allows me to click. See this gif:
http://www.stackandtile.com/sat/tmp/bodogbetbox.gif

SaT sends a click to the betbox to give it focus, so that it can type in the appropriate betsize. If this click fails, then that would explain these issues. And this would explain why users are only seeing this problem on tournaments, and not cash tables.

Now, I don't see this problem on ALL tournament tables. Some tournament tables behave just like the cash tables, and allow me to click the betbox every time. This would explain why the problem is intermittent and random.

Can you guys please test and confirm if you are sometimes seeing the same problems with clicking the betbox with your mouse (with SaT off)? Can you try a few different tournaments and maybe resize the tables and see if that matters?

I'm wondering if the horrible bodog client gets messed up when SaT tries to resize the table, which messes up their graphics and ends up preventing clicks. If it works for you then just use SaT normally. And then if you see the Allin hotkey failing, can you Stop SaT and see if you can click the betbox or not? v2.95L would not have fixed this problem

Have I mentioned how much I hate this new bodog software?

[Guest]

oh the new software is definitely a nightmare, (similar to the old software but in new and exciting ways)

ill keep checking/testing and let you know what i find

[Guest]

PS the captcha number never seems to work the first time its selected, usually have to get the letters right and go to preview post then re-select the number

[Guest]

So I think I've found the problem.

Try clicking the betbox on Bodog with your mouse, with SaT completely off.

On play money cash everything works: I can click anywhere in the betbox, and the betbox will get focus. As soon as I mouse over the betbox, the mouse cursor changes from the pointer to the bar, and it allows me to click. As soon as I click the betbox, the betbox clears itself and gets focus.

On play money SNG, I cannot click anywhere in the betbox. The mouse cursor stays as the pointer, and the betbox prevents me from clicking it in most locations. I have to move the mouse all over it and try to find a place where it allows me to click. See this gif:
http://www.stackandtile.com/sat/tmp/bodogbetbox.gif

SaT sends a click to the betbox to give it focus, so that it can type in the appropriate betsize. If this click fails, then that would explain these issues. And this would explain why users are only seeing this problem on tournaments, and not cash tables.

Now, I don't see this problem on ALL tournament tables. Some tournament tables behave just like the cash tables, and allow me to click the betbox every time. This would explain why the problem is intermittent and random.

Can you guys please test and confirm if you are sometimes seeing the same problems with clicking the betbox with your mouse (with SaT off)? Can you try a few different tournaments and maybe resize the tables and see if that matters?

I'm wondering if the horrible bodog client gets messed up when SaT tries to resize the table, which messes up their graphics and ends up preventing clicks. If it works for you then just use SaT normally. And then if you see the Allin hotkey failing, can you Stop SaT and see if you can click the betbox or not? v2.95L would not have fixed this problem

Have I mentioned how much I hate this new bodog software?

ya youre right

few things
resizing didnt change behavior of "broken betboxes", or working ones

Fullscreening either table it kept its previous behavior... ?once a table is broken it stays that way?

hovering cursor over the betslider and scrolling mwheelup "unlocked" the bet box so it responded to clicks thats a possible hack fix untill you can figure out something more elegant (client side option, not one of my hotkeys)

ill check/verify that more later when i have fewer tables, tho im wondering if theres an interaction between wpn and bovada that causes the glitch somehow since it worked fine while just testing bovada