JacklynnB
commented
1 month ago Would really like to know if there's an easy way to fix this! We have a lot of history stuck on a save we can no longer access until this issue is fixed! Thank you.
Open JacklynnB opened 1 month ago
JacklynnB
commented
1 month ago Would really like to know if there's an easy way to fix this! We have a lot of history stuck on a save we can no longer access until this issue is fixed! Thank you.
CrispyChaos
commented
1 month ago ditto! It continues the issues even if you roll back to 4.0-458 AND 4.0-457. It continues to flag SPECIFICALLY ticking on the player (via Neruina) with quark at 4.0-459. Il attach my Crash Logs with the testing on our groups server with the (versions) of Quark used and hopefully thats of some help. crash-2024-08-03_21.16.45-fml.txt crash-2024-08-03_21.17.25-fml.txt
vizthex123
commented
1 month ago Same issue here.
Log: latest.log
UltrioG
commented
1 month ago Ditto.
Crash report: crash_report (latest.log exceeded pastebin limit, sorry)
GustavDjavulen
commented
1 month ago Downgrade
• Zeta to "1.0-19" • Quark to "4.0-455"
It worked to me
AmanoMoriya
commented
1 month ago Same problem happened to me as well
latest.log crash-2024-08-04_07.57.28-fml.txt
EDIT: I ended up downgrading both Quark and Zeta until it gets fixed or a solution is found.
ModernGamingWorld
commented
1 month ago Its Zeta latest update caused the crash, I was able to update just Quark without Zeta and no crash. My guess is @Vazkii pushed a update of Zeta without checking to see if Quark's current update worked with it
me and a friend have had a small local lan server set up recently and had little to no issues, however after today's (8/3/2024) update to the mod, both of our clients boot almost 50%, then crash. Tested with blank profiles only containing quark & zeta, and recreated the crash several times.
(BIGGER MODPACK LOGS AND MODLIST) crash-2024-08-03_21.43.27-fml.txt latest.log
(ONLY USING QUARK LOGS AND SCREENSHOT) latest(1).log
crash-2024-08-03_21.52.50-fml.txt