MC-95490Invalid Loot Table names containing periods (".") do not create error message
Relates to:
MC-91061: Probably caused by the fix
The bug
When you provide a LootTable name with a period the game is unable to find a loot table but does not print an error indicating this.
How to reproduce
- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid"} - Open the chest
→ The error is printed in the log: "Couldn't find resource table minecraft:invalid" - Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid2."} - Open the chest
→ No error message is printed
The reason
The following is based on a decompiled version of Minecraft 1.9 using MCP 9.24 beta.
The reason for this is that the method net.minecraft.world.storage.loot.LootTableManager.Loader.load(ResourceLocation) only prints the error message
Invalid loot table name '[LOOT_TABLE]' (can\'t contain periods)
as debug message and not as error message.
Linked Issues
Created Issue:
Invalid loottable names containing point does not create error message
Relates to:
MC-91061: Probably caused by the fixThe bug
When you provide a LootTable name with a point the game is unable to find a loottable but does not print an error indicating this.
How to reproduce
- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid"}- Open the chest
The error is printed in the log: "Couldn't find resource table minecraft:invalid"- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid2."}- Open the chest
No error message is printed
Invalidloottable names containing point doesnot create error messageInvalid LootTable names containing points do not create error message
Relates to:
MC-91061: Probably caused by the fixThe bug
When you provide a LootTable name with a point the game is unable to find a loot table but does not print an error indicating this.
How to reproduce
- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid"}- Open the chest
The error is printed in the log: "Couldn't find resource table minecraft:invalid"- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid2."}- Open the chest
No error message is printed
Invalid LootTable names containing pointsdo not create error messageInvalid LootTable names containing periods (".") do not create error message
Relates to:
MC-91061: Probably caused by the fixThe bug
When you provide a LootTable name with a p
ointthe game is unable to find a loot table but does not print an error indicating this.How to reproduce
- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid"}- Open the chest
The error is printed in the log: "Couldn't find resource table minecraft:invalid"- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid2."}- Open the chest
No error message is printedRelates to:
MC-91061: Probably caused by the fixThe bug
When you provide a LootTable name with a period the game is unable to find a loot table but does not print an error indicating this.
How to reproduce
- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid"}- Open the chest
The error is printed in the log: "Couldn't find resource table minecraft:invalid"- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid2."}- Open the chest
No error message is printed
Relates to:
MC-91061: Probably caused by the fixThe bug
When you provide a LootTable name with a period the game is unable to find a loot table but does not print an error indicating this.
How to reproduce
- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid"}- Open the chest
The error is printed in the log: "Couldn't find resource table minecraft:invalid"- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid2."}- Open the chest
No error message is printedThe reason
The reason for this is that the method net.minecraft.world.storage.loot.LootTableManager.Loader.load(ResourceLocation) only prints the error message
Invalid loot table name '[LOOT_TABLE]' (can\'t contain periods)as debug message and not as error message.
Relates to:
MC-91061: Probably caused by the fixThe bug
When you provide a LootTable name with a period the game is unable to find a loot table but does not print an error indicating this.
How to reproduce
- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid"}- Open the chest
The error is printed in the log: "Couldn't find resource table minecraft:invalid"- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid2."}- Open the chest
No error message is printedThe reason
The reason for this is that the method net.minecraft.world.storage.loot.LootTableManager.Loader.load(ResourceLocation)
only prints the error messageInvalid loot table name '[LOOT_TABLE]' (can\'t contain periods)as debug message and not as error message.
Relates to:
MC-91061: Probably caused by the fixThe bug
When you provide a LootTable name with a period the game is unable to find a loot table but does not print an error indicating this.
How to reproduce
- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid"}- Open the chest
The error is printed in the log: "Couldn't find resource table minecraft:invalid"- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid2."}- Open the chest
No error message is printedThe reason
Please link to this comment in the description
The following is based on a decompiled version of Minecraft 1.9 using MCP 9.24 beta.
The reason for this is that the method net.minecraft.world.storage.loot.LootTableManager.Loader.load(ResourceLocation) only prints the error message
Invalid loot table name '[LOOT_TABLE]' (can\'t contain periods)as debug message and not as error message.
Relates to:
MC-91061: Probably caused by the fixThe bug
When you provide a LootTable name with a period the game is unable to find a loot table but does not print an error indicating this.
How to reproduce
- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid"}- Open the chest
The error is printed in the log: "Couldn't find resource table minecraft:invalid"- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid2."}- Open the chest
No error message is printedThe reason
Please link to this comment in the descriptionThe following is based on a decompiled version of Minecraft 1.9 using MCP 9.24 beta.
The reason for this is that the method net.minecraft.world.storage.loot.LootTableManager.Loader.load(ResourceLocation) only prints the error messageInvalid loot table name '[LOOT_TABLE]' (can\'t contain periods)as debug message and not as error message.
Relates to:
MC-91061: Probably caused by the fixThe bug
When you provide a LootTable name with a period the game is unable to find a loot table but does not print an error indicating this.
How to reproduce
- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid"}- Open the chest
The error is printed in the log: "Couldn't find resource table minecraft:invalid"- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid2."}- Open the chest
No error message is printedThe reason
The following is based on a decompiled version of Minecraft 1.9 using MCP 9.24 beta.
The reason for this is that the method net.minecraft.world.storage.loot.LootTableManager.Loader.load(ResourceLocation) only prints the error message
Invalid loot table name '[LOOT_TABLE]' (can\'t contain periods)as debug message and not as error message.
Invalid Loot Table names containing periods (".") do not create error message
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
Relates to:
MC-91061: Probably caused by the fixThe bug
When you provide a LootTable name with a period the game is unable to find a loot table but does not print an error indicating this.
How to reproduce
- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid"}- Open the chest
→ The error is printed in the log: "Couldn't find resource table minecraft:invalid"- Use the following command
/setblock ~ ~ ~ chest 0 replace {LootTable:"invalid2."}- Open the chest
→ No error message is printedThe reason
The following is based on a decompiled version of Minecraft 1.9 using MCP 9.24 beta.
The reason for this is that the method net.minecraft.world.storage.loot.LootTableManager.Loader.load(ResourceLocation) only prints the error message
Invalid loot table name '[LOOT_TABLE]' (can\'t contain periods)as debug message and not as error message.
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
is blocked by
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
'point' may also be called 'period' or 'dot' - this character: '.'
Is this still an issue in the latest snapshot 16w44a? If so please update the affected versions.
This is an automated comment on any open or reopened issue with out-of-date affected versions.
Can't seem to reproduce any error message anymore by using /setblock ~ ~ ~ minecraft:chest{BlockEntityTag:{LootTable:"invalid"}} and /setblock ~ ~ ~ minecraft:chest{BlockEntityTag:{LootTable:"invalid2."}}. May due to JSON being introduced?
In 20w07a (and probably earlier) loot table names containing periods are not considered invalid anymore.