Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bet button value and Raise button value located in two different areas. A distinct Bet button set up should be implemented #174

Open
SirFrancis83 opened this issue May 3, 2023 · 7 comments

Comments

@SirFrancis83
Copy link

Hello,
in setting up a particular poker table refering to People's Poker I came across a problem with raise and bet button vaue locations. In this poker table the corrisponding values are located in two different areas. Therefore if you correctly set up the raise value Bot cannot recognize the bet value and viceversa. In addition this poker client does not show the all in value when bot must go all in to call.
I attach some screenshots that show it.

2
3
1

@dickreuter
Copy link
Owner

Ok so basically 2 things:

  1. There should be a separate Raise value that is used when the raise button is detected
  2. All in call value should be 'my funds'

I think the second issue you can solve by pointiing the call in call value to my funds. Would that work?

@SirFrancis83
Copy link
Author

So if I have understood what you are telling me, i should point as all in value the value of my funds? I can test and tell you if it works.

@dickreuter
Copy link
Owner

dickreuter commented May 3, 2023 via email

@SirFrancis83
Copy link
Author

Yes it seems to work the same👍

@dickreuter
Copy link
Owner

What about the raise button. Does it work if you mark the area to read the number to the whole button? It should automatically ignore any letters.

@SirFrancis83
Copy link
Author

Yes it seems i managed to overcome the problem marking the whole button. But it has been quite difficult since I have also the problem of coma instead of dot.

@dickreuter
Copy link
Owner

dickreuter commented May 4, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants