Sign in to follow this  
Followers 0

Ealric's Final Version

98 posts in this topic

Posted (edited) · Report post

Code Removed - Check final script thread on PAGE 4 of this thread.  That post has all of the instructions and the newest and latest code.  If the date is past February 5, 2004 then the final script will also be removed.  Until then, I will keep the scripts in that thread going.

Edited by Ealric

Share this post


Link to post
Share on other sites



Posted · Report post

I'll have one test script up with pausing enabled soon. You will not have to change your backgrounds or windows or anything like that though.

Keep a lookout.

Share this post


Link to post
Share on other sites

Posted · Report post

Tested the script out and having a few issues, not sure whats causing them.

Have the right resolution set, mouse hardware on etc.

Script starts fine, casts, and reels in first fish np.

Then it goes to and auto sorts, again, no problems at all.

Then is proceeds to fish again, but if you get a "You didn't catch anything" message, the mouse curser moves back to the auto sort, with no window open and tries to click.

After this, the next "You have something on the line" message, doesnt get recognized and will not pull in the fish.

Not sure if i have anything set wrong, i dont think so since it runs fine on start up.

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Code Removed - Check final script thread on PAGE 4 of this thread.  That post has all of the instructions and the newest and latest code.  If the date is past February 5, 2004 then the final script will also be removed.  Until then, I will keep the scripts in that thread going.

Edited by Ealric

Share this post


Link to post
Share on other sites

Posted · Report post

Great script I cant wait to test it. I didn't see any code for auto drop of rust item. Does the script have this feature like Iron's?

Share this post


Link to post
Share on other sites

Posted · Report post

I tries to use this, but it dosnt work!I run the script wiht AutoIT v3.91, and its in my taskbar, then i start FFXI.

Once ingame i start fishing, but the bot dosnt do annything.

I havent been able to use anny of the fish bots...

AutoIT examples work fine...

I use Windows XP, 1280*1024, hardware mous on.

Please help :whistle:

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

One sidenote on the script.

If you keep chat on or are in a very chatty linkshell, their messages could push the event line up too fast for the script to see.

In this case, I did leave the failsafe in so it will toggle it eventually. Just be patient. Otherwise, to get around this you can take your linkshell out while you fish, tell everyone to shut up or else, or force the script to pause by fishing in a non-fishable area.

Then you can just type /fish again. :whistle:

--

I don't know what to tell you Raf. It's been working perfectly on two machines right now (xp-pro) and (win98) for 90+ minutes now. I have no problems with either machine.

Edited by Ealric

Share this post


Link to post
Share on other sites

Posted · Report post

Great script I cant wait to test it.  I didn't see any code for auto drop of rust item.  Does the script have this feature like Iron's?

earl?

Share this post


Link to post
Share on other sites

Posted · Report post

Ealric, the problem Raf is having is the Send("!1") or Send("!i") doesn't work - basically the ! or ALT isn't happening. I'm not quite sure what could cause this, but I'm having same problem and looking into it. I have tested both compact and normal keyboard setting in FFXI...now I'm looking elsewhere.

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

That usually occurs if you don't have the right version of autoit installed.

I would check that you are using the beta version of autoit 3.91.

Make sure you downloaded the beta .exe version and had the program install itself. If you just downloaded the source code and are running 3.91 out of a folder, it will not work.

--

Also, no feature for rusty item drops. I didn't feel it was completely necessary to put that in.

The only things I'm going to be putting in next now are:

GM control

GM AI interface

Complete text log.

I'm doing this later on. Tonight, I'm taking a break and.. fishing!

Edited by Ealric

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Hey Ealric, I'm trying to convert this to 1024x768 but there is a pixelgetcolor set that I don't know for what text it's looking for. Can you just tell me what it is and I shouldn't have any problems getting it done myself.

If PixelGetColor(25,996) = 10651647 AND PixelGetColor(143,997) = 10979839 AND PixelGetColor(178,997) = 10783487 Then
checkpause()
EndIf

Thanks.

