[1.14.4] Trying to implement modded block loot tables, but now no items are dropping?

[Izzymandias]

Hi there,

 

I'm currently implementing loot tables to some of my modded items, when I noticed that, even in survival, no items are dropping, not even vanilla ones. For example, I tried on several different worlds to break grass or trees, but no items were dropped; I started test worlds in both creative and survival and nothing changed. This appears to only be happening in my mod dev client (I checked through a Minecraft launcher running forge and no other mods and blocks dropped normally) so I'm presuming its an issue related to my Mod.

 

Any advice would be appreciated - I don't know what code would be revelant to add here so if you need to see some please just ask, thank you!

 

Edit; I did some continued testing, and this issue appears to have occurred even before I tried to implement custom loot tables. I've still got no idea what's causing it though...

 

Edit 2; It also affects recipes - I was unable to make any recipes, vanilla or otherwise. I did some searching on Google and tried to use /datapack disable (my mod name) but the command didn't appear to work - whenever I tried to re-enable it, it claimed that the Mod was already enabled, suggesting it was never properly disabled when the disable command was first used. Again, still no idea what's causing this.

Edited November 16, 2019 by Izzymandias
More testing performed, refined problem

[Draco18s]

One of your data files is bad and it caused everything to be discarded. 

[Izzymandias]

Okay, that sucks - would you suggest a clean re-install of Forge & Gradle then? Or is there any way to check what part isn't working?

[Draco18s]

It is one of YOUR data files that is causing problems. It should be mentioned in the log. But if you can't find it,  remove all of your assets inside /data and put them back in binary chunks (add half of the most recently removed if the problem isn't exhibited, remove half of what was most recently added if it does) and narrow it down. 

[Izzymandias]

Okay, Will do when I've got time

[Izzymandias]

Right, it is definitely something to do with the data I inputted, as removing the src/main/resources/data folder entire has allowed the game to function correctly again.

 

Here's the code for my custom loot table JSON;

{
  "type": "minecraft:block",
  "pools": [
    {
      "name": "aotmm:pool_blue_mushroom",
      "rolls": 1,
      "entries": [
        {
          "type": "minecraft:item",
          "name": "aotmm:blue_mushroom"
        }
      ],
      "conditions": [
        {
          "condition": "minecraft:survives_explosion"
        }
      ]
    }
  ]
}

 

And my custom recipe JSON;

{
  "type": "minecraft:crafting_shaped",
  "pattern": [
    "###",
    "#x#",
    "###"
  ],
  "key": {
  	"x": {
  	  "tag": "minecraft:leather"
  	}
    "#": {
      "tag": "aotmm:blue_mushroom"
    }
  },
  "result": {
    "item": "aotmm:spore_leather"
  }
}

 

My source files also had this path, if this could have caused a problem;

/src/main/resources/data/AttackOfTheMushroomsMod/recipes/
&
/src/main/resources/data/AttackOfTheMushroomsMod/loot_tables/blocks/

 

It's possible the error comes from using my full mod name (AttackOfTheMushroomsMod) rather than my ModID (aotmm) as a subfolder within /data/? Otherwise, I'm not too sure what needs to be fixed

[Izzymandias]

Ah, I figured it out!

my /src/main/resources/data/[mod]/ path needed the ModID, not the Mod Name. Changing it from AttackOfTheMushroomsMod to aotmm (the ModID) worked - now drops, both vanilla and otherwise, are functioning. Cheers for your help!