Complementary Broken? Start Here
Complementary problems usually fall into a few buckets: loader conflicts, wrong folders, overly high presets, or outdated ZIPs.
Match the symptom on this checklist, then open the linked guide. Do not reinstall Minecraft first.
Quick checks for every issue
- Confirm you are on Java Edition with Iris or OptiFine loaded.
- Confirm the Complementary ZIP sits in shaderpacks.
- Disable other shader packs and heavy visual mods temporarily.
- Drop to Potato or Low and test a new world.
- Update GPU drivers when compile errors persist.
- Remove OptiFine from Iris instances and the reverse.
Symptom guides
Wrong or old ZIP
Pack name missing, compile fails after an update, or a modpack needs a pin.
Versions and archivesVersion and download recovery
Many “shader is broken” reports are simply a bad download, an extracted ZIP, or a mismatched archive. Redownload from the download page, keep the file zipped, and confirm the label against the versions page.
If the failure started right after an update, compare notes on the changelog and roll back one build while you test.
Still stuck
Re-read install steps and requirements. If you need site help about broken links or content errors, use the contact page.
Symptom map
Build a clean test profile
Create a fresh Fabric profile with Iris, Sodium, and one Complementary ZIP only. If that works, add mods back in batches. This isolates pack conflicts faster than guessing.
Still stuck after a clean profile? Confirm Java vs Bedrock on the Bedrock page, then redownload from the download page.
Common questions
Keep reading
-
All downloads
Fresh ZIPs and mirrors
-
Versions
Pick or roll back a build
-
Iris setup
Rebuild a clean loader path
-
Potato settings
Stabilize FPS quickly
-
Complementary guides
Setup, FPS, updates, and fixes