Closed Created-Creation closed 6 months ago
Can you find your crash report over \modpacks\hexxit-ii\crash-reports\
and copy it over to https://mclo.gs?
Just pasted it in.
(closed on accident, issue remains)
Can you copy the link?
Right, my b
(accidental close again - new to github)
A bit of a shot in the dark, but can you try to disable Entity Tracker
(change value of from true
to false
) in \modpacks\hexxit-ii\config\UniversalTweaks.cfg
?
To find the modpack's installation folder:
- Select the
MODPACKS
tab, then click onHexxit II
- Click on
Modpack Options
⚙ in the top right corner- Click on
Open
at the top right corner of the pop-up window
Looks like the same things happened again
Thanks to a comment from @ACGaming, I can confirm that disabling EnableNaturalSpawn
is the cause for this issue. I will experiment with workarounds
Edit: It appears trying to utilise the whitelist option causes the same crash. At the moment the only workaround is to keep EnableNaturalSpawn
, and to add further biomes to the blacklist.
@Created-Creation Can you try to keep the default eyesinthedarkness.cfg
configs, and instead edit \modpacks\hexxit-ii\config\incontrol\spawn.json
to have this block at the end? (notice the added comma on the previous block)
, {
"mod": "eyesinthedarkness",
"result": "deny"
}
Let me know how it goes.
Might just be easier to remove the mod in this case.
Oh, right. That's true.
Tried adding it to spawn.json and hexxit won't start from the launcher. I tried disabling the mod as well but it didn't work, and I'm worried about how removing the mod will affect multiplayer.
I can handle Eyes for now though. Thanks for the help so far!
Tried adding it to spawn.json and hexxit won't start from the launcher
Did you add a comma after the previous block? Can you share a screenshot of how the config file looked like?
That might be a bit tricky, but yeah, I looked at how all the other blocks were formatted and did the exact same thing, triple-checked it and all.
Can you share your latest.log
from when it did not launch?
I don't remember the exact time so it'll take a bit.
I'm going to reattempt it and get the log from there. Will doing this affect multiplayer?
Turns out I hadn't hit the set to default but instead a different button, my b, was tired. It's working properly now with the code block in, though the tab indent was deleted because the other code blocks didn't have those. Idk if it's the tab removal or the setting to default, but one or both seems to have done the trick. Thanks so much for all the help!
Glad we figured out a workaround! Indents shouldn't affect the config, only brackets and commas. And as it's a config file rather than a mod change, it usually won't affect multiplayer.
Closing this as wontfix
as the Eyes in the Darkness mod is no longer in active development.
Was this bug reported before?
Please provide a link to your crash report or latest.log, if relevant
Link always fails upon clicking the Get Link button.
If you have any, please provide a list of additional mods
No additional mods installed.
Please describe the issue you are experiencing
Whenever I get within rendering distance of a Mushroom Island biome, the game crashes, and whenever I try to rejoin it crashes immediately. I cannot get within rendering distance at all. The mod cited to cause the crash is "Unknown" and clicking the Get Link button always just fails. Most recent crash file is titled "crash-2024-05-14_19.29.33-client.txt" though this issue has been going on for at least a couple weeks. I literally cannot find any other information about this.
In case of relevancy: