-
Bug
-
Resolution: Fixed
-
1.15.2, 20w20a, 20w20b, 20w21a, 20w22a, 1.16 Pre-release 2, 1.16 Pre-release 3, 1.16 Pre-release 5, 1.16 Pre-release 6, 1.16 Pre-release 7, 1.16 Pre-release 8, 1.16 Release Candidate 1, 1.16, 1.16.1, 20w27a, 20w28a, 20w29a, 20w30a, 1.16.2 Pre-release 1, 1.16.2 Pre-release 3, 1.16.2
-
None
-
Confirmed
-
Data Packs
The bug
When checking a range in the entity_scores condition, you either need to specify an exact value, or both the lower and upper bounds. Using only min or only max results in the loot table or predicate not being loaded.
How to reproduce
- Create the following predicate in a data pack
{ "condition": "minecraft:entity_scores", "entity": "this", "scores": { "foo": { "min": 1 } } }
- Reload the world and notice that the predicate did not load
"Missing max, expected to find a Float"