so me and my friends have been playing on a multiplayer server for a about 2 and a half weeks now and we have been trying everything to fix this crashing problem, the people over at bisect have tried to figure it but cant. please help were so tired of crashing we just want to have fun. I can provide all of my crash logs since redownloading the pack, BisectHosting staff said to try fully deleting and reinstalling the pack the last time. also side note I am not the owner of the server, my friend is.
#Crashes back to ATLauncher when clicking quest book or trying to use REI
balmy bloom
high laurel
Please send your crash logs, because without them it's like reading tea leaves. (No offense to real witches)
balmy bloom
Please send your crash logs, because without them it's like reading tea leaves. ...
also when replying to this could you please @ me so I get a notification for this thread
this is all I have so far since redownloading the pack
balmy bloom
just crashed again after already opening the book and using it but almost every time I crash it's as soon as I click the quest book
heres the crash log for it
balmy bloom
quaint sinew
try adding this https://modrinth.com/mod/bugjump
balmy bloom
this crash happened in mid air I never opened anything
I hope these aren't too much I just really want to stop crashing
I'm sorry if I'm sending too many
quaint sinew
did you add the mod?
balmy bloom
did you add the mod?
I'm not the owner of the server and it only happens on multiplayer but I just did speak with my friend who DOES own the server and she said that she couldn't figure it out so she's having the BH staff install it for her
quaint sinew
it's a clientside mod...
balmy bloom
oh okay let me see
I'll have to let you know if it works or not later after my kids go to sleep. don't have time to play now that their nap is over
balmy bloom
did you add the mod?
so far so good! thank you so much for helping us out I'll update if anything changes.
high laurel
@balmy bloom I'm sorry I was busy with real life and couldn't get back to you. All them errors were a result of /calling for the value while no value was yet provided/, which has a solid background of possible events, related to more likely rendering distance, libs loading, calling for databases to check them contents and many more. The response time for them to return proper values was too short so if the function asking for that check did not receive the value in time - it was shutting out, crashing. Few things can help in this matter, from reducing the amount of data that's in the flow, reducing the distance rendering, actions per same chunk you are performing the function call at, but, best solution already provided above - a simple client-side tool that fixes such response times (and many more) and checks if there are actually any "values" for the requested stuff, if they are, no crash would happen, else you will get detailed info to which is missing 😅
@quaint sinew Thanks for helping them all out here 👍
balmy bloom
<@308125116527804420> I'm sorry I was busy with real life and couldn't get back ...
Don’t worry about it I understand everyone has a life outside of their online persona. I really appreciate the in depth explanation and thank you guys for having such a timely response. I didn’t have the same experience with the ATLauncher discord lol. Took about 3 days before anyone saw it.
Is there a way to close this thread now that my issue is fixed?
high laurel
Is there a way to close this thread now that my issue is fixed?
It will get archived soon by automation, but since the moderators are checking them threads daily I'm sure the appropriate actions are taken once someone's available.