The game crashes when referenced loot context parameters are not provided by certain loot tables

Most elements that uses loot context parameters confirm that paramaters they are goint to use is not null, and if that’s not the case they returns fallback value (number providers → 0, predicates → false, item modifiers → original stack, etc.).
However, following elements doesn’t perform such confirmation, which can results in crash if they are executed in context that doesn’t have try-catch (e.g. loot table when mobs are killed by non-player damage).

• EnchantmentLevelProvider

• EnvironmentAttributeValue

• EnvironmentAttributeCheck

How to reproduce

• Create world with attacked datapack.

• Perform following action to test these classes:

  • EnchantmentLevelProvider: Summon a silverfish and kill it by non-player damage (e.g. fall damage)

  • EnvironmentAttributeValue: Barter with a piglin.

  • EnvironmentAttributeCheck: Summon an arumadillo and use a brush on them via a dispenser.

• ※ These specific actions are to call loot tables without required parameter (enchantment_level for EnchantmentLevelProvider, origin for the other two) outside of try-catch (for exapmle, player attack or command have try-catch).

• Each of these action causes crash.