I'm trying to make a system that allows you to define loot tables for blocks. To do this, I'm using the method shown in the forge docs, but it doesnt seem to work for me. The list that stores the resulting itemstacks never gets populated, and the block drops nothing. 

 

Here's the event handler I'm using:

 

https://pastebin.com/1Q5JSC7H

 

And heres the table, which is located at src/main/resources/assets/foragecraft/loot_tables/dirt.json:

 

https://pastebin.com/tZQhZfHn

 

 

And your debugging messages..?

 

 

[19:30:41] [Server thread/INFO] [STDOUT]: [com.theishiopian.foragecraft.handler.BlockForageHandler:blockBreak:31]: net.minecraft.world.storage.loot.LootTable@58554c7e
[19:30:41] [Server thread/INFO] [STDOUT]: [com.theishiopian.foragecraft.handler.BlockForageHandler:blockBreak:44]: []

list = loottable.generateLootForPools(world.rand, context.build());

 

That is returning a zero-sized list.

Yes, I know that. What I want to know is why.

You're going to have to examine that method.

I assume you mean generateLootForPools? 

I apologize if I'm missing something terribly obvious, I've never used loot tables before.

5 minutes ago, theishiopian said:

I assume you mean generateLootForPools? 

There are no other methods on that line, so yes.

I've looked at that method before, and I can't see the problem. Since vanilla uses it all the time, I know it works. 

So you need to follow the execution of the vanilla code when you pass it in your data and figure out why it is not returning what you expect.

I've followed this rabbit hole for days, I can't find anything. I've narrowed the problem down to the resource location, or possibly the loot context, but I can't find anything wrong with either, based on similar usages of the code in other projects.