Default Dark Mode

Default Dark Mode

4M Downloads

[Resource Pack Error] Resource reload failed (25w19a and higher)

Closed this issue ยท 2 comments

commented

This is shocking but when I attempted to load Default Dark Mode in 25w17a or higher I was met with this unfortunate message below.
Image

from: 25w17a
25w17a

from: 25w19a
25w19a

Hey @nebuIr I'm begging you to update the Resource Pack asap! that type of issue shouldn't be happening.

and please bump resource pack format to 63 (1.21.6-pre1)

Error Message

[21:21:38] [Render thread/INFO]: Reloading ResourceManager: vanilla, file/Default-Dark-Mode-Expansion-1.19.0+-2025.5.1-beta.zip, file/Default-Dark-Mode-1.20.2+-2024.6.0.zip
[21:21:38] [Worker-Main-5/INFO]: Found unifont_all_no_pua-16.0.03.hex, loading
[21:21:38] [Worker-Main-6/INFO]: Found unifont_pua-16.0.03.hex, loading
[21:21:38] [Worker-Main-5/INFO]: Found unifont_jp_patch-16.0.03.hex, loading
[21:21:39] [Render thread/ERROR]: Couldn't compile fragment shader (minecraft:core/rendertype_text_intensity): ERROR: 0:8: 'FogStart' : redefinition 
ERROR: 1 compilation errors.  No code generated.
[21:21:39] [Render thread/ERROR]: Couldn't compile pipeline minecraft:pipeline/text_intensity: fragment shader minecraft:core/rendertype_text_intensity was invalid
[21:21:39] [Render thread/ERROR]: Couldn't compile fragment shader (minecraft:core/rendertype_text): ERROR: 0:8: 'FogStart' : redefinition 
ERROR: 1 compilation errors.  No code generated.
[21:21:39] [Render thread/ERROR]: Couldn't compile pipeline minecraft:pipeline/text_polygon_offset: fragment shader minecraft:core/rendertype_text was invalid
[21:21:39] [Render thread/ERROR]: Couldn't compile pipeline minecraft:pipeline/text: fragment shader minecraft:core/rendertype_text was invalid
[21:21:39] [Render thread/INFO]: Caught error loading resourcepacks, removing all selected resourcepacks
commented

Created a pull request, fixing this issue for 25w19a+ versions (some things changed since 25w17a). Hopefully Mojang won't change anything else

commented

It's been fixed, thank you NebuIr and Vi-Tul!