#My modpack with Moonlight lib 1.20-1.2.16 VS Moonlight lib 1.20-1.2.18
61 messages · Page 1 of 1 (latest)
Moonlight sorry :p
My modpack with 1.20-1.2.16 VS 1.20-1.2.18
My modpack with Moonlight 1.20-1.2.16 VS 1.20-1.2.18
My modpack with Moonlight 1.20-1.2.16 VS Moonlight 1.20-1.2.18
My modpack with Moonlight lib 1.20-1.2.16 VS Moonlight lib 1.20-1.2.18
same issue happened to me, gonna downgrade the mod
trying to create a new world since my other world got corrupted, wonder if that's related, but yeah, game crashes and the only mod mentioned is Moonlight Lib
Here's my log too in case that helps
I am having the same problem - my log looks near identical
ok so small update, 1.2.18 also made my world corrupted
downgrading my version and the world loaded fine (thankfully), thought my world corrupted cuz of a different mod
ok its just the last update of moolight broken
Same here - "corrupted" world, error when creating new one. Rolled back moonlight to the last version, repeated the steps and my world thankfully was a-okay and I can once again create new worlds
@analog tree can you archive latest moonlight you published?
It seems to be broken
It's from a pr I merged which had some issues
Actually if you could fix that it would be awesome. Some files in this directory which were edited have missing brackets and commas
If you open them intellij will tell you where error is
A new pr might come today, would just then only need to publish a new verison
alright
I see you archived it.
I did the same with modrinth
MehVahdJukaar,
which mod is using these files from PR today? like beetroot_soup.json and others?
@late wasp
is this right?
there is 2 "food"
you can see the highlighted words in the picture
let me know what's the correct solution to that 2 "food". there are 2 more files with 2 "food".
👍
and I also have to update Moonlight lib to fix a problem in EveryComp (the recipe)
leavesType will need to have "sapling" as part of the child list
@late wasp ok. idk why the guy who updated these JSON. added that part. that part is what caused the crash because the mod wasn't loaded
Hm no that's correct
It supports items form any mod even if that mod isn't on
Therr was some missing brackets or comma somewhere
yeah i fixed that. and also missing comma.
let me run a test.
i think something similar to "isModLoaded" stuff need to be added in the JSON
because I removed that part (red rectangle) and I no longer have the "crash"
@late wasp ☝️
It must be invalid some other way because having a mod there is totally valid and done in many other jsons
Send me the crash
hold on
There you go: latest.log
i've restored the red rectangle code. the log should give you the whole story.
@late wasp ☝️ let me know if you know a good solution to fix the problem. I have no idea. but i know the code via red rectangle is responisble for the crashing.
That complains about powder snow
I see others aswell
Tbh idk log doesn't say but if you look at other old jsons they do use modded stuff
Pr has been made
Also I'll be back soon ish
k. PR is for Supplementaries. and is also for fixing the missing commas in JSON just like Moonlight Lib. So i'll leave it to you
Yeah that's no issue since no update was published
Can you push that new update if it works?
hmm. alright, i'll have to pull Supplemenatirs and test it.
You just need to run the mod alone. If it runs then it worms
yea. that's why i had to remove the code just like that red rectangle
Works