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

Have to edit script to parse # baubles? #6

Open
HiddevH opened this issue Feb 25, 2020 · 3 comments
Open

Have to edit script to parse # baubles? #6

HiddevH opened this issue Feb 25, 2020 · 3 comments

Comments

@HiddevH
Copy link

HiddevH commented Feb 25, 2020

Would like to pass in the GUI / terminal how many baubles I have as they are used frequently and should not be edited in scripts (or am I doing this wrong).

@disarmyouwitha
Copy link
Owner

I think this is a cool idea / I do believe it could be done.. It may be tricky trying to OCR the # of baubles? But I could also see it working by asking for a screenshot of 0 baubles and using them if SSIM doesn't match.

It may also work as a dumb function / trying to use baubles even if you have none.. but I haven't tested how this would work in the game.

In practice, I was being lazy and usually just set mine to 60/90 and always bought that many baubles before I left the bot going, bit I certainly think it should be moved to a config at the very least!

@disarmyouwitha
Copy link
Owner

(Unfortunately I'm not sure if my WoW subscription is active anymore, so I don't know if I will be making any further improvements at this time -- I, however, welcome any improvements either submitted as Pull Requests, or if you just wanted to make your own fork and run with it! =D)

@HiddevH
Copy link
Author

HiddevH commented Feb 25, 2020

I would rather require the User to pass the # of baubles at the start of the script (heavily reduces complexity and OCR is really prone to errors).
I'll add that when I have time. Might provide a little GUI while I'm at it

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