[Release] Free FFXIV Fishing bot. Works with 2.5.1

jelio · 03/29/2015, 08:49

Hmm. It still happens for me every time I do this:

Launch the game.

Log into Character 1.

Launch the bot.

Start and stop the bot to confirm it's working.

Log out of Character 1. Leave the game client opened.

Log into Character 2.

Attempt to start the bot. Parsing hotbar error.

Close and relaunch the bot. Attempt to start the bot. Parsing hotbar error.

EN Client. Windows 7 64bit.

The workaround for me right now is to close the game client entirely when switching characters.

tyas1999 · 03/29/2015, 09:09

So far my only issue is that if I set release or do releases, the bot donks out trying to cast on a release fish.

jelio · 03/29/2015, 09:27

On a line break with sinking minnow.

Bot status log:

Code:

[3:23:18] Casting fishing line!
[3:23:47] You got a bite!
[3:23:53] Index was outside the bounds of the array.
[3:23:53] Bot stopped!

In game:

Code:

[3:23]You cast your line at the middle Hathoeva River.
[3:23]Something bites!
[3:23]Your line breaks!
[3:23]The fish gets away with your sinking minnow...

It was a heavy tug from The Sinker big fish. [edit] Standing, if it matters.

[edit3] Removed chat detection problem until I can reliably reproduce it.

LuckOnCooldown · 03/29/2015, 12:59

Quote:

Originally Posted by tyas1999

So far my only issue is that if I set release or do releases, the bot donks out trying to cast on a release fish.

Grab the 0.9.7 release I posted on page 6, or wait until later after I test some stuff and post it myself on the front page. That issue should be fixed in that version.

Quote:

Originally Posted by jelio

Hmm. It still happens for me every time I do this:

Launch the game.

Log into Character 1.

Launch the bot.

Start and stop the bot to confirm it's working.

Log out of Character 1. Leave the game client opened.

Log into Character 2.

Attempt to start the bot. Parsing hotbar error.

Close and relaunch the bot. Attempt to start the bot. Parsing hotbar error.

EN Client. Windows 7 64bit.

The workaround for me right now is to close the game client entirely when switching characters.

Yeah, this works for me. I don't know what to do about it if I can't reproduce it. :/

Quote:
Originally Posted by jelio
On a line break with sinking minnow.

Bot status log:
Code:
[3:23:18] Casting fishing line!
[3:23:47] You got a bite!
[3:23:53] Index was outside the bounds of the array.
[3:23:53] Bot stopped!
In game:
Code:
[3:23]You cast your line at the middle Hathoeva River.
[3:23]Something bites!
[3:23]Your line breaks!
[3:23]The fish gets away with your sinking minnow...
It was a heavy tug from The Sinker big fish. [edit] Standing, if it matters.

I've literally never had a line break. Not even once in all the fishing I've done. Clearly, it's the same issue that TomHanks was having before. The bot didn't recognize the line break, and tried to read the fish name, and it wasn't there, and ended up reading junk from memory. I don't know what to do about it though until I get a line break myself and can examine memory to figure out what I need to check for.

tomhanks123 · 03/30/2015, 03:48

Quote:

Originally Posted by LuckOnCooldown

Grab the 0.9.7 release I posted on page 6, or wait until later after I test some stuff and post it myself on the front page. That issue should be fixed in that version.

Yeah, this works for me. I don't know what to do about it if I can't reproduce it. :/

I've literally never had a line break. Not even once in all the fishing I've done. Clearly, it's the same issue that TomHanks was having before. The bot didn't recognize the line break, and tried to read the fish name, and it wasn't there, and ended up reading junk from memory. I don't know what to do about it though until I get a line break myself and can examine memory to figure out what I need to check for.

The easiest way to get a line to break is fish for Gigant Clams at Costa Sol with me :P. Having said that, it's been awhile since I had an error (haven't had any since 0.9.7 and no fish have stolen my lure yet.

Update: Lost a lure just now but no error.

Lost the lure several times with no error, for the record I was using heavy still jig. Perhaps try with jelio one of sinking minnow. I think different lures can have different reeling states. (fresh water/coast/seawater etc)

LuckOnCooldown · 03/30/2015, 20:29

Quote:

Originally Posted by tomhanks123

The easiest way to get a line to break is fish for Gigant Clams at Costa Sol with me :P. Having said that, it's been awhile since I had an error (haven't had any since 0.9.7 and no fish have stolen my lure yet.

Update: Lost a lure just now but no error.

Lost the lure several times with no error, for the record I was using heavy still jig. Perhaps try with jelio one of sinking minnow. I think different lures can have different reeling states. (fresh water/coast/seawater etc)

They do, and that's accounted for, but as far as I can tell, there is only one "Unsuccessful" state. See the following code:

Code:

        private static Dictionary<int, string> FishingState = new Dictionary<int, string>
        {
            {0,  "Unknown"},
            {2,  "Not Fishing"},
            {35, "Fishing Stance"},
            {37, "Packing Up"},
            {38, "Casting"},
            {39, "Casting"},
            {40, "Casting"},
            {41, "Fishing"},
            {42, "Fishing"},
            {43, "Fishing"},
            {44, "Fishing"},
            {45, "Fishing"},
            {46, "Fishing"},
            {47, "Unsuccessful"},
            {48, "Successful"},
            {49, "Reeling"},
            {50, "Reeling"},
            {51, "Reeling"},
            {52, "Reeling"},
            {53, "Reeling"},
            {56, "Bite"},
            {57, "Bite"},
            {58, "Bite"}
        };

Notice how "Unsuccessful" is 47, and 46 and 49 are already accounted for with Fishing and Reeling states. That's not proof positive of anything. There could be another state @59 that I'm missing. But it is an indicator.

lol2k6 · 03/30/2015, 22:19

Can Square Enix detect the bot as its messing with files? Or can you only get banned if you afk bot, someone reports you and you dont respond etc.?

LuckOnCooldown · 03/31/2015, 00:42

Quote:

Originally Posted by lol2k6

Can Square Enix detect the bot as its messing with files? Or can you only get banned if you afk bot, someone reports you and you dont respond etc.?

It doesn't mess with any files...

Nefeltari · 03/31/2015, 01:48

The hotbar parsing did not work for me and presses the wrong keys. I use an english client and havent activated the cross hotbars. I removed any Fishing Skill from the cross hotbars. It seems the bot cant find the right key, because he press 'p' and 'n' or 'f' instead. In my keybinding configuration some windows lays on this keys like Achievment or Party Finder and not any fishing skill. Each time i start the bot he opens/close this windows in believe that where the right skill for Cast/Hook.

Log:

Code:

[1:14:58] Bot Started!
[1:15:00] Mooching to catch a bigger fish!
[1:15:02] Expected status 'Casting' or 'Fishing', but got: 'Not Fishing'
[1:15:02] Bot stopped!

The mooching statement is also strange because i only stand for the fishing spot with the right bait and the availability for fishing (the Mooch option is ticked). I tried to restart the bot and client several times with no luck. I have no idea what causes this strange problem. If you need any additonal informations i think that is not the problem.

ThePoroKing · 03/31/2015, 03:43

patch 2.55 coming up in several hours, do you think ALPHA v0.9.6 can still work ?

Thanks for continuing the legacy !

LuckOnCooldown · 03/31/2015, 04:02

Quote:
Originally Posted by Nefeltari
The hotbar parsing did not work for me and presses the wrong keys. I use an english client and havent activated the cross hotbars. I removed any Fishing Skill from the cross hotbars. It seems the bot cant find the right key, because he press 'p' and 'n' or 'f' instead. In my keybinding configuration some windows lays on this keys like Achievment or Party Finder and not any fishing skill. Each time i start the bot he opens/close this windows in believe that where the right skill for Cast/Hook.

Log:
Code:
[1:14:58] Bot Started!
[1:15:00] Mooching to catch a bigger fish!
[1:15:02] Expected status 'Casting' or 'Fishing', but got: 'Not Fishing'
[1:15:02] Bot stopped!
The mooching statement is also strange because i only stand for the fishing spot with the right bait and the availability for fishing (the Mooch option is ticked). I tried to restart the bot and client several times with no luck. I have no idea what causes this strange problem. If you need any additonal informations i think that is not the problem.

That's extremely weird. I can't imagine what might cause it to break for you and you only.

I will tell you this, at least Cast, Hook, and Quit have to be on your bar with hotkeys, or it will say the parsing failed. It doesn't sound like that's your issue though.

Can you post a screenshot of your hotbars and your hotbar settings window? Maybe I can figure something out from there.

Quote:

Originally Posted by ThePoroKing

patch 2.55 coming up in several hours, do you think ALPHA v0.9.6 can still work ?

Thanks for continuing the legacy !

Grab 0.9.7 on page 6 of this thread. The fact that I'm using signature scanning means it *should* still work, but there's always a chance things will break.

tomhanks123 · 03/31/2015, 04:04

Quote:

Originally Posted by ThePoroKing

patch 2.55 coming up in several hours, do you think ALPHA v0.9.6 can still work ?

Thanks for continuing the legacy !

The latest version is 0.9.7, i think LuckOnCooldown didn't put it on the front page yet but it's somewhere in the last page or two. I think the new patch will screw up with soem offsets again but I think the process of finding them is already sorted? So perhaps not a huge downtime. Correct me if wrong.

LuckOnCooldown · 03/31/2015, 04:57

Quote:

Originally Posted by tomhanks123

The latest version is 0.9.7, i think LuckOnCooldown didn't put it on the front page yet but it's somewhere in the last page or two. I think the new patch will screw up with soem offsets again but I think the process of finding them is already sorted? So perhaps not a huge downtime. Correct me if wrong.

I didn't post it on the front page, because it was completely untested code. However, you guys have been using it for a couple of days, and it seems to be the most stable version yet. I've just been a little busy and haven't had a chance to update the front page.

MapleStoryTeller · 03/31/2015, 09:03

Chiming in, I've been using 0.9.7 and it's been working fine without any problems so far

tomhanks123 · 03/31/2015, 12:38

confirmed, 0.9.7 works with patch 2.55. Just tested :3.