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

Issue on servers (RLcraft) #17

Open
Skothophagotis opened this issue Jan 15, 2024 · 3 comments
Open

Issue on servers (RLcraft) #17

Skothophagotis opened this issue Jan 15, 2024 · 3 comments

Comments

@Skothophagotis
Copy link

Skothophagotis commented Jan 15, 2024

Hi, I just started playing with friends on an RLcraft private server. When trying to fish, we get the message 'There doesn't seem to be biting anything here.' It's working on non-server. We also set up bait traps and tried putting in raw meat, carrots (as seen on YouTube), but we get a message that it's not a valid bait. We tried toggling flying on and off (left it on). Is there any way to fix this?

Edit: We tried it in rivers, shallows, oceans and it doesn't seem to be working, we tried to dig up 3x3 with baiting box inside which didn't help too. Tried different rods with differend bobbers and still same issue. Combining rod + bait in crafting doesn't work too. Tracker doesn't find anything too.

@KameiB
Copy link
Contributor

KameiB commented Jan 16, 2024

I think it would help more if you Link the config files located in your server and latest.log.

@Skothophagotis
Copy link
Author

Im sending logs and config from server
config.zip
hs_err_pid31678.log

@KameiB
Copy link
Contributor

KameiB commented Jan 18, 2024

Hi again!
I just contributed to the localization, so I'm not too deep in the mechanics, but...

Just in case,
In fishingmadebetter.cfg :
Have you tried reseting:
"Tracking Time" to 5
"Fish Regeneration Time" to 60

If I remember correctly, "Tracking Time" must not be too low, so 5 should be the sweet spot.
About "Fish Regeneration Time", you can try lowering its value little by little until you find the desired sweet spot.

I hope it helps!

If the problem persists, can you post the latest.log instead of the crash report?

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

2 participants