Welcome, Datapack Creator! (A Simple Guide to Predicates)

If you've ever dived into the amazing world of Minecraft data packs, you've probably heard of **Predicates**. Think of a predicate as a super-smart checklist or a set of rules that the game can use to ask a "true or false" question. They are the secret ingredient behind some of the most advanced custom creations, from loot tables that only drop a rare sword when you're in a specific biome, to advancements that are only awarded if you defeat a monster in a very specific way. A predicate can check almost anything: Is the player on fire? Are they wearing a full set of diamond armor? Are they looking at a specific block? This is incredibly powerful, but it comes with a big challenge: writing the predicate code in its required **JSON format** is famously tricky. A single misplaced comma or bracket can cause the whole thing to fail, and the game often won't tell you what or where the error is. This can lead to hours of frustrating guesswork.

This tool is designed to be your personal debugging assistant, a friendly guide that speaks the language of predicates fluently. As you type or paste your code into the editor on the left, the analysis panel on the right will instantly come to life. First, it acts as a strict syntax checker, immediately catching common errors like missing commas that would break your code. But then it does something more magical: it translates your complex conditions into plain, human-readable English. You'll see exactly what your predicate is checking for, in a clear and simple summary. This instant feedback loop makes the process of writing and debugging predicates faster, easier, and much more fun. It's the ultimate tool for streamlining your data pack creation, saving you precious time and helping you build bigger and better things in Minecraft.

How to Use This Debugger

1. Write or Paste Your Predicate: In the "Predicate JSON" editor on the left, either write your predicate from scratch or paste in code from your data pack file. Your work is automatically saved in your browser, so you can come back to it later.
2. Read the Live Analysis: The "Analysis" panel on the right will instantly update as you type. It will tell you if your JSON code is valid and then break down each condition into a simple English explanation.
3. Check for Errors: If there's a syntax error in your JSON, a clear error message will appear, helping you find and fix the problem quickly.
4. Save and Share: If you've created a complex predicate you want to save or ask for help with, click the "Copy Share Link" button. This will generate a unique URL that you can send to others!

Tips for Writing Predicates

• JSON is Picky:** The most common errors are simple syntax mistakes. Every opening brace `{` needs a closing brace `}`, and every item in a list needs to be separated by a comma (but there's **no** comma after the *last* item!). This tool is your best friend for spotting these tiny but critical errors.
• Use the Wiki as Your Spellbook:** The official Minecraft Wiki has a complete and up-to-date list of every possible predicate condition and all their valid options. This tool is your debugger, but the wiki is your ultimate reference manual. When in doubt, check the wiki!
• Test, Test, Test In-Game:** Once your predicate is written and this tool says it's valid, the final test is always in Minecraft itself. A simple command like `/execute if predicate my_datapack:my_predicate run say Predicate is true` is a fantastic way to check if it's working exactly as you expect under real game conditions.
• Combine and Conquer with `any_of` or `all_of`:** For more complex logic, you can create a list of conditions and wrap them in an `any_of` block (which passes if *any one* of the conditions inside is true) or an `all_of` block (which passes only if *all* of them are true). This is how you can create incredibly detailed and specific checks.
• Don't Forget `inverted`!:** One of the most useful but simple conditions is `inverted`. You can wrap another condition inside it to check for the opposite. For example, if you want to check if a player is *not* in the plains biome, you would use an `inverted` condition that contains the check for being in the plains.