ВЕРСИИ (18)

- port to 26.1 - fix mod crashing on dedicated servers - temporarily remove support for EMI, as it is not yet available on 26.1 - add JEI support

- port to 26.1 - fix mod crashing on dedicated servers - temporarily remove support for EMI, as it is not yet available on 26.1 - add JEI support

- fix incorrect registry creation ### Known issues: EMI might not display recipes properly if connected to a dedicated server.

- fix incorrect registry creation ### Known issues: EMI might not display recipes properly if connected to a dedicated server.

## 0.5.0 - Allow use item recipes to take multiple ingredients. The first ingredient contains the item stack in the main hand, the second one the item stack in the offhand. If less than one or more than two ingredients are present, parsing the recipe will fail. - Validate recipe ingredients and predicates. This should prevent exceptions from being thrown at runtime. - remove `spawn_at_player` in favor of `from_face`. This property determines how stacks are crafted. - Block Stacks (see below): If `from_face` is true, the block will be spawned at the block position next to the block on which the item was used. Otherwise, the block the player used the item on will be replaced. - allow blocks to be possible results. The placement of blocks is determined based on the value of the `fromFace` property which was introduced in this release. - Separate Ingredients and stacks. This means: - Stacks still test against recipe contexts, but contrary to ingredients and conditions, they should not return if they match a contexts, but rather true if they can be crafted under the current circumstances, e.g. if a block can be placed at the given `BlockPos`. - Stacks are now tested to check if they can be crafted, not if they meet certain conditions - the item and tag ingredients (which replace the item stack) have more freedom and can match against tags as well as specific items. ### Known issues: EMI might not display recipes properly if connected to a dedicated server.

## 0.5.0 - Allow use item recipes to take multiple ingredients. The first ingredient contains the item stack in the main hand, the second one the item stack in the offhand. If less than one or more than two ingredients are present, parsing the recipe will fail. - Validate recipe ingredients and predicates. This should prevent exceptions from being thrown at runtime. - remove `spawn_at_player` in favor of `from_face`. This property determines how stacks are crafted. - Block Stacks (see below): If `from_face` is true, the block will be spawned at the block position next to the block on which the item was used. Otherwise, the block the player used the item on will be replaced. - allow blocks to be possible results. The placement of blocks is determined based on the value of the `fromFace` property which was introduced in this release. - Separate Ingredients and stacks. This means: - Stacks still test against recipe contexts, but contrary to ingredients and conditions, they should not return if they match a contexts, but rather true if they can be crafted under the current circumstances, e.g. if a block can be placed at the given `BlockPos`. - Stacks are now tested to check if they can be crafted, not if they meet certain conditions - the item and tag ingredients (which replace the item stack) have more freedom and can match against tags as well as specific items. ### Known issues: EMI might not display recipes properly if connected to a dedicated server.

## 0.4.3 - Add +modloader to version - fix api jar uploading ### Known issues: EMI might not display recipes properly if connected to a dedicated server.

## 0.4.3 - Add +modloader to version - fix api jar uploading ### Known issues: EMI might not display recipes properly if connected to a dedicated server.

## 0.4.2 - set up unit tests for common module - Port to 1.21 - Fix registries not being created correctly ### Known issues: EMI might not display recipes properly if connected to a dedicated server.

## 0.4.2 - set up unit tests for common module - Port to 1.21 - Fix registries not being created correctly ### Known issues: EMI might not display recipes properly if connected to a dedicated server.

- ported to 1.20.6 - t ## Breaking Changes - the mutually exclusive resource location and tag fields for the block condition are now grouped into the `block` category like so: ```json5 { // this is new "block": { "id": "minecraft:stone" }, // nothing changed here "hardness": { "min": 1 } } ``` Instead of leaving out `id` and `tag`, one must now leave out the whole `block` key instead. If `block` is present, it must contain `id` *xor* `tag`. - support Neoforge instead of Forge

- ported to 1.20.6 - t ## Breaking Changes - the mutually exclusive resource location and tag fields for the block condition are now grouped into the `block` category like so: ```json5 { // this is new "block": { "id": "minecraft:stone" }, // nothing changed here "hardness": { "min": 1 } } ``` Instead of leaving out `id` and `tag`, one must now leave out the whole `block` key instead. If `block` is present, it must contain `id` *xor* `tag`. - support Neoforge instead of Forge

- added multiloader support

- added multiloader support

- Fix Tree rendering when a node only has a single child. - The complete API has javadoc comments now.

- Clients with immersive crafting will now be able to browse recipes. - Initial Condition tree implementation. Can be accessed from emi - more javadoc

- Added basic support for EMI (predicates are still missing) - Recipe in- and outputs are now based on the same powerful predicate-based system as recipe conditions.

Initial Release