Edited by ravenfyre

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Code Removed - Check final script thread on PAGE 4 of this thread.  That post has all of the instructions and the newest and latest code.  If the date is past February 5, 2004 then the final script will also be removed.  Until then, I will keep the scripts in that thread going.

Edited by Ealric

Share this post


Link to post
Share on other sites

Posted · Report post

Heh one last change sorry guys.

I changed the $start to $unpause. I had forgotten to change the variable name. Use the code above and it should work now.

It is also reflected in the autosort()

and the pause pixel event.

Many thanks.

Share this post


Link to post
Share on other sites

Posted · Report post

I just remover AutoIT, deleted the folder, cleander registry and reinstalled the latests beta.

No change...

Share this post


Link to post
Share on other sites

Posted · Report post

Found an issue...though it's not a bug, it's another thing that should be included int he "INSTRUCTIONS" above

Your "Do...Until" is exiting prematurely...if say I cast and any of the "don't catch" scenarios occur event is set to 1 as it should; however, on the next run through the while loop, when it gets to Do...Until the first line in your log is still the last thing that happened, your failed catch, so event is set to 1 again before something even bites the hook.

Now, the reason I can think of this offhand, is that you have your log set to only display as text appears and then it eventually vanishes (the default text box mode). So, any of you who are having problems where you are getting bites but the Send(ENTER) isn't happening, try restoring your chat box to its default mode (no lines always visible and dynamically adjusts - I don't remember what the settings are called)

Raf: I had version 3.090 and uninstalled and isntalled 3.091 and it works for me now.

Share this post


Link to post
Share on other sites

Posted · Report post

Yes I have my chat box normal and lines always showing. It does not have reactive window use and is sitting at 8 full lines. Thanks for catching that.

Share this post


Link to post
Share on other sites

Posted · Report post

Ealric --

Firstly, thanks for all the work. :) I'm currently using this latest version, but the problem I mentioned earlier seems to persist. Catching multiple fish on a single cast seems to throw the script a curve ball, preventing it from sorting as normal and makign it rely on the failsafe to recast.

I'm using the same settings as you are, to my knowledge: Default window background, non-reactive window (always up), 8 lines. Even when I filter out _all_ other chat, this occurs. Also using the latest beta version, and running XP.

Sorry to be a bother! Any ideas?

Share this post


Link to post
Share on other sites

Posted · Report post

Ealric,

Best script I have used to date!!!

One minor issue:

Occationally the autosort function runs when it shouldn't.

Also I am having the same prob as LifestoneExpress

Tested the script out and having a few issues, not sure whats causing them.

Have the right resolution set, mouse hardware on etc.

Script starts fine, casts, and reels in first fish np.

Then it goes to and auto sorts, again, no problems at all.

Then is proceeds to fish again, but if you get a "You didn't catch anything" message, the mouse curser moves back to the auto sort, with no window open and tries to click.

After this, the next "You have something on the line" message, doesnt get recognized and will not pull in the fish.

Not sure if i have anything set wrong, i dont think so since it runs fine on start up.

Other than that it seems to be great!

Share this post


Link to post
Share on other sites

Posted · Report post

On your multiple fish obtained message, how does it appear..

Does it say:

Obtained: 3 Fish etc.

If it doesn't have the first word Obtained: in then it's not going to work. If this is different than the others, let me know and I'll find a screenshot of the pixel event.

When you obtain anything it should autosort right after and continue on. It seems to me like this event may differ from the normal ones. Let me know if Obtained: is coded in white color on your machine.

Share this post


Link to post
Share on other sites

Posted · Report post

$failsafe is becoming a thorn in my side.

It's designed to continue the script in case one of the message pixel events doesn't go off or is pushed up too fast. Because it's persistent the count is reached occassionally during an event and it creates a slight echo. This is more than likely what is occuring.

I would suggest doing the following:

Set $failsafe to 3000 for now since it's basically just an event that occurs when no messages are received and the number is reached. By setting it to 3000, you will bypass it interfering with the events themselves, hopefully.

I'm also working on a bypass for $failsafe so that it doesn't interfere with pause. I think I found a way but having trouble with the pixel coords working right. I'm going to try a couple of things and then post a revised version of this script tonight or tomorrow.

Hopefully by tomorrow we'll have a great script working here on this resolution size.

Share this post


Link to post
Share on other sites

Posted · Report post

yes i am a new user of this bot and i must say i love it, it works great cept for 1 minor detail

after i fish my delay time for fishing is random, sometimes it will wait exactly the time limit and sometimes it takes like 5 min for it to cast. is there a way i can fix the delay time from cast to cast?

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Does it say:

Obtained: 3 Fish etc.

If it doesn't have the first word Obtained: in then it's not going to work. If this is different than the others, let me know and I'll find a screenshot of the pixel event.

Just caught a batch of three, you're correct, it doesn't say obtained, I never realized that. It says:

You caught '3 <whatever>'!

With the "You caught" being the standard white text and the "# whatever" being the standard green.

Thanks again! I'll load up fraps this time too, let me know if you need a screenshot.

--Edit--

Additionally, I'm having the same issue as LifestoneExpress. I didn't notice it before, because I was in a busy area with a lot of chatter, which was forcing the failsafe. However, once I hit a quiet spot, it stops recognizing bites after the first catch. Very strange... we must be overlooking some setting that's different from your own.

--Edit Edit--

Incase it wasn't clear, the above didn't happen with the previous script (from the other thread). The only error the two seem to share is the one with catching multiple fish which we just identified. Something new is causing this...

Edited by falcon

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Additionally, I'm having the same issue as LifestoneExpress. I didn't notice it before, because I was in a busy area with a lot of chatter, which was forcing the failsafe. However, once I hit a quiet spot, it stops recognizing bites after the first catch. Very strange... we must be overlooking some setting that's different from your own.

This is the issue I noted earlier. The script is seeing what you did last time when it goes to read the pixels and is prematurely setting $event to 1...

I have tested it and one way to fix this problem is to turn on your reactive window sizing and set it to slightly slower than the default. Every single hooked fish resulted in {ENTER} firing as it should.

Edited by cgicw

Share this post


Link to post
Share on other sites

Posted · Report post

Falcon,

Yes I need a screenshot in 1280 x 1024 mode. Send me a link via PM if you don't want others to see your uplink spot. I'll add the code in asap.

Arrow,

It means that your events weren't seen so you have to wait for the $failsafe to trigger the event notifier. I would suggest you do nothing for now except move to a quieter area so you don't get a lot of chatter. If you have a busy linkshell equipped, remove it while you fish.

Cgicw,

I thought I was following you earlier but now I'm not so sure. I do not have reactive window sizing on and it's working perfectly for me. If you have it on, you should turn it off. Otherwise, if you are hitting a multiple event it's because the $failsafe kicked in. I'm sure of it.

Okay folks,

What I need to find out is how I can get the "You can't fish here" message to trigger. For some reason, the pixel color on that event message is so far off in different areas that even by finding 3 common numbers, I'm still not able to get an event trigger off of it. Because of this, the pause is not working.

I'm not sure what Ironfist used for his pixel coloring marks on that message. Ironfist if you read this can you give me some feedback on what areas of the message you forced a trigger to occur? This would help things out a lot.

Thanks.

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Good call Cgicw, that's interesting. I tried it at about 1/3rd full, and it was too slow to trigger anything. Instead opted for one or two (forget) clicks to the right of default, and now it's hitting enter every time. Not quite the 3-3.2 seconds it _should_ be, but it is hitting it every time. :) That said, still seems to be triggering the failsafe sleep time on occasion, resulting in some really long delays between casts. Seems like it's defaulting to about ~21 seconds between.

Happy to at least have it looping properly though. :)

--edit--

For what it's worth, here's my situation:

With static window size, or the reactive set too slow, it fails to hit enter as mentioned before. For _some reason_ by doing what Cgicw mentioned above, it makes enter actually fire with regularity. I can't even begin to pretend I understand why this is.

Screenshot links incoming shortly.

Edited by falcon

Share this post


Link to post
Share on other sites
Sign in to follow this  
Followers 0