mojira.dev

Ryan Matthew

Assigned

No issues.

Reported

MC-197843 Condition match_location does not work with piglin bartering Confirmed

Comments

I've attached the datapack I used to demonstrate the issue. All of the interesting stuff is in data/minecraft/loot_tables/gameplay/piglin_bartering.json.

I made sure to add one item which should always have a chance of dropping (diamond), one which should in a warped forest (warped planks), and one which never have a chance of dropping in an unmodified nether (bamboo). This ensures that:

  1. The datapack is working and the loot table is being overridden, as none of those are normal drops

  2. The conditions are valid and not being ignored, as no bamboo is ever dropped

  3. The conditions do what they are supposed to with other means of using the loot table, as /loot works as expected

  4. The conditions are always negative when used for piglin bartering, as diamonds are the only item that ever drops

I created a small datapack to demonstrate the issue. I've attached three screenshots. One shows the source code for the barter loot table, one shows the result of bartering with piglins in a warped forest (where warped planks should drop 80% of the time in my example datapack), and one shows the result of using the /loot command in a warped forest, where you can see warped planks dropping.

If there's anything else I can provide, let me know!

(Edit) I just noticed in the screenshot with the /loot command the biome information is covered up by previous command results. It was in the same location as the bartering screenshot, a warped forest, and I can probably go back and provide any information which is covered up.

Isn't Slowness VI (amplifier 5) obtainable in vanilla survival with Strong Turtle Master? So would bugs with that be unsupported?

This also occurs when opening creative inventory on search tab, typing the character "e" (or whatever it's binded to). My temporary solution is just binding chat/command to page down and page up buttons so nothing is typed.

Happens with / for comments too (am using Ubuntu 20.04, has happened in all versions I've played)