Game fails to initiate after launching via Modrinth

[void bison]

So everything seems to launch fine (after a couple restarts and repairing game files), but once I get to the point of selecting Single-Player Game, it gives me the Loading World screen, and then after a few seconds, that text disappears and just stays on this blank Dirt texture screen endlessly. If I click on it, then it freezes properly, and asks me to Close Program or Wait for Program to Respond.

Ultimately I just have to force-quit it and try again (now multiple times in a row to no success).

Here are the logs, but I don't think I saw any error messages..
https://mclo.gs/0E5amD3

[gaunt laurel]

Modrinth

👋 Hello! Thank you for creating a new thread on Modrinth server

📃 Something went wrong with the game? Make sure to provide logs using mclo.gs
❔ If you're having an issue with Modrinth product, use our dedicated support portal instead

🔔 Don't forget to mark your thread as solved if issue has been resolved by using </solved:1460815060854243411>

[void bison]

bump

[void bison]

bumping again because I still cannot seem to fix the problem;
the latest attempt had the game sitting for over an hour on the screen in the picture above.

[wide berry]

Hey, just a heads up — you have two versions of Ars Nouveau in your mods folder at the same time:

• ars_nouveau-1.20.1-4.12.7-all.jar
• ars_nouveau-1.20.1-4.9.0-all.jar

Having duplicate mods can cause crashes. Try deleting the older one 4.9.0 and keeping 4.12.7 — might fix your issue! If it still doesn't work, send your logs again and i'll take another look.

[void bison]

I think there was a reason I had the older version in with the newer one.. but I don’t remember why anymore!
I’ll try to remove it when I get home from work today and see how that goes.

I’ll also try to get the latest log, but because it’s never “truly crashing” (I have to either Alt-F4, or use the Windows “close or wait for the program to respond” box), I don’t know if a true crash log is generated.

[wide berry]

No worries — latest.log is exactly what we need here. It gets written continuously during the session, so even without a proper crash it should contain everything up until the freeze. Just reproduce the issue (let it hang for a bit, then force-quit), and then grab the latest.log right after. That should tell us where it got stuck!

[void bison]

🫡

[wide berry]

Actually, I took another look at the log you already sent and think I found the likely culprit!

When you load a singleplayer world, Minecraft starts an internal server thread in the background — and that thread seems to be crashing immediately because your curios-server.toml config file is empty or corrupted:

Failed loading config file curios-server.toml of type SERVER for modid curios
Caused by: ParsingException: Not enough data available

The client then keeps running (hence the frozen dirt screen) while the server thread is already dead.

Worth trying: Delete this file:
...\Solo Instance (1)\config\curios-server.toml

Forge should regenerate it with default values on the next launch. Can't guarantee this is the only issue, but it's the most obvious error in the log around the time the world starts loading!

Here is your crash report: D:\ModrinthApp\profiles\Solo Instance (1)\crash-reports\crash-2026-05-03_14.14.12-server.txt

[void bison]

Oooooh.. interesting. And also confusing as I was playing the game quite literally just two days prior without any issues, so I’m not sure why it would suddenly just… crap itself like this?

I’ll look at that when I get home then! Thank you!

[gaunt laurel]

-# Command suggestion: </solved:1460815060854243411>

[void bison]

okay I'm at home looking at the Config folder, and this [...\Solo Instance (1)\config\curios-server.toml] doesn't exist! I have 'curios-client' and 'curios-common', but not -server.toml

I'm gonna try downgrading the Curios API mod to the previous version to see if that helps it regenerate this bonked up file (that also seems to just be missing)

[void bison]

okay that didn't help, and now modrinth itself keeps freezing and crashing :D

WHAT IS GOING ON

anyway here is the latest latest.log
https://mclo.gs/pxPuZp3

[wide berry]

Good news — the crash is confirmed, and I can see exactly why you couldn't find the file!

SERVER-type config files aren't stored in the global config folder, they're stored inside the world's save folder. Look here instead:

...\Solo Instance (1)\saves\[your world name]\serverconfig\curios-server.toml

That file is empty or corrupted, which causes the internal server thread to crash immediately when you try to load the world — leaving you stuck on the dirt screen.

Delete it and Forge will regenerate it on the next launch. There's also a crash report if you want to take a look:

...\Solo Instance (1)\crash-reports\crash-2026-05-06_21.46.37-server.txt

[void bison]

Ooh alright, I’ll give that a shot now!

File located and deleted; attempting to launch now

No luck.. right back to Dirt Limbo 😞

https://mclo.gs/aADwuXE

[void bison]

I opened that crash log you referenced last night, and I see there's a lot of mods in the Data Packs: line that say (incompatible)..
should I try downgrading them to attempt restoring compatibility?

[crude spear]

Try removing the server config file for JEI (jei-server.toml), and you shouldn't worry about the datapacks that say "(incompatible)", as the most likely reason for that is just that a mod author forgot to change the internal format version, which is used to check if a datapack or resource pack is compatible with the current version

[wide berry]

Just to add to that — it might be worth deleting the entire contents of the serverconfig folder rather than just jei-server.toml. The log shows that curios-server.toml was also broken (it got auto-corrected this time, but it crashed last time), so there's a good chance more files in there are empty or corrupted. Clearing the whole folder lets Forge regenerate everything cleanly at once.

Path: ...\saves\New World\serverconfig\

[void bison]

😱😵‍💫
Mmmmkay guess I’ll give that a shot now

Also because I haven’t said it yet,

THANK YOU for helping me this far; I sincerely appreciate it so much!

[gaunt laurel]

-# Command suggestion: </solved:1460815060854243411>

[void bison]

Attempting to start now~

[void bison]

https://tenor.com/view/head-smash-frustrated-smashing-head-banging-head-angry-gif-5036079142072797219

[wide berry]

any new logs? or did the game start?

[void bison]

Sorry, had a busy afternoon; there were some new logs, but I never got the game to start..

[gaunt laurel]

-# ⚠️ Last message in this thread was sent <t:1778206190:R>. It will be automatically archived soon.

[void bison]

Okay perfect timing to finally get back to figuring this stupidity out because the bot just warned me it'll archive this soon otherwise.

https://mclo.gs/CCHl4H8 I think this was the last crash log I had gotten (from 5/7/26, had a pretty busy week, then out of town for a wedding)

[void bison]

I know I'd done some mod updates, but I just checked through all of them, and none had a compatible update around the time I started having the launch problems, so I don't think that's what the cause is.. or, I hope not at least.. D:

Aaaaand Modrinth is back to just randomly crashing as I inspect things. Wonderful.

[full palm]

this whole log is just errors, can you provide a crash log with a mod list?

[void bison]

Ooh uhh.. yeah lemme try running it again, since I set it down for a while

[void bison]

I thought that just isolating the errors would be helpful by making it easier to see the problems, sorry :x

[void bison]

Here's the full log now: https://mclo.gs/NYQ7zAL

[crude spear]

Remove the glyph touch config file for Ars Nouveau (ars_nouveau/glyph_touch.toml)

[void bison]

…if it’s just as simple as that, I’m gonna scream.

I’ll try that when I get home from the gym

[crude spear]

But if it doesn't work, you could try removing all of the config files for Ars Nouveau (so the whole ars_nouveau folder)

[void bison]

Home finally and trying to launch now with the touch.toml file deleted

same issue with the glyph_touch.toml file gone; trying again with ars_nouveau config deleted

this is seriously pissing me the hell off, nothing seems to be fixing this, and I really don't want to give up on the world in there

(log with no glyph_touch.toml): https://mclo.gs/ty0tjci

WAIT HOLY CRAP I THINK IT'S WORKING NOW

https://tenor.com/view/sherlock-sherlock-holmes-benedict-cumberbatch-john-watson-martin-freeman-gif-25334595

aaaaand the pair of them crashed, Modrinth and the launched instance. god dammit.

WE DID IT.

no fuckin' clue what went so critically wrong with Ars Nouveau's files, but I'm glad it finally got its head out of its ass.

[gaunt laurel]

-# Command suggestion: </solved:1460815060854243411>

[crude spear]

Do /solved

[void bison]

Thank you all so much for taking the time to me with this, i really appreciate it!

[gaunt laurel]

-# Command suggestion: </solved:1460815060854243411>