If you'd have clicked on the 'More Information' link on the product page for this software, you'd have been taken to the developer's site. There, you would've read this:

Q: "Isn't this a violation of the WoW Terms of Service (ToS)?

A: "Yes. Using GoneFishing to fish for you is totally, 100%, against the ToS. Use this at your own risk -- you might get your account banned (and don't say I didn't warn you). However, if you are smart about when and how you use it, you probably won't get caught. See "How to not be stupid" further down the page."

Also the guy is trying to get you to give him $7 for "extra features". $7 to get your account suspended is just not worth it. People who cheat on WoW really make me mad. Hopefully Blizzard shuts him down.

GoneFishing is free and requires no money to use. The program never expires, and you may use it to fish for as long as your heart desires.

That said, I am sorry, iGaucho, if I've offended you in some way with the release of this application. However, I felt compelled to provide a solution to the mind-numbing adventure that is leveling to 375 fishing in World of Warcraft. I'm already sitting here playing a video game... the last thing I want to be doing is boring myself to death inside said game.

Strangely, some people appear to agree with me.

Sorry. I guess I overreacted a little bit. I do agree that fishing is not the most exciting part of the game. I also think that your time is probably better spent sending a suggestion and starting something to get Blizzard to improve the ability. It's really not fair to the rest of us who play fair and have to suffer through this occasionally tedious task. It's also not right for people to lose their privilege to play the game as a result of your software. I know I can't stop people from making this type of software or other hacks or cheats, but I hope that you warn users before they install it. I'm sure not everyone will see the disclaimer on your website.

Nobody is forcing anybody to use this app, and my website is QUITE clear about the TOS ramifications (not to mention this thread is, as well). I make no secret of it. While I cannot force everybody who downloads this app to read the information on my website, I would similarly argue that:

1) It is not my responsibility to do so, and:
2) If they play WoW, they have already read & agreed to the WoW TOS.

But then again, if a user never bothered to read the WoW TOS (which, as you know, is presented at install and after EVERY patch to the game -- of which there have been numerous), why would they read any information about this app?

Either way, I've updated the description here with a note about TOS violation (pending MU approval, of course). If people don't read my website, OR the description here, OR the WoW TOS then... well, I'm at a loss.

Turn up your graphics (spell detail, full screen glow) and zoom your camera all the way in to first person. Make sure to turn on auto-loot in WoW (interface options). If it's finding the bobber, those steps will help you catch fish.

I seem to be having trouble as well. It'll cast over and over, but never auto loot. I'm in first person, color set to the red feather, spell detail on max and full screen glow on.

Any ideas? I'm running 10.5.1 if that means anything.

Try using the "Scan Offset" settings in the preferences to center the captured bobber area around the base of the bobber, rather than the feathers. This usually involves moving the captured area to the left (negative x offset) and down a bit (negative y offset). You'll have to play around with the numbers to find good values for your screen resolution.

While the feather color is great for identifying the bobber itself, the base is the most distinctive area that changes when a fish is caught (ie, it disappears around the *splash*). Centering the scan area on the base, as well as expanding the scan radius if necessary, will help GoneFishing to accurately determine when a fish is caught.

I hope that helps.

As an addendum, I discovered an endian issue tonight on Intel machines that may have been causing the odd behavior you have noticed with regards to finding the bobber. Please upgrade to version 1.1.3 and let me know if this solves any of your problems :)

don't work.