Autoit bot(Craft/Fish) - Simple bot

Quote:

Originally Posted by 13ouncer You should record your pixels.

I did, i record always window1 to 3 for the first before starting fish bot ;;
It may be true that bot cannot find/read window2 pixel?
i just had ff xiv and Bot up on screen

Quote:

Originally Posted by Neshl I did, i record always window1 to 3 for the first before starting fish bot ;; It may be true that bot cannot find/read window2 pixel? i just had ff xiv and Bot up on screen

Check your pm nesh. I am in the.process of setting up my pc now so I can post more often.

@Nesh and Neko, try changing
Movedelay=500 to higher number.

Quote:

Originally Posted by Neshl I did, i record always window1 to 3 for the first before starting fish bot ;; It may be true that bot cannot find/read window2 pixel? i just had ff xiv and Bot up on screen

Are you moving your mouse around while FF XIV window is active?

Quote:

Originally Posted by Neshl The bot now is just spaming "Jig nummber x perfomed" before it feel a fish bait anyway.. it seems that the bot starts "Jigs" too early before it feel fish bait but i think its a bug which shouldn´t do that early.. fishing interface was at the up left corner and bot window under the fishing interface. Im using the 5.4e one and didn´t change things at ini. well should i manually enter something there?

It sounds like you have pixels that are incorrect. The bot loops until a pixel is found then moves to jigging. Your pixel seems to not be changing which leads me to believe that you are not recording things correctly or moving fish window in correct place.

Try starting bot, minimize the bot, then don't move the mouse. keep everything still.

I am positive it is not a bot/code issue, but rather user error since most of the errors so far are related to the user not placing the window in the correct place or misunderstanding how the bot needs to be setup.

Every error you get in the bot will be because a pixel is recorded incorrectly. It all leads back to pixels because the bot runs off of pixels. If one is wrong the bot will not work.

Quote:

Originally Posted by 13ouncer It sounds like you have pixels that are incorrect. The bot loops until a pixel is found then moves to jigging. Your pixel seems to not be changing which leads me to believe that you are not recording things correctly or moving fish window in correct place. Try starting bot, minimize the bot, then don't move the mouse. keep everything still. I am positive it is not a bot/code issue, but rather user error since most of the errors so far are related to the user not placing the window in the correct place or misunderstanding how the bot needs to be setup. Every error you get in the bot will be because a pixel is recorded incorrectly. It all leads back to pixels because the bot runs off of pixels. If one is wrong the bot will not work.

Yes, i minimized the bot after i started fish bot and didn´t touch mouse at all and there´s no diff.

Still not working. It just quits after a couple of casts for no reason. I don't understand why it works for like 20 casts then just quits. =/

Here's the last few lines of my log, if that helps?

Bait OK!
Checking Depth.
Depth Set.
Waiting for fish.
Jig number 2 performed.
Cannot find window 3, or tired pixels. Please confirm again.
All bots deactivated.
Press again to activate.
Starting new fish session.

EDIT: I've recorded all of the windows many times, and I'm not moving my mouse AT ALL.

fyi, im working on changing a bit of code with the fish bot. It should fix the issue that some are having.

@Nesh, Try the version I have attached to this post. Let me know if the problem still persists.

Quote:

Originally Posted by 13ouncer @Nesh, Try the version I have attached to this post. Let me know if the problem still persists.

Yep, i got it.

Thnx a ton!!

Quote:

Originally Posted by 13ouncer @Nesh, Try the version I have attached to this post. Let me know if the problem still persists.

Still not working for me. Worked fine for 1 cast then the next one it just kept hitting "Wait" while in the log it said it was trying different Jig positions.

Quote:

Originally Posted by nekopoke Still not working for me. Worked fine for 1 cast then the next one it just kept hitting "Wait" while in the log it said it was trying different Jig positions.

Look at the youtube videos. At this point any error will be a user error. It is not a problem with the bot.

I haven't seen much in the way of this by anybody else but I usually use it while working so I can keep an eye on any messages and anything that's going on with the game. As I don't AFK bot for many reasons this may be a minority issue but here goes.

Sometimes the bot will trigger or trip my caps lock, and act as if it's holding down the caps lock or shift key. To the point that "," will become "<" as well as all the other issues coming from holding down shift such as selecting large amounts of text or multiple files on the computer.

Mostly this can be solved simply by tapping the shift key again or holding it and typing or tapping the caps lock. This is no way a human error, i am not in any way hitting the caps lock key on my keyboard and it's happened across multiple computers with others using them. I wondered if there is any way to stop it? It seems whenever this occurs the caps lock LED on the keyboards will light up as if it's been pressed, every time the bot does an action with synthesis or jigging.

Additionally if you try to correct it too fast it bot seems to almost "fight" with you and force the text back to the shift enabled variant, and eventually it can lead to a glitch where despite closing out the bot, the shift key is still seemingly held down by the computer, and only a restart seems to fix it.

I've had no other issues with the bot and it works perfectly and I would like to express my thanks for the hard work you've put into this, I was just curious if this was a known bug or issue, or if it's something that hasn't really been known yet. Is it fixable by minimizing the screen or some other small seemingly simple task? I make sure the directs are followed, and I've never tried minimizing or covering the left half of the screen (figured they needed to be seen for pixel detection to work) so I am unsure as to what I could do that would fix it if it's an error on my end. I would like to note that I am using 5.4e, I am now trying 5.4f and I'll edit this post if the issue resolves itself.

Any help would be greatly appreciated!

EDIT: Forgot to mention, the bot also completely disables the use of the "-" key, though the "-" key on the numpad works fine.

Oh man >.> it seems it does not like me? my resolution is 1280x720, Fishthing is up left, bot is down right, I click on record resolution, click on fish and it says Pixel error @ depth. why?

thats crazy man