Feature: Universal TXT/JSON/NBT Loottable support

[NLBlackEagle]

Is your feature request related to a problem? Please describe.

I wanted to import loottables into MC, however creating loottables often happens in JSON format rather then NBT. I have tried linking both JSON as TXT to a chest string of which neither worked e.g.:

B(-3,0,-4,CHEST:3,../NBT/VanillaLoot/jsonloot/underwater_ruin.txt) B(-3,0,-4,CHEST:3,../NBT/VanillaLoot/jsonloot/underwater_ruin.json)

Describe the solution you'd like

It would be nice to see that multiple methods are allowed. Preferably json/nbt and perhaps txt ( as this is also used in the entity string )

Describe alternatives you've considered

A possible workaround is manually editting an existing NBT file or to use the minecraft:loottable However if the loottable is different from the default minecraft loottable or non-existant in the game ( so custom ) one is forced to manually put the loottable in a NBT file.

Description aka Additional context

This feature request is one of lower priority and more of a luxury as workarounds are there but definitely worth putting in at some point.

[PG85]

Hey @NLBlackEagle , thanks for reporting this. Sounds like a good idea that would make working with BO3's/BO4's easier. Moving to backlog for now.

[PG85]

• To clarify: Entity() supports both .nbt and .txt, Block() supports only .nbt atm.