Mojira Archive
MCM-233

Loot Table naming issues

Windows_Minecraft - Release_834163
1.2.20 Beta

Summary:
Custom entities are having a hard time accepting custom named loot tables. This is a difficult issue to narrow down, but I'll try to describe some of the circumstances.

  • I found this issue while trying to make a mob whose loot table was defined in a component group, and would switch to a different component group with a different loot table when right clicked with shears.
  • I initially named the loot tables "chest_rusty" and "chest_shiny". These names did not work.
  • I then renamed them "sheep" and "llama". They worked properly under these names.
  • I then named them "llama" and "llamatoo" (also tried "llama2"). Only "llama" worked in this scenario.
  • I have a separate behavior pack where I did the same thing, but the names were "duck_red", "duck_blue" etc. These all worked properly.

I moved forward with this feature using the names "sheep" and "llama".

Impact:
The inconsistency of naming files working correctly makes it confusing for behavior pack editors to know if they are correctly formatting things.

Repro Steps:
1. Get the world "loottableissue.mcworld" from Quinn on Slack.
2. Open the world, spawn a llama, and kill it.
3. Spawn a llama, right click it with shears, then kill it.
4. Notice the drops you're getting.
5. Enter the Behavior File and Loot Table files, change the names to be consistent with the names provided above, and notice the variable results.

Observed Results:
Some naming conventions do not work.

Expected Results:
As you are defining a specific file path, all naming conventions should work.

Screenshots/Videos attached:
No

Cannot Reproduce

[Noxcrew] Joe Arsenault

2018-04-25, 10:16 PM

2018-05-29, 11:29 PM

2018-05-29, 11:29 PM

0

0

Future Release

-