You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
There is a compatibility issue with crafting recipes in that the recipe components require to be able to match exactly. This presents many issues with plugin compatibility.
Describe the solution you'd like
A very simple solution would be to add an option to a recipe to ignore NBT data for that recipes input items. This would unlock many possibilities with custom item/plugin compatibility.
Or a setting in a recipe to ignore specific NBT keys on the recipe components.
Describe alternatives you've considered
Alternatives are to make R*N recipes, R being the amount of recipes, and N being the amount of variant items which can turn a few recipes into many many recipes, especially in large project.
Additional context
Currently have a project where receiving an item in game will add a misc NBT tag to the item marking it as received and the value set for this tag is unique to the player which this makes it impossible to have crafting recipes for the item since that tag will never be the same.
Images | 相关图片
No response
The text was updated successfully, but these errors were encountered:
This fixes #74 to some extent, but you may need to provide items through other item plugins, not vanilla items because there is no special item identification NBT
Describe your idea | 描述你的想法
Is your feature request related to a problem? Please describe.
There is a compatibility issue with crafting recipes in that the recipe components require to be able to match exactly. This presents many issues with plugin compatibility.
Describe the solution you'd like
A very simple solution would be to add an option to a recipe to ignore NBT data for that recipes input items. This would unlock many possibilities with custom item/plugin compatibility.
Or a setting in a recipe to ignore specific NBT keys on the recipe components.
Describe alternatives you've considered
Alternatives are to make R*N recipes,
R
being the amount of recipes, andN
being the amount of variant items which can turn a few recipes into many many recipes, especially in large project.Additional context
Currently have a project where receiving an item in game will add a misc NBT tag to the item marking it as received and the value set for this tag is unique to the player which this makes it impossible to have crafting recipes for the item since that tag will never be the same.
Images | 相关图片
No response
The text was updated successfully, but these errors were encountered: