Dye Recipe Unifier: Automatically Unify Dyes in Minecraft

Dye Recipe Unifier: Streamlining Minecraft Dye Crafting If you have ever spent time in a modded Minecraft world, you know the frustration of scrolling through ten different recipes for the same color of dye. One mod adds pink dye from peonies, another from beetroot, a third from some exotic flowe...

Download DyeUnifier for Minecraft 1.20.1, 1.19.2, 1.18.2, 1.16.5

Original name: DyeUnifier

Minecraft: 1.16.5, 1.18.2, 1.19.2, 1.20.1

FileVersionLoaderSize
DyeUnifier-1.16-1.0.zip1.16.5—17 КБDownload
DyeUnifier-1.18-2.0.zip1.18.2—19 КБDownload
DyeUnifier-1.19-3.0.zip1.19.2—19 КБDownload
DyeUnifier-1.20-4.0.zip1.20.1—20 КБDownload
DyeUnifier-1.20-4.1.zip1.20.1—27 КБDownload

Dye Recipe Unifier: Streamlining Minecraft Dye Crafting

If you have ever spent time in a modded Minecraft world, you know the frustration of scrolling through ten different recipes for the same color of dye. One mod adds pink dye from peonies, another from beetroot, a third from some exotic flower you have never seen before. Your inventory clogs up with incompatible items, and your crafting grid becomes a guessing game. The Dye Recipe Unifier steps in to solve exactly that headache, offering a clean, automated way to standardize dye recipes across your entire modpack.

The Dye Chaos in Vanilla and Modded Minecraft

Vanilla Minecraft already has a decent dye system, but mods love to add their own flowers, crops, and processing methods. Soon you end up with multiple ways to craft white dye—from bone meal, from white tulips, from lily of the valley, from modded marble dust. Each recipe creates a slightly different item tag or metadata, meaning they do not stack, do not work in recipes interchangeably, and fill your storage with clutter. This is where a unification datapack becomes essential.

The Dye Recipe Unifier does not just patch a few recipes; it automatically tags all dye outputs so that any dye-producing recipe in your pack outputs a single, unified item. You get one white dye, one red dye, one blue dye—no matter the source. This saves inventory slots, simplifies autocrafting setups, and keeps your modpack feeling cohesive.

How the Dye Recipe Unifier Works

At its core, the tool is a clever combination of a datapack and a KubeJS script. The datapack handles the heavy lifting of auto-tagging. It scans all items that act as dyes and assigns them a common tag, effectively telling the game “these are all the same thing.” Then the KubeJS script steps in to adjust or remove duplicate recipes that the datapack cannot touch, because datapacks alone cannot delete recipes—only override or add them. This two-pronged approach gives you complete control without needing to edit dozens of JSON files by hand.

The creator originally built this out of personal necessity, tired of constantly tweaking a custom dye fixer script every time they assembled a new modpack. Now, the Dye Recipe Unifier does the repetitive work automatically, so you can focus on building and exploring. You simply drop the datapack into your world or server folder, add the companion KubeJS script, and the unification happens silently in the background.

Installation and Setup

Getting started is straightforward, even if you are new to datapacks. First, download the main datapack file from the project page. Place it inside the datapacks folder of your Minecraft world save. Next, you need the KubeJS script file, which is provided separately for each version. Put that script in your kubejs/server_scripts folder. If you are using a custom launcher like the foxygame.net launcher, you can easily download and manage mods right from its menu, making the process even smoother—especially when you want to keep everything organized for multiple modpacks. Once both components are in place, reload your world or run the /reload command, and the unification kicks in.

If you do not already have KubeJS installed, you will need to add that mod to your mods folder. The script relies on KubeJS to handle recipe removal and advanced logic. Without it, the datapack can still tag items, but duplicate recipes might linger. For the full experience, always pair the two.

Customization with KubeJS Scripts

One of the biggest strengths of this system is how editable it is. The provided KubeJS script is an example file, not a locked black box. You can open it in any text editor and tweak which recipes get removed, add support for mods that are not yet covered, or adjust the priority of certain dye sources. The script uses JavaScript syntax that is beginner-friendly, and the project page includes comments to guide you.

Common customization scenarios include:

  • Excluding a specific mod’s dye recipe because you prefer its aesthetic.
  • Adding a new flower from a freshly installed mod so its dye gets unified.
  • Changing the output dye item to a particular mod’s version for consistency with your pack’s theme.

Because the KubeJS file is separate from the datapack, updating the datapack itself does not overwrite your custom script. You can safely replace the datapack when new mod support is added while keeping your personal recipe adjustments intact.

Community and Ongoing Support

The project is actively maintained, with the developer welcoming bug reports and suggestions for additional mod support. If you run into a dye from a lesser-known mod that refuses to unify, you can report it and often see a fix included in the next update. The Discord server provides a space to chat about this datapack and other projects, making it easy to get help or share your own script tweaks.

Modpack creators will appreciate how much time this saves during pack development. Instead of writing a custom CraftTweaker or KubeJS script from scratch for every pack, you drop in the Dye Recipe Unifier, do a quick pass to verify coverage, and move on to more interesting balance work. Players benefit from a cleaner inventory and less confusion at the crafting table.

Why Unification Matters for Your Modpack

Beyond mere convenience, dye unification improves performance and reduces world bloat. When dozens of nearly identical items exist, the game must track more unique identifiers, and storage systems like Refined Storage or Applied Energistics waste disk space on items that should be interchangeable. Unifying dyes also prevents recipe conflicts in machines that process dyes, such as botany pots, squeezers, or dye mixers. Your automation lines run smoother, and your resource management becomes predictable.

For players who enjoy building with colored blocks, having a single source for each dye means less time hunting for specific flowers and more time creating. You can dye wool, terracotta, concrete, glass, and candles without double-checking which red dye you have on hand. The Dye Recipe Unifier turns a scattered crafting system into a streamlined experience.

Final Thoughts

The Dye Recipe Unifier is one of those small quality-of-life tools that, once added, you will never want to play without. It respects the vanilla feel while solving a real problem introduced by mod diversity. The combination of an auto-tagging datapack and an editable KubeJS script gives you both power and flexibility. Whether you are building a massive kitchen-sink pack or a focused thematic adventure, this utility keeps your dye economy clean and your crafting grid sane. Grab the datapack and example script, drop them into your world, and enjoy a unified rainbow.