#Modpack Crashing, without crashlog, not sure whats causing it to close itself... log just ends?

1 messages · Page 1 of 1 (latest)

terse plover
#

Could it be running out of memory if the log is just ending?

wet tulip
#

shouldn't be running out of memory? has 30gbs of ram

terse plover
#

Hmm

wet tulip
#

computer has 64gbs

#

the modpack originally needed 25gb and that was 1,600 mods

#

only added a hundred, figured another 5gbs wouldn't hurt.

terse plover
#

I can't help after you surpass atm10 levels of fuckery unfortunately

#

this is probably a multilayered issue lol

#

It confuses me how someone even fits that many mods in a pack and still lets it turn on

#

mixin hell

wet tulip
#

all the mods 10, is a lie.

#

its not all the mods. XD

terse plover
#

all the mods you'd want

wet tulip
#

i wanted all the mods, nooone had a modpack XD

#

well someone had one, it was just insanely not updated

#

ima check to see if its running out of ram... ups to 40gbs of ram

#

if ur wondering, minecraft limit was processor, so i got the best processor i could find, then the best amount of ram.

wet tulip
#

i hate sodium

wet tulip
#

@terse plover im now at 1,685 mods... and its giving crash logs now.

#

the issue was a color selector mod... on the first log...

#

removed all of sodium, and just used embeddium and embeddium++