So for the past hour I've been running the command "/loot give @p fish minecraft:gameplay/fishing 0 7 13 mainhand" while holding a fishing rod with a luck of the sea value of either 100, 40, or 3.
What I expected to happen:
While running the command I thought that eventually I'd get some form of treasure.
What actually happened:
I didn't.
Here's a video of the bug.
https://www.youtube.com/watch?v=YiyOjiJthVY
Attachments
Comments 5
I was thinking the reason that it didn't work is because of the changes to fishing not allowing you to get treasure unless you fulfill certain conditions. But even when the spot that you fish in does fulfill said conditions it doesn't give you treasure at all so that's not it.
Hi there!
I ran the same test in 1.15.2 and did receive treasure loot. Your speculation is likely correct.
I actually showed this to a friend and one of them pointed out that it probably broke because the loot table detects if the bobber is in open water. However, since this is a command running it and not an entity then the check fails and always gives you treasure. So you can fix this if you remove the condition from the loot table. So maybe this is less of a bug and more of a side effect. Still, it is kind of annoying so I hope that they do something about because otherwise I either have to remove that or add a system that chooses if the player gets fish or treasure loot.
Hi there!
Can confirm. I'm attaching a screen recording of my test (with command blocks). I've had to lower the quality of the video due to limitations with Jira, but you should see what's going on here.
EDIT: I tested it with the same command you used after recording this clip; same results.