Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autogig can miss very fast fish because it doesn't account for gig travel time #45

Open
retep998 opened this issue Jul 23, 2024 · 0 comments

Comments

@retep998
Copy link

retep998 commented Jul 23, 2024

Autogig seems to not take into account the time it takes for the gig to travel upwards, and that fish will have moved in that span of time.
For really fast fish this can mean if the fish is in the top row the gig will miss the fish entirely as the fish has moved out of the way before the gig could get to it. The same exact fish in the middle or bottom row is just fine however.

Offset adjustment is not a valid solution as some fish are so fast (for example the Wivre Cod), that tweaking the offset enough to hit the top row means it will miss the bottom row instead!

Also it would be great if I could tell it to prioritize catching the fish over using nature's bounty if there's not enough time to use nature's bounty and still be able to catch the fish. This most notably happens right after catching another fish and the next fish is already on screen, it will use nature's bounty while the fish is actively passing the gig, and then just sit there because the fish already moved out of the way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant