Block drops using Vanilla loot tables?

[labmonjos]

Hi,

I have a question on how the loot table function for blocks is supposed to work. I have created the following server script for a new ore I want to add. using pool.addItem works, but I wanted to use the Vanilla style loot table and I thought pool.addEntry:

startup script:

StartupEvents.registry('block', event => {
  event.create('modmonjo:lead_ore')
    .material('stone')
    .hardness(3)
    .displayName('Lead Ore')
    .tagBlock('minecraft:mineable/pickaxe')
    .tagBlock('minecraft:needs_stone_tool')
    .requiresTool(true)
})

server script:

ServerEvents.blockLootTables(event => {
  event.addBlock('modmonjo:lead_ore', table => {
    table.addPool(pool => {
      pool.addEntry('modmonjo:lead_ore') //What i want but not working
      //pool.addItem('modmonjo:raw_lead', 100, [4, 8]) //old but working
	})
  })
})

Looking at the Wiki (https://wiki.latvian.dev/books/kubejs-legacy/page/loot-table-modification) (outdated because of kubejs 6) is pool.addEntry what I think it does? How can i achieve using this style of loot table? Or is there a way to convert my datapack style loot table to a kubejs one?

KubeJS Forge 1902.6.0-build.142 (1.19.2)

Thanks,

[labmonjos]

wow that code did not paste the way i wanted it to (im very new)

Heres a pastebin
https://pastebin.pl/view/623289d8

[ChiefArug]

What is the loot table you are trying to recreate? And is there any reason you want to do it via JS (cause KJS supports loading data like loot tables via the data folder)?

[labmonjos]

I would like to use the one from the data folder but apon reloading, but I get the following error with the config in the orignal post:

I created a loot table in kubejs/data/modmonjo/loot_tables/lead_ore.json:
(this is just a rip from minecraft's regular ores loot table lol)

{
  "type": "minecraft:block",
  "pools": [
    {
      "bonus_rolls": 0.0,
      "entries": [
        {
          "type": "minecraft:alternatives",
          "children": [
            {
              "type": "minecraft:item",
              "conditions": [
                {
                  "condition": "minecraft:match_tool",
                  "predicate": {
                    "enchantments": [
                      {
                        "enchantment": "minecraft:silk_touch",
                        "levels": {
                          "min": 1
                        }
                      }
                    ]
                  }
                }
              ],
              "name": "modmonjo:lead_ore"
            },
            {
              "type": "minecraft:item",
              "functions": [
                {
                  "enchantment": "minecraft:fortune",
                  "formula": "minecraft:ore_drops",
                  "function": "minecraft:apply_bonus"
                },
                {
                  "function": "minecraft:explosion_decay"
                }
              ],
              "name": "modmonjo:raw_lead"
            }
          ]
        }
      ],
      "rolls": 1.0
    }
  ]
}

[labmonjos]

After a lil digging in the source I think I found it? I found this: addLootTable. So i used that instead of addEntry and it appears to be using my loot table:

ServerEvents.blockLootTables(event => {
  event.addBlock('modmonjo:lead_ore', table => {
    table.addPool(pool => {
      pool.addLootTable('modmonjo:lead_ore')
    })
  })
})

Would this be the correct way to map to a loot table in the data folder?

[ChiefArug]

Move the loot table to kubejs/data/modmonjo/loot_tables/blocks/lead_ore.json.
That should remove the need for the script, as this is where MC looks for the blocks loot table in the first place.

In theory it is possible to not use the json and make the entire loot table in script, but KubeJS' loot table format is difficult to work with and not very well documented.

[labmonjos]

LOL! my bad! You are right! Moving the loot table to the loot_tables/blocks folder works without a script in /server_scripts/. I should have looked at the folder structure a little more carefully. Thank you for helping me with this!!! Marking as solved!