We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WhenDungeonsArise--Forge/src/main/resources/data/dungeons_arise/loot_tables/chests/mines_treasure_big.json
Line 73 in 159b590
I'm getting these two errors on my server and think this line, and similar lines, are the cause:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
WhenDungeonsArise--Forge/src/main/resources/data/dungeons_arise/loot_tables/chests/mines_treasure_big.json
Line 73 in 159b590
I'm getting these two errors on my server and think this line, and similar lines, are the cause:
[19Sep2024 22:58:41.001] [Worker-Main-3/ERROR] [net.minecraft.world.level.storage.loot.LootDataType/]: Couldn't parse element ResourceKey[minecraft:root / minecraft:loot_table]:dungeons_arise:chests/mines_treasure_big - Failed to parse either. First: Unknown registry key in ResourceKey[minecraft:root / minecraft:loot_function_type]: minecraft:set_nbt; Second: Not a json array: {"function":"minecraft:set_nbt","tag":"{Enchantments:[{id:\"minecraft:sharpness\",lvl:6s},{id:\"minecraft:looting\",lvl:3s}]}"} -- 264 | [19Sep2024 22:58:41.020] [Worker-Main-3/ERROR] [net.minecraft.world.level.storage.loot.LootDataType/]: Couldn't parse element ResourceKey[minecraft:root / minecraft:loot_table]:dungeons_arise:chests/mines_treasure_medium - Failed to parse either. First: Unknown registry key in ResourceKey[minecraft:root / minecraft:loot_function_type]: minecraft:set_nbt; Second: Not a json array: {"function":"minecraft:set_nbt","tag":"{Enchantments:[{id:\"minecraft:sharpness\",lvl:6s},{id:\"minecraft:looting\",lvl:3s}]}"}The text was updated successfully, but these errors were encountered: