Stars Bet Pot AHK ?

[disco_stu1978]

when you are assigning hotkeys to the script, what is the language for the numpad keys?

Like would 1(end) on the numpad be numpad1::, or something different.

I do not wanna mess around and try stuff myself (without asking) just in case I somehow trigger some sort of catastrophic accident.

[_dave_]

Hi Disco_Stu,

[ QUOTE ]
when you are assigning hotkeys to the script, what is the language for the numpad keys?

Like would 1(end) on the numpad be numpad1::, or something different.

I do not wanna mess around and try stuff myself (without asking) just in case I somehow trigger some sort of catastrophic accident.

[/ QUOTE ]

Numpad1:: is the correct notation, presuming you have num-lock on.

Here is a list of all the available hotkeys:

Autohotkey.com : List of Keys, Mouse Buttons, and Joystick Controls

dave.

[_dave_]

[ QUOTE ]
Version 2 seems a bit buggy to me. It seems to "lag" when your using it, and also mis-adds your raise more often than version 1./

[/ QUOTE ]

It should never lag - You are on Stars, I presume? Do you have debug=1 enabled? Debug mode will certainly cause lag, as it shows you areas where image-scanning takes place.

Mis-adding raises I consider unacceptable - must be fixed. Any ideas when / what causes this to happen? (debug mode will inform you what it thinks are the pot size / amount to call - can use this to find problems - but this will make it laggy)

dave.

[_dave_]

Hi Jsnipes28,

[ QUOTE ]
It seems to work well except for it won't calcu;ate a pot-sized raise like the old party one would. I changed the percentages of the bet sizes a little but I wouldnt thnk that would cause it not to calculate the pot-sized raise.

[/ QUOTE ]

Could you please post a HH where this happened, the hotkey you used, and what amount it should have bet?

There must be a math error somewhere - an erronious HH will help track it down [img]/images/graemlins/smile.gif[/img]

dave.

[_dave_]

Hi GLmaestro

[ QUOTE ]

The new bet pot script causes my full tilt client to crash. The old one didn't, please help! : )

[/ QUOTE ]

I noticed your BBV post [img]/images/graemlins/frown.gif[/img] not a good time for an FT client crash.

FT software is very easy to crash - I have put in loads of checks to try and prevent this.

You say in BBV:
[ QUOTE ]

I was betting with one of my extra buttons on another table (half pot or whatever) and that's what caused the client crash


[/ QUOTE ]

Could you post the code for this extra button?

At a guess, you probably have it preceeded by the ~ (pass through) modifier - and the reciept of this button press while other stuff was going on caused FT to crash.

Try without ~, it hopefully will prevent crashes.

You can see in the default code I am not using the ~ for the fold / call hotkeys - Originally when I had these mapped to F and C keys, using ~ would occasionally cause FT to crash out [img]/images/graemlins/frown.gif[/img]

dave.

[_dave_]

Hi Aisle Phive,

[ QUOTE ]
Any updates with the new mouse, Dave?

[/ QUOTE ]

Just got home with it an hour ago - It is charging [img]/images/graemlins/smile.gif[/img]

Looks very nice, but not tried it yet.

Thank you ZBT for the quick review - Hopefully I'll be able to figure out how to get all these new buttons to do something [img]/images/graemlins/smile.gif[/img]

dave.

[disco_stu1978]

awesome, thanks for that dave.

So as I said, I use this for LHE mostly, but I just tried it out in some NL games, and I found a little bug (I think). When I try to do any kind of raise action it lags super bad, and a white box moves across the table. (I assume this is the script gathering info?)

(this is on stars, and I use a stripped down "no image" theme. I have xp/classic mode.) it is not really a big deal to me as I really never play NL, but I thought it might pop up for others.

Cheers.

edit: nm, read the thing about the debug being on, changed it, and it seems to be working fine now. [img]/images/graemlins/smile.gif[/img]

[_dave_]

[ QUOTE ]

When I try to do any kind of raise action it lags super bad, and a white box moves across the table. (I assume this is the script gathering info?)

[/ QUOTE ]

Yes, this is the script gatering info, BUT:

This is the script running in debug mode - debug := 1 set instead of debug := 0. With debug enabled, it purposefully spends 1/2 a second on each image search, displaying a white box where over the scanning area. This is so we can observe if it is looking in the correct place for information, and is usefult if you find it not working properly for finding wat is the problem. Also this means you get a baloon help with the contents of important variables in it for the same problem-finding reasons.

For most people, debug mode should be off, and there should be no lag. Annoyingly I forgot to change this setting before uploading the version 2, so I suspect many people are finding Stars a bit laggy. I corrected it and re-uploaded, so anyone downloading now should have debug off by default, but you were obviously quick to download the new version.

Set debug := 0 near the top of the script, save & reload to get rid of this lagginess [img]/images/graemlins/smile.gif[/img]

EDIT:
[ QUOTE ]

edit: nm, read the thing about the debug being on, changed it, and it seems to be working fine now.


[/ QUOTE ]

Glad to hear it, but was worth me posting the explaination again anyway, in case others have this unwanted setting [img]/images/graemlins/smile.gif[/img]
dave.

[jsnipes28]

Dave-
I realized that it was doing this so I never misbet- I just scrolled up and then bet so it wasn't much of an issue but it would basically be like:

I raise to 21, 2 calls, so pot ~$62ish, BB leads for $15, I click M (middle button to pot size raise) and it goes right to $62ish.

I will misbet later and then save the HH for you if that will help.

[_dave_]

[ QUOTE ]

I will misbet later and then save the HH for you if that will help.

[/ QUOTE ]

Probably no need now, your example is explanitory enough - It looks like it is not correctly finding the amount to call - is this on Stars?