I left 1 bread bait to reproduce the bug,and the video is here.

https://user-images.githubusercontent.com/64828020/136638301-01ee857f-70d5-428d-8f20-142e2b4a6d81.mp4

the console info:

Press f1 to start ... [Resumed] holding the rod putting on bait casting pressed - rod casted Gotta click this fish TIME TO FIGHT THE FISH release Hold1 Hold1 Hold1 Hold1 Hold1 Hold1 Hold1 release release Hold1 Hold1 Hold1 Hold1 Hold1 Hold1 Hold1 Hold1 release release Hold1 Hold1 Hold1 Hold1 Hold1 Hold1 Hold1 release Hold1 Hold1 Hold1 Hold1 Hold1 release release release release release release release release release release release Grats on the fish! (I hope) -- Restarting loop holding the rod putting on bait You dont have any bait left casting pressed - rod casted casting pole casting pole rod casted casting pole casting pole rod casted casting pole rod casted casting pole [Exit]

I set the waterType to 1,and my Python version is 3.7

When i fish in a hotspot, it has medium pertange to obatain a issue of line broke. I thought the configuration of reeling time or some number of it lead to this problem.

If i set the waterType when My baits have used up , the bot will not correct working . It may caused by the code at line 147: if status == 'readytocast' and waterType == 0 or hasBait == False:

so I changed the code into : if status == 'readytocast' and (waterType == 0 or hasBait == False):

Now the bots can work correctly : )

Not an issue but seemed the easiest way to share. I pulled the UI images from the data file, they are stored as dds but I also converted them to png. Not sure if it'll be helpful, they have transparent backgrounds so they probably could be used as a mask. It does contain all the possible tension icons fishing.zip .

Checking for the F3 image after catch allows it to wait longer for when you get a cutscene like rare pull but also know quickly when you're ready to recast on common fish.

Using the greyscale and region options on LocationOnScreen reduces the time for the function call to about 1/3 on the calls for the non-bobber icons. Example f3.png from 0.17 seconds to 0.066. Interact region is smaller than the center region for matching the bobber. Hold checks didn't work constantly well as grey scale but still resulted in about 1/2 the execution time with region. Either way, it should help on lower end machines and could offset the cost of checking f3.png in the release loop. The only issue would be if the game wasn't in 1080p but then the other screen offsets wouldn't work anyway and the matching image scaling would be wrong.