What this fixes

If you run Litematica alongside VulkanMod, you may have noticed schematics rendering blank, invisible, or with wrong/blue-tinted colors instead of showing the normal ghost-block overlay. To combat this you would usually have to disable VulkanMod, which fixes it immediately.

The actual cause

Litematica's schematic renderer uses custom render pipelines defined by malilib, pointing at shader files malilib bundles in its own jar. This is a completely normal use of Minecraft's own rendering API.

VulkanMod's shader-loading code however, only ever looks for shader files inside its own jar, and ignores which mod a shader actually belongs to when building the file path. So when it needs to compile one of malilib's custom pipelines, it looks in the wrong place, never finds the shader, and the pipeline fails to build correctly which is what causes the blank/miscolored rendering.

This isn't specific to Litematica or malilib. Any mod that registers a custom render pipeline with shaders bundled in its own jar will hit the same problem under VulkanMod.

What this mod does

A small client-side patch that steps in only when VulkanMod's own shader lookup comes up empty. In that case, it figures out which mod actually owns the shader and reads it from that mod's real jar instead. Nothing else about VulkanMod's rendering or performance is touched — this only affects the specific lookup that was failing.

Requirements Minecraft 1.21.11, Fabric VulkanMod malilib + Litematica (or any other mod hitting the same issue) Compatibility

This mod does nothing unless VulkanMod is installed, so it's safe to leave in your mods folder even if you switch renderers later.