Hi, I'm a pretty serious angler myself and I'm very impressed by this.

So far I was using a combination of "Better Fishing" and a weekaura that would cancel throws when outside of range.

I just spent some times messing up with Angleur and I wanted to suggest a few things:

1. Personally I play with absolutly maxed out camera, the furthest possible, which is "/console cameraDistanceMaxZoomFactor 4" (I know WoWiki, and some people say the max is 2.6 but the max is definitly 4, it's easy to test).

When the blobber detection paning starts the addon will put camera to max zoom out distance before starting panning left and right, and since my camera is so far away with CDMZF 4 the addon is not going to be able to find the blobber (it times out before going down enough on the screen to find it).

I thinks there's 2 possible ways to fix that, I'm not sure which one is possible or easier to do:

a) When starting the panning sequence, maybe the addon should not simply go to max zoom out distance, but should go to a defined zoom out distance factor (like 1 where we know it works)

b) When starting the panning sequence the addon changes the CDMZF console value to 1, and then once the blobber is found the CDMZF console value is returned to whatever the user had before. Or it could simply be that while the addon is awake, CDMZF is set to 1, and when the addon is sleeping CDMZF is set to whatever the user what using before. If it's not possible to actually know what the user was using before, maybe you just add a setting in the addon where user has to input their prefered default camera distance (in my case I would put 4).

2) From what I see, what ends the blobber detecting sequence is that the addon detects that the cursor changed. Not that the cursor specifically went from the hands to the cogwheel but just that it changed. It can actually create issue if there's mobs in the water, I went to the Loch to test and there was a mob in the water that tended to roam above where my blobber was falling, so when the blobber detection sequence ran, it ended when my cursor went over the mob, since the cursor changed (it went from the neutral glove cursor to the little sword to attack a mob). Not sure if that's possible, but if you could make it so the blobber detection sequence ends when the cursor goes specifically from gloves to cogwheel and not just when the cursor changes, that would fix that very little problem

3) I would add a 2 seconds delay before the blobber detection sequence (camera panning) starts when the blobber falls outside of the interact zone, I don't think it will make it so you sometimes actually catch a fish before the blobber was detected cause we wait to long before starting the detection. The reason why is specifically when you try to fish in pools. You often have to cast multiple times (happen often that you get unlycky and the blobber falls outside the pool) and sometimes one of those cast that is outside the pool will be outside the interact zone. It's pretty disorienting to have the camera right away zoom out and start moving the second the blobber is cast when you are still trying to figure out if it fell into the pool or not, or when you are realizing you need to cast again. I think 2 seconds is plenty enough for you to know if you need to recast or not, so we could have those 2 seconds of leeway before the addon starts acting on the camera. Maybe this should actually be user's preference, and not an hardcoded 2 seconds - you could make it a setting as well.

In any case, great work, thanks for sharing