In the /loot command the <tool> argument (for the mine/fish options) is ambiguous with mainhand and offhand input.
/effect was split up to /effect give and /effect clear for exactly this reason.
Current synaxt:
/loot <...> mine <x> <y> <z> <tool>|mainhand|offhand
/loot <...> fish <loot table> <x> <y> <z> <tool>|mainhand|offhandExpected synaxt:
/loot <...> mine <x> <y> <z> mainhand|offhand
/loot <...> mine <x> <y> <z> tool <tool>
/loot <...> fish <loot table> <x> <y> <z> mainhand|offhand
/loot <...> fish <loot table> <x> <y> <z> tool <tool>Comments 4
Hey! Thanks for the report! But could you present your logic in a bit more detail? We did not fully understand what exactly and why you want to change.
I think what they mean is that being able to specify any of <tool>|mainhand|offhand at the same position in the command might be confusing, since someone might look at mainhand or offhand and think it’s an item with ID minecraft:mainhand or minecraft:offhand used as the value of the <tool> argument.
This is the same problem that /effect had before 1.13 when any of <effect>|clear could be specified as the first argument, which could result in clear being mistaken for a minecraft:clear effect being specified as the value of the <effect> argument. This was fixed by adding a give literal node right after effect that could be used to specify an effect to give instead.
The reporter is suggesting that a new literal node like tool be added to eliminate the ambiguity between the <tool> and the literal nodes mainhand and offhand.
Thank you for your report!
After consideration, the issue is being closed as Invalid.
You have posted a feature request or a suggestion. This site is for bug reports only.
For suggestions, please visit The official Minecraft feedback site or visit the Minecraft Feedback Discord server.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Still in 1.21.4.