Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-229481

Datapacks not working at all in 1.17

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Invalid
    • None
    • 1.17
    • None
    • Unconfirmed
    • (Unassigned)

      So I have a datapack Ive been working on for the past few months (1.16), and I actually recently ran into an issue where chiseled_stone_bricks and stone_brick_walls just dont work? However, I was told this issue is "outdated" and to update to 1.17. So I did, because maybe the issue got fixed...

      Nope.

      Datapacks do not work at all.

      It says "Data pack validation failed" every single time.

      The datapack is linked below. And by the way I have posted this before but I stopped receiving responses.

      I was told (quote):

      "

      • You can only use lowercase characters, but you are using uppercase
      • You have some files in your datapack that are empty (for example acacia_slab.json). Delete all of them
      • You are using minecraft:air in some recipes, which does not exist. You need to specify the output item or use "result": {} if it should be empty.
      • As well as other errors

      "

      But in response:

      Im aware I have empty files; that is intentional and I do not plan to delete them. Im trying to overwrite and remove the recipes with blank files. It worked fine until the 1.17 update. Did something change? If so, how would I do this differently in 1.17?

      And what do he mean by lowercase? Like did he mean the main folders? What needs to be lowercase and isnt?

      And what recipes use air? I dont remember ever using minecraft:air in any of the recipes. Even if I did, wouldn't the recipe just not work? Why would it make the entire pack not work??

      The datapack also gives me this error:

      https://paste.ubuntu.com/p/whPwZ3NYSp/

       

            Unassigned Unassigned
            aceplante aceplante
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: