- fix incorrect registry creation
### Known issues:
EMI might not display recipes properly if connected to a dedicated server.
### Known issues:
EMI might not display recipes properly if connected to a dedicated server.
沉浸式制作是一个库模组，为数据驱动的世界内制作提供支持。
制作配方完全由数据驱动，并位于 `data/{某个文件夹}/ic_recipes` 文件夹中。配方也可以使用 fabric-datagen API 进行生成。
沉浸式制作提供了几种内置的配方类型，例如在方块上右键点击物品时制作物品。一切都设计得可以高度定制。
文档
最新的文档可以在[这里](
示例
以下示例在玩家在夜晚用一堆钻石右键点击石英块时，制作一颗下界之星。
{
"type": "immersive_crafting:use_item_on",
"ingredient": {
"type": "immersive_crafting:item",
"stack": {
"count": 5,
"item": "minecraft:diamond"
}
},
"predicate": {
"conditions": [
{
"type": "immersive_crafting:invert",
"condition": {
"type": "immersive_crafting:day_time",
"end_time": 12999,
"start_time": 0
}
},
{
"type": "immersive_crafting:block",
"id": "minecraft:quartz_block"
}
]
},
"result": [
{
"type": "immersive_crafting:item",
"stack": {
"item": "minecraft:nether_star"
}
}
]
}
已复制！用法与依赖
- 沉浸式制作适用于 Fabric，并依赖于 [Fabric API](
链接 )。 - 建议使用 EMI 查看配方。未来将添加对 REI 和 JEI 的支持。
版本&下载
- fix incorrect registry creation
### Known issues:
EMI might not display recipes properly if connected to a dedicated server.
### 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
- 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
收录
