Quote:
Originally Posted by tomhanks123
more fishing states :)
[7:18:46] You got a bite!
[7:18:48] Unknown Fishing State [54] encountered
[7:18:48] Bot stopped!
I notice the program still hooks the fish even though it encounters the error before it stops, is it possible to make it so the bot keeps fishing after the error report. I understand that ideally we don't get the error but this way it can still be functional (perhaps something like 3 errors before a stop)? I think I may still have a few more fishing states to report, possibly the fish getting away or fish breaking the line etc.
Update: Haven't run into other errors besides the one additional one above stated. Some feedback on the hotbar parse, it seems to work fine the first time but once you change class, do something else, switch back, it seems to lose the ability to parse the hotbars. The bandaid for this is to log out (not closed the game), close and relaunch program and that seems to do the trick. Can get bit a inconvenient though.
|
The fact that it hooked the fish first is important information. That means that the unknown state you encountered is a reeling state, as opposed to a casting or fishing state.
I ran into the problem with switching jobs and causing the hotbar parse to fail, but I fixed it, and it doesn't happen for me anymore. :( That's really irritating that it's still happening for you. I'll look into it tonight.
Btw, I fixed the issue with the timespan crossing midnight, I just haven't posted it yet, I wanted to test it a little more first. The code I had put in to handle it simply did not work the way MSDN said it does. I had to find a workaround.
Quote:
Originally Posted by hman32
I've tried different hotbar settings, but to no avail. Here's my initial settings, hotbars 4-8 are shared:
[Only registered and activated users can see links. Click Here To Register...]
Also, can you please show your hotbar settings, so I can check if they would work for me?
If parsing hotbars has so many issues, I agree it would be much more effective to just use fixed bindings like '1' for 'Cast', '2' for 'Hook', etc.
I haven't run the version by StolasZagan, but his description says that he uses this model of sending commands:
[Only registered and activated users can see links. Click Here To Register...]
Probably there were good reasons for this. |
I will post a pic of my hotbar settings tonight. And yeah, parsing hotbars is finicky. Maybe I'll add an option to use set keys. I'll keep looking into your issues. Do you think you could also post a pic of your actual hotbar settings window? I'll try to duplicate your setup exactly and see if I can get it to fail.
Edit: Oh shit...I just looked at your picture again, and I know exactly what your problem is. I'm not handling the case where the hotkey is a letter. This is causing one of your buttons to be in a "not found" state. This is a REALLY easy fix too. I'll knock it out when I get home from work.
Edit: Actually, it was so easy I decided to just go ahead and do it. v0.9.5 is posted in the OP. It works for me now when letters are assigned to hotkeys. It definitely broke with "Unable to parse" before. Let me know how it works for you.
Edit: Hmm, that may or may not have been the issue in your case HMan. The more I look at it, the more I think that the hotbar parsing code wouldn't have failed, but the bot just wouldn't have been able to use Release. Try it out anyway, just in case, and let me know the results. If the current fix doesn't work, I'll just add some code to dump the memory where it thinks hotbars are on your machine and have you send me the resulting file. I should be able to figure out what's going wrong from there.