MCPE-150791/loot doesn't parse slashes correctly without quotes
The bug
Unlike other commands such as /function, /loot fails to parse slashes correctly and requires identifiers that use them to be quoted.
How to reproduce
- /function test/test
→
It correctly parses, but tells you the function was not found - /loot spawn ~ ~ ~ loot entities/pig
→
Syntax error
Also note that unlike in Java Edition, there are no command suggestions for loot tables in this command. This makes it impossible to determine what parameters are valid without an external resource.
Linked Issues
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
Created Issue:
/loot doesn't parse slashes correctly without quotes
The bug
Unlike other commands such as /function, /loot fails to parse slashes correctly and requires identifiers that use them to be quoted.
How to reproduce
# /function test/test
→
# /loot spawn ~ ~ ~ loot entities/pig
→
Also note that there are no command suggestions for loot tables even when files exist
The bug
Unlike other commands such as /function, /loot fails to parse slashes correctly and requires identifiers that use them to be quoted.
How to reproduce
# /function test/test
→
# /loot spawn ~ ~ ~ loot entities/pig
→
Also note that there are no command suggestions for loot tables even when files exist, making it impossible to determine what parameters are valid without an external resource.
relates to
![[Helper] lillybeacon](../../../data/avatars/users/93893.png){kind=small}
The bug
Unlike other commands such as /function, /loot fails to parse slashes correctly and requires identifiers that use them to be quoted.
How to reproduce
# /function test/test
→
# /loot spawn ~ ~ ~ loot entities/pig
→
Also note that there are no command suggestions for loot tables even when files exist, making it impossible to determine what parameters are valid without an external resource.
The bug
Unlike other commands such as /function, /loot fails to parse slashes correctly and requires identifiers that use them to be quoted.
How to reproduce
- /function test/test
→- /loot spawn ~ ~ ~ loot entities/pig
→
Also note that there are no command suggestions for loot tables even when files exist, making it impossible to determine what parameters are valid without an external resource.
The bug
Unlike other commands such as /function, /loot fails to parse slashes correctly and requires identifiers that use them to be quoted.
How to reproduce
- /function test/test
→- /loot spawn ~ ~ ~ loot entities/pig
→
Also note that there are no command suggestions for loot tables
even when files exist,makingit impossible to determine what parameters are valid without an external resource.The bug
Unlike other commands such as /function, /loot fails to parse slashes correctly and requires identifiers that use them to be quoted.
How to reproduce
- /function test/test
→- /loot spawn ~ ~ ~ loot entities/pig
→
Also note that unlike in Java Edition, there are no command suggestions for loot tables in this command. This makes it impossible to determine what parameters are valid without an external resource.