forge-autofish
forge-autofish copied to clipboard
North-West-Wind
Rod randomly retracts with no reason.
Describe the bug AFK fishing isn't possible because the rod seems to be getting reeled back in, even when there is no fish, and it seems the mod also doesn't realize this cause it doesn't recast. Also doesn't play the reel sound either when it happens. Tried adjusting recast delay to 1000ms but seems to make zero difference.
To Reproduce Run the auto fisher for more than a couple catches, sometimes happens after first cast, sometimes not. I could watch this happen 4-5 times in a few minutes, so much so, I chose to rather just fish manually.
Expected behavior AFK fishing.
Screenshots I could get a video but seems pointless with the reproduction rate.
Version Latest version(1.1.3) on MC 1.16.4, also in Singleplayer.
Video https://user-images.githubusercontent.com/11309486/103161269-059f7400-4794-11eb-89e3-fd69cccc4508.mp4
Issue is not fixed.
This is after 7 minutes of fishing, same issue. And yes, I am running the latest version.
I also get this with mod version 2.0.0. Cast rod sometimes autofishes sometimes pulls reel with nothing and doesn't recast.
Alright, I will take a deeper look into this.
The funny thing is that I've never encountered this issue in my test world.
@SpadeCA @Drunkender Do you both have rod protect enabled? If not, I won't have to investigate it.
Reset my config to be sure but yes rod protect is on by default.
Turning it off doesn't fix the issue.
Same issue here in 1.17.1 with AutoFish forgeautofish-3.0.2-1.17.x.jar Default config.
Now I'm trying with rodprotect = false and Reel-In Delay 100
Additional Info:
IllegalStack server plugin is detecting forge-autofish after 4-5 reels:
<nickname> appears to be using an autofishing mod.. 4 caught within 0.3 blocks of each other @ world x y z
IllegalStack server plugin is detecting forge-autofish after 4-5 reels:
<nickname> appears to be using an autofishing mod.. 4 caught within 0.3 blocks of each other @ world x y z
If the server doesn't want you to, stop using it. It is also irrelevant to this issue.
My last comment was for informational purposes, to add more details to the problem I was experiencing, and to clarify that the problem was not this plugin itself but the server configuration.
It may not seem relevant to you, but perhaps to someone it is.
Cheers!
I understand your intention, but it seems really odd just to separate them. I put that in your first comment.