✅ | I installed drippy and it gives me this

[steady maple]

It says this everytime I try to play and I removed all incopatable mods yet it still did not work

[open sigil]

I’m checking what this Drippy startup crash usually means and what info will help narrow it down. 🛠️

I’m narrowing it down, but I still need the exact error text from the log to be sure. If you can grab latest.log, that’ll make this much faster 🙏

I found the crash text , it’s failing right when Drippy starts up, so I’m checking the exact dependency/setup notes now. 🔎

[open sigil]

Ahh gotcha , that looks like Drippy is crashing during startup, so this is usually a version/dependency problem rather than just “one bad mod” 😕🛠️

Can you send me your full latest.log from the logs folder?
That’s the most useful file for this kind of crash , the crash report alone usually isn’t enough.

Also please check these real quick:

• Minecraft version matches the Drippy build you installed
• FancyMenu is installed too
• Konkrete and Melody are installed in the correct versions
• For testing, try launching with only:
  • Drippy
  • FancyMenu
  • Konkrete
  • Melody
  • your mod loader

And even if you removed “incompatible mods,” double-check for the common FancyMenu/Drippy troublemakers like:

• Remove Reloading Screen
• Custom Loading Screen
• Animated Mojang Logo
• OptiFine

If you want, drop the latest.log here and I’ll help you read through it with you 🙂

[open sigil]

Log File Detected

The file message.txt is a Minecraft log file.

Minecraft Version

1.21.11

Mod Loader

Fabric 0.18.4

Loaded Mods

89

Log Statistics

0 error(s), 3 warning(s)

Java Version

21

Optimization Mods

Sodium, Sodium Extra

Essential Mod

Detected

Keksuccino's Mods

FancyMenu v3.9.0
Drippy Loading Screen v3.1.1
Konkrete v1.9.18
Melody v1.0.15

I spotted an attached text file too, so I’m checking if it has the exact crash message. 📄🔍

[open sigil]

Thanks for sending the log snippet 🙏

From the part I can see, your setup looks basically fine for Drippy:

• drippyloadingscreen 3.1.1
• fancymenu 3.9.0
• konkrete 1.9.18
• melody 1.0.15

So there’s no obvious Drippy setup problem in this excerpt.
The warning about Sodium Extra wanting Reese's Sodium Options is just a warning and not the Drippy crash.

What I’m missing is the actual error line / stack trace , this file ends before the crash happens.
Could you send the full latest.log from your Minecraft logs folder? That’s the one that usually shows exactly why Drippy is failing 😅

If you want, I can help you read it once you upload it.

[open sigil]

Log File Detected

The file message.txt is a Minecraft log file.

Minecraft Version

1.21.11

Mod Loader

Fabric 0.18.4

Loaded Mods

89

Log Statistics

0 error(s), 41 warning(s), 15 exception(s)

Java Version

21

Optimization Mods

Sodium, Sodium Extra

Essential Mod

Detected

Keksuccino's Mods

FancyMenu v3.9.0
Drippy Loading Screen v3.1.1
Konkrete v1.9.18
Melody v1.0.15

I got another attached log snippet, so I’m checking whether it contains the real crash line this time. 🧾🔎

Aha, I found one big clue in the log: OptiFine is still installed. I’m checking whether Drippy/FancyMenu already call that out as a known problem before I reply. ⚠️

[open sigil]

Aha, I found the likely culprit 👀

Your log still shows OptiFine is installed:

• OptiFine_1.21.11_HD_U_J9.jar at line 98

And that’s a known incompatibility with Drippy/FancyMenu. There are even GitHub issues about OptiFine causing Drippy startup crashes.

Also, the log shows Drippy itself actually starts loading fine later on:

• Drippy
• FancyMenu
• Konkrete
• Melody

So this doesn’t look like Drippy “not installing” , it looks like another mod is breaking it, and OptiFine is the big one still present.

What I’d do next:

• Delete OptiFine completely from your mods folder
• Launch again with only:
  • Drippy
  • FancyMenu
  • Konkrete
  • Melody
  • Fabric Loader
• If it still fails, try removing Voxy too for a test, because it’s throwing a bunch of missing Iris/Flashback/Nvidium warnings in your log

The Sodium Extra / Reese’s Sodium Options warning is not the Drippy problem.

If you want, send me the next latest.log after removing OptiFine and I’ll check it again with you 🙂

[open sigil]

Log File Detected

The file message.txt is a Minecraft log file.

Minecraft Version

1.21.11

Mod Loader

Fabric 0.18.4

Loaded Mods

77

Log Statistics

0 error(s), 15 warning(s), 3 exception(s)

Java Version

21

Optimization Mods

Sodium, Sodium Extra

Essential Mod

Detected

Keksuccino's Mods

FancyMenu v3.9.0
Drippy Loading Screen v3.1.1
Konkrete v1.9.18
Melody v1.0.15

I got another attached file, so I’m checking if it has the updated log after removing OptiFine. 🧩

[open sigil]

Nice, this updated log is a lot clearer 👍

Good news: OptiFine is gone now, and Drippy, FancyMenu, Konkrete, and Melody all load successfully in this log.

What I’m seeing is this:

• Drippy is not crashing here
• The only visible issue is:
  • Failed to get system info for Render Extensions
  • IllegalStateException: Can't getDevice() before it was initialized

That looks like a graphics/render initialization warning, not a Drippy error. So at this point, the problem is probably not Drippy itself.

What I’d try next:

• test with Drippy + FancyMenu + Konkrete + Melody only
• temporarily remove other rendering-related mods like:
  • Voxy
  • Sodium Extra
  • anything Iris/renderer related if you have it
• update your GPU drivers if possible

If it still doesn’t start, please send the full latest.log from the logs folder, because this snippet still doesn’t show an actual crash stack trace.

If you want, I can also help you make a super clean “Drippy only” mod list to test with 🙂