Evidence-backed Minecraft help

Litematica Not Showing Blocks with Sodium: Safe Conflict Test

Confirm the placement and render-layer settings first. If those are correct, update Sodium, Litematica and MaLiLib to mutually compatible builds, then reproduce the issue in a temporary profile without optional rendering mods.

Researched and technically reviewed by BlockArtLab · Updated September 6, 2026

What should you do first?

Preserve the original file and test with a copy. Do not start by deleting a world, changing random NBT values or renaming file extensions. This guide begins with reversible checks because several different failures can produce a similar symptom.

How do you fix it step by step?

  1. Verify that another schematic is visible with Render Layers set to All.
  2. Record the exact Minecraft, loader, Sodium, Litematica and MaLiLib versions.
  3. Create a temporary profile with only Litematica and required dependencies.
  4. If rendering returns, add optional mods back in small groups to identify the conflict.
  5. Search or report the exact version combination upstream rather than deleting the world or schematic.

What should you verify before trying again?

  • Placement exists
  • Rendering enabled
  • Exact versions recorded
  • Clean-profile test completed

Change one variable at a time and record the exact Minecraft version, mod loader and mod versions. If a clean profile works, the original schematic is probably not the first thing to replace; add optional mods back gradually until the conflicting combination is clear.

Does this work in Java and Bedrock Edition?

This diagnosis changes client mods only; make a separate profile and do not modify an important world as a first troubleshooting step.

What evidence supports this solution?

The first source below documents real player demand. Project documentation or an upstream tracker is included to confirm the relevant feature and avoid presenting one community reply as universal fact.

  • Player rendering report: The community recommendation was to check current Sodium, Litematica and MaLiLib versions and test without Sodium.
  • Litematica upstream issues: Current compatibility reports and reproducible rendering bugs should be checked against the upstream tracker.

Need a fresh build-ready file?

Convert an image into a block preview, gridded PNG, CSV material list and Java Litematic. Check the small preview before committing resources to a large build.

Open the free Minecraft image converter

Frequently asked questions

What is the short answer for “litematica not showing blocks with sodium”?

Confirm the placement and render-layer settings first. If those are correct, update Sodium, Litematica and MaLiLib to mutually compatible builds, then reproduce the issue in a temporary profile without optional rendering mods.

Should I test this in my main Minecraft world?

No. Keep the original file and reproduce the problem in a separate creative world or temporary game profile first. That preserves the source and makes mod conflicts easier to isolate.

What can Bedrock or console players use instead of Litematic?

This diagnosis changes client mods only; make a separate profile and do not modify an important world as a first troubleshooting step.

Related BlockArtLab guides