[Release] Free FFXIV Fishing bot. Works with 2.5.1

[SimplyUnwanted]

I tested the "Macro" as I like to call it since I wouldn't consider myself a botter, out last night and strangely enough I had the "Parse Hotbars" and the previous issue I had with Zagans build and this build was the program not registering the casting 3 times then stopping. I turned FF14 off, the program off, went to sleep and woke up, turned FF14 back on and then opened the Macro.

Oddly enough it is working now no issues so far, I guess there is some kind of problem because when I went to try restarting FF14 and the program last night it still gave me errors, I would recommend waiting until FF14 has been turned off for a day to try and fix these issues.

Thank you for the program nonetheless fishing is a nice skill but after going 2 weeks for 50 crafting and gathering skills I'd rather do it this way while I watch :P

[LuckOnCooldown]

Originally Posted by SimplyUnwanted

I tested the "Macro" as I like to call it since I wouldn't consider myself a botter, out last night and strangely enough I had the "Parse Hotbars" and the previous issue I had with Zagans build and this build was the program not registering the casting 3 times then stopping. I turned FF14 off, the program off, went to sleep and woke up, turned FF14 back on and then opened the Macro.

Oddly enough it is working now no issues so far, I guess there is some kind of problem because when I went to try restarting FF14 and the program last night it still gave me errors, I would recommend waiting until FF14 has been turned off for a day to try and fix these issues.

Thank you for the program nonetheless fishing is a nice skill but after going 2 weeks for 50 crafting and gathering skills I'd rather do it this way while I watch :P

Yeah, there is an issue apparently when you logout out to the login screen then back in. It could be showing up in other places too. The current "fix" is just to stop the bot, restart FFXIV entirely, then start the bot. This has been working for everyone so far.

This won't make any sense to you if you're not a programmer, but the problem is when you log out to the login screen, then back in, the pointer chain that points to the hotbar data in memory changes. It's usually the last pointer that becomes invalid. It's really odd. I've never seen anything like it.

Originally Posted by tichondrius255

Lol I can sound quite unappreciative but this thing is awesome! As always the holy grail of automation is to minimize supervision but this is definitely way better than fishing myself .

You didn't sound unappreciative. I just like my software to be perfect, and I'm not happy until it is!

[Sony2103]

I always have the problem that it indicates to me that it can not parse the buttons analsyieren what am I doing wrong? !!??

[MaugrimWolf]

As of right now this bot is working like a charm! I'll let you know if I encounter any issues, but as it stands I've landed 3 Marlins effort free so far with this bad boy.

[plebe07092]

Hello. Would like to ask on how to fix the error "unable to parse hotbar". keeps on appearing. Thank you

[kernza]

this is the error i'm getting when i try to fish.
[1:20:36] Casting fishing line!
[1:20:38] Expected status 'Casting' or 'Fishing', but got: 'Fishing Stance'
[1:20:38] Bot stopped!

I tried the closing the bot and then FF14 and then restarting ff14 and then the bot but still getting the same error.

[NotKeepingThis]

Just make an option for us to put hotkeys in standard places, or to parse the hotkeys and crash the bot.
I'm perfectly happy to put cast in 1, catch in 2, mooch in 3 and quit in 4 if it means I don't have to repeatedly restart the client every time I change class.

[jelio]

Originally Posted by NotKeepingThis

Just make an option for us to put hotkeys in standard places, or to parse the hotkeys and crash the bot.
I'm perfectly happy to put cast in 1, catch in 2, mooch in 3 and quit in 4 if it means I don't have to repeatedly restart the client every time I change class.

See .

Summary: in order to get Mooch working (without using mooch/cast macro in one, I suppose), he needs to parse hotbars, maintain a list of moochable fish, or parse the chat log. The first option is the apparent path of least resistance.

[lucid]

Originally Posted by jelio

See .

Summary: in order to get Mooch working (without using mooch/cast macro in one, I suppose), he needs to parse hotbars, maintain a list of moochable fish, or parse the chat log. The first option is the apparent path of least resistance.

Or see the source of that information (6 months prior), ! Part of the original discussion when Stolas was still working on the original version of the bot.

Anyhow that doesn't really prohibit what NotKeepingThis was asking for in his request. It is entirely possible to press the mooch key without knowing mooch is available, though it would be naive and unable to isolate/target specific mooch chains. Alternatively a different mooch detection method could be employed if fixed keys [1=Cast, 2=Hook, etc...] were used.

It is possible to parse hotbar info from the binary hotbar.dat file.

There is also a second copy of hotbar info in memory which could be used.

The chatlog or on-screen info are also possible sources (the on-screen info is inaccurate if the user hovers any items while fishing is underway).

The existing pointer chain could be fixed so it always points to the most recent set.

It is also entirely possible that the pointer is fine but not updating the hotbar address is what causes this; I'm not sure because I haven't looked at the in-memory data structure which is in use. is run only once afaik and it loads _offsets. If the derived offset is changed, the data structure has no way of changing because it is not lazily evaluated nor recalled. I'm also not sure if the repo is up-to-date (last updated 16 days ago) so that might be inaccurate.

[philtee]

thanks for the work you put in this. so far it has worked well for me. did find one error when the fish gets away the bot stops. my fishing is too low for some of the fish...anyway just an fyi

[tyas1999]

Originally Posted by plebe07092

Hello. Would like to ask on how to fix the error "unable to parse hotbar". keeps on appearing. Thank you

At the moment this should only be occurring in the situation of having returned to the character select after your initial login, either for being disconnected or switching characters.

For the time being the only solution is to exit out completely and log back in.

The dev is working on another fix but because of the way this works (to make it work most efficiently) it is a bit twitchy.

Originally Posted by LuckOnCooldown

Be patient, and I hope it's working well enough to keep you guys satisfied for now.

Hey it works most of the time and the price is right, I'm happy.

Thank you.

Originally Posted by LuckOnCooldown

FYI guys, I'm probably going to be unavailable for the next couple of weeks or so. I'm expecting a little one, and there's lots to get done around the house, and lots of stuff the wife can't do for herself anymore.

I haven't stopped working, I've just slowed down a good bit!

Hope your little one goes well. Also, figure the time you're going to be shorted, then multiply by 2.

[LuckOnCooldown]

Originally Posted by lucid

Or see the source of that information (6 months prior), ! Part of the original discussion when Stolas was still working on the original version of the bot.

Anyhow that doesn't really prohibit what NotKeepingThis was asking for in his request. It is entirely possible to press the mooch key without knowing mooch is available, though it would be naive and unable to isolate/target specific mooch chains. Alternatively a different mooch detection method could be employed if fixed keys [1=Cast, 2=Hook, etc...] were used.

It is possible to parse hotbar info from the binary hotbar.dat file.

There is also a second copy of hotbar info in memory which could be used.

The chatlog or on-screen info are also possible sources (the on-screen info is inaccurate if the user hovers any items while fishing is underway).

The existing pointer chain could be fixed so it always points to the most recent set.

It is also entirely possible that the pointer is fine but not updating the hotbar address is what causes this; I'm not sure because I haven't looked at the in-memory data structure which is in use. is run only once afaik and it loads _offsets. If the derived offset is changed, the data structure has no way of changing because it is not lazily evaluated nor recalled. I'm also not sure if the repo is up-to-date (last updated 16 days ago) so that might be inaccurate.

Thanks Lucid. The repo is not quite up to date, but close enough. The problem is, it actually doesn't matter if call FindOffsets() again. The hotbar data in memory doesn't move, but the last pointer in the pointer chain gets incremented by exactly 1024. I have no idea wtf is going on with that, and I haven't had time to run it down.

The wild part is, it happens with the first scanned address I used as well. At this point, I'm thinking about requiring you to have cast on 1 and using that to find the hotbars in memory. That's such a hack though...makes me feel unclean...

Sorry I haven't been around much guys, like I said before, the wife is about to pop. I really don't have time to work on this at the moment. I will get back to it though, I promise.

[dizuane]

When fishing in The Brewer's Beacon (Western La Noscea), Silver Dagger HQ produces the error below. This ONLY happens with HQ Silver Daggers. It also does not log it (may have something to do with that?)

[12:32:32] You got a bite!
[12:32:42] Index was outside the bounds of the array.
[12:32:42] Bot stopped!

[Syfhon]

Hey boss! Works great out of the box. Thank you for all your hard work making this for everyone.

[darklion666]

hey works great ! , tough i had problems at the start where i needed to have "hook" in the 2nd slot and it also wanted to catch at 2nd slot
if anyone has this problem i solved it with putting a marco on second slot
"
/ac Hook <me>
/ac Mooch <me>
/ac Cast <me>
"
that should solve the problem