added __on_player_chooses_recipe and __on_player_switches_slot events
This commit is contained in:
1 parent
fff3ccf3f6
commit
690c85f3b0
4 files changed
+126
No files matched your search
@@ -38,6 +38,50 @@ item_category('ender_pearl') => misc
|
||||
item_category('stone') => building_blocks
|
||||
</pre>
|
||||
|
||||
### `recipe_data(item, type?)`, `recipe_data(recipe, type?)`
|
||||
|
||||
returns all recipes matching either an `item`, or represent actual `recipe` name. In vanilla datapack, for all items
|
||||
that have one recipe available, the recipe name is the same as the item name but if an item has multiple recipes, its
|
||||
direct name can be different.
|
||||
|
||||
Recipe type can take one of the following options:
|
||||
* `'crafting'` - default, crafting table recipe
|
||||
* `'smelting'` - furnace recipe
|
||||
* `'blasting'` - blast furnace recipe
|
||||
* `'smoking'` - smoker recipe
|
||||
* `'campfire_cooking'` - campfire recipe
|
||||
* `'stonecutting'` - stonecutter recipe
|
||||
|
||||
The return value is a list of available recipes (even if there is only one recipe available). Each recipe contains of
|
||||
an item triple of the crafting result, list of ingredients, each containing a list of possible variants of the
|
||||
ingredients in this slot, as item triples, or `null` if its a shaped recipe and a given slot in the patterns is left
|
||||
empty, and recipe specification as another list. Possible recipe specs is:
|
||||
* `['shaped', width, height]` - shaped crafting. `width` and `height` can be 1, 2 or 3.
|
||||
* `['shapeless']` - shapeless crafting
|
||||
* `['smelting', duration, xp]` - smelting/cooking recipes
|
||||
* `['cutting']` - stonecutter recipe
|
||||
* `['special']` - special crafting recipe, typically not present in the crafting menu
|
||||
* `['custom']` - other recipe types
|
||||
|
||||
Note that ingredients are specified as tripes, with count and nbt information. Currently all recipes require always one
|
||||
of the ingredients, and for some recipes, even if the nbt data for the ingredient is specified (e.g. `dispenser`), it
|
||||
can accept items of any tags.
|
||||
|
||||
Also note that some recipes leave some products in the crafting window, and these can be determined using
|
||||
`crafting_remaining_item()` function
|
||||
|
||||
Examples:
|
||||
<pre>
|
||||
recipe_data('iron_ingot_from_nuggets')
|
||||
recipe_data('iron_ingot')
|
||||
recipe_data('glass', 'smelting')
|
||||
</pre>
|
||||
|
||||
### `crafting_remaining_item(item)`
|
||||
|
||||
returns `null` if the item has no remaining item in the crafting window when used as a crafting ingredient, or an
|
||||
item name that serves as a replacement after crafting is done. Currently it can only be buckets and glass bottles.
|
||||
|
||||
### `inventory_size(inventory)`
|
||||
|
||||
Returns the size of the inventory for the entity or block in question. Returns null if the block or entity don't
|
||||
|
||||
Reference in new issue
Block a user