New data pack component crafting doesn't work with suspicious stews
Expected result: Custom suspicious stew (in this case a modified azure bluet suspicious stew) recipe outputs the water breathing effect.
Actual result: Azure bluet suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Suspicious stew recipes that don't override vanilla recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world (see sus_stew_example-1.zip
) - Open world
- Craft azure bluet suspicious stew
- Craft flowering azalea suspicious stew
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Edit: I don't know if this will help, but I made a data pack that implements the vanilla recipes with the new components (see sus_stew_fix.zip
). To fix it, I used a block filter on the vanilla recipe in the .mcmeta file.
Created Issue:
New data pack component crafting doesn't work with suspicious stews
In my custom recipe I would expect to get a suspicious stew output with the water breathing effect, but it defaults to the blindness effect. The recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Note: Entirely custom suspicious stew recipes work fine (see attachment). Thus, I believe that my data pack is not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
1. Add a data pack to world with the recipe to override suspicious stews (here's mine for reference) [^suspicious_stew_from_flowering_azure_bluet.json]2. Open world
3. Craft recipe
In my custom recipe I would expect to get a suspicious stew output with the water breathing effect, but it defaults to the blindness effect. The recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Note: Entirely custom suspicious stew recipes work fine (see attachment). Thus, I believe that my data pack is not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
1. Add a data pack to world with the recipe to override suspicious stews (here's minefor reference)[^suspicious_stew_from_flowering_azure_bluet.json]2. Open world
3. Craft recipe
In my custom recipe I would expect to get a suspicious stew output with the water breathing effect, but it defaults to the blindness effect. The recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Note: Entirely custom suspicious stew recipes work fine (see attachment). Thus, I believe that my data pack is not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
1. Add a data pack to world with the recipe to override suspicious stews (here's mine [^suspicious_stew_from_flowering_azure_bluet.json])2. Open world
3. Craft recipe
In my custom recipe I would expect to get a suspicious stew output with the water breathing effect, but it defaults to the blindness effect. The recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Note: Entirely custom suspicious stew recipes work fine (see attachment). Thus, I believe that my data pack is not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
1. Add a data pack to world with the recipe to override suspicious stews (here's mine [^suspicious_stew_from_flowering_azure_bluet.json])2. Open world
3. Craft recipe
In my custom recipe I would expect to get a suspicious stew output with the water breathing effect, but it defaults to the blindness effect. The recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Note: Entirely custom suspicious stew recipes work fine (see attachment). Thus, I believe that my data pack is not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
1. Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json)
2. Open world
3. Craft recipe
In my custom recipe I would expect to get a suspicious stew output with the water breathing effect, but it defaults to the blindness effect. The recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Note: Entirely custom suspicious stew recipes work fine (see attachment). Thus, I believe that my data pack is not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
1. Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json)
2. Open world
3. Craft recipe
In my custom recipe I would expect to get a suspicious stew output with the water breathing effect, but it defaults to the blindness effect. The recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Note: Entirely custom suspicious stew recipes work fine (see attachment). Thus, I believe that my data pack is not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json
)
- Open world
- Craft recipe
In my custom recipe I would expect to get a suspicious stew output with the water breathing effect, but it defaults to the blindness effect. The recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Note: Entirely custom suspicious stew recipes work fine (see attachments). Thus, I believe that my data pack is not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json
)
- Open world
- Craft recipe
In my custom recipe I would expect to get a suspicious stew output with the water breathing effect, but it defaults to the blindness effect. The recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Note: Entirely custom suspicious stew recipes work fine (see attachments). Thus, I believe thatmydata packisnot superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).Steps to recreate:
- Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json
)
- Open world
- Craft recipe
Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result: Custom suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Entirely custom suspicious stew recipes work fine (see attachments). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json
)
- Open world
- Craft recipe
Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result: Custom suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description:
Entirely custom suspicious stew recipes work fine (see attachments). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).Steps to recreate:
- Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json
)
- Open world
- Craft recipe
Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result: Custom suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Entirely custom suspicious stew recipes work fine (see
and suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json
)
- Open world
- Craft recipe
Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result: Custom suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Entirely custom suspicious stew recipes work fine (see
and suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json
)
- Open world
- Craft recipe
Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result: Custom suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Entirely custom suspicious stew recipes work fine (see attachments). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json
)
- Open world
- Craft recipe
Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result: Custom suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Entirely custom suspicious stew recipes work fine (see attachments). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json
)
- Open world
- Craft recipe
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs,
Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result: Custom suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Entirely custom suspicious stew recipes work fine (see attachments). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json
)
- Open world
- Craft recipe
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs
,Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result: Custom suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Entirely custom suspicious stew recipes work fine (see attachments). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json
)
- Open world
- Craft recipe
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result: Custom suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Entirely custom suspicious stew recipes work fine (see
attachments). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).Steps to recreate:
- Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json
)
- Open world
- Craft recipe
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result: Custom suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Entirely custom suspicious stew recipes work fine (see ^suspicious_stew_from_flowering_azalea.json). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json
)
- Open world
- Craft recipe
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result: Custom suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description:
Entirely custom suspicious stew recipes work fine (see ^suspicious_stew_from_flowering_azalea.json). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).Steps to recreate:
- Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json
)
- Open world
- Craft recipe
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result: Custom suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Entirely custom suspicious stew recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add a data pack to world with the recipe to override suspicious stews (here's mine suspicious_stew_from_azure_bluet.json
)
- Open world
- Craft recipe
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result: Custom suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Entirely custom suspicious stew recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add
adata pack to worldwith the recipe to override suspicious stews (here's minesuspicious_stew_from_azure_bluet.json)
- Open world
- Craft recipe
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result: Custom suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Entirely custom suspicious stew recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world sus_stew_example.zip
- Open world
- Craft azure recipe
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result: Custom suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Entirely custom suspicious stew recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world sus_stew_example.zip
- Open world
- Craft azure
recipeProposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result: Custom suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Entirely custom suspicious stew recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world sus_stew_example.zip
- Open world
- Craft azure bluet suspicious stew
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Expected result: Custom suspicious stew recipe outputs the water breathing effect
Actual result:
Customsuspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.Description:
Entirely custom suspicious stewrecipes work fine (see suspicious_stew_from_flowering_azalea.json). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world sus_stew_example.zip
- Open world
- Craft azure bluet suspicious stew
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Expected result: Custom suspicious stew (in this case a modified azure bluet suspicious stew) recipe outputs the water breathing effect.
Actual result: Azure bluet suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Suspicious stew recipes that don't override vanilla recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world sus_stew_example.zip
- Open world
- Craft azure bluet suspicious stew
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Expected result: Custom suspicious stew (in this case a modified azure bluet suspicious stew) recipe outputs the water breathing effect.
Actual result: Azure bluet suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Suspicious stew recipes that don't override vanilla recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world (sus_stew_example.zip
)
- Open world
- Craft azure bluet suspicious stew
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Expected result: Custom suspicious stew (in this case a modified azure bluet suspicious stew) recipe outputs the water breathing effect.
Actual result: Azure bluet suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Suspicious stew recipes that don't override vanilla recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world (see sus_stew_example.zip
)
- Open world
- Craft azure bluet suspicious stew
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Expected result: Custom suspicious stew (in this case a modified azure bluet suspicious stew) recipe outputs the water breathing effect.
Actual result: Azure bluet suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Suspicious stew recipes that don't override vanilla recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world (see sus_stew_example.zip
)
- Open world
- Craft azure bluet suspicious stew
- (Optional) Craft flowering azalea suspicious stew
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Expected result: Custom suspicious stew (in this case a modified azure bluet suspicious stew) recipe outputs the water breathing effect.
Actual result: Azure bluet suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Suspicious stew recipes that don't override vanilla recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world (see sus_stew_example.zip
)
- Open world
- Craft azure bluet suspicious stew
(Optional)Craft flowering azalea suspicious stewProposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Expected result: Custom suspicious stew (in this case a modified azure bluet suspicious stew) recipe outputs the water breathing effect.
Actual result: Azure bluet suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Suspicious stew recipes that don't override vanilla recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world (see sus_stew_example.zip
)
- Open world
- Craft azure bluet suspicious stew
- Craft flowering azalea suspicious stew
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Edit: I don't know if this will help, but I made a data pack that implements this feature.
Expected result: Custom suspicious stew (in this case a modified azure bluet suspicious stew) recipe outputs the water breathing effect.
Actual result: Azure bluet suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Suspicious stew recipes that don't override vanilla recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world (see sus_stew_example.zip
)
- Open world
- Craft azure bluet suspicious stew
- Craft flowering azalea suspicious stew
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Edit: I don't know if this will help, but I made a data pack that implements this feature.
Expected result: Custom suspicious stew (in this case a modified azure bluet suspicious stew) recipe outputs the water breathing effect.
Actual result: Azure bluet suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Suspicious stew recipes that don't override vanilla recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world (see sus_stew_example.zip
)
- Open world
- Craft azure bluet suspicious stew
- Craft flowering azalea suspicious stew
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Edit: I don't know if this will help, but I made a data pack that implements this feature (see sus_stew_fix.zip
).
Expected result: Custom suspicious stew (in this case a modified azure bluet suspicious stew) recipe outputs the water breathing effect.
Actual result: Azure bluet suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Suspicious stew recipes that don't override vanilla recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world (see sus_stew_example.zip
)
- Open world
- Craft azure bluet suspicious stew
- Craft flowering azalea suspicious stew
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Edit: I don't know if this will help, but I made a data pack that implements this
feature(see sus_stew_fix.zip).
Expected result: Custom suspicious stew (in this case a modified azure bluet suspicious stew) recipe outputs the water breathing effect.
Actual result: Azure bluet suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Suspicious stew recipes that don't override vanilla recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world (see sus_stew_example.zip
)
- Open world
- Craft azure bluet suspicious stew
- Craft flowering azalea suspicious stew
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Edit: I don't know if this will help, but I made a data pack that implements this the vanilla recipes with the new components (see sus_stew_fix.zip
). To fix it, I blocked the vanilla recipe in the .mcmeta file.
Expected result: Custom suspicious stew (in this case a modified azure bluet suspicious stew) recipe outputs the water breathing effect.
Actual result: Azure bluet suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Suspicious stew recipes that don't override vanilla recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world (see sus_stew_example.zip
)
- Open world
- Craft azure bluet suspicious stew
- Craft flowering azalea suspicious stew
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Edit: I don't know if this will help, but I made a data pack that implements
thisthe vanilla recipes with the new components (see sus_stew_fix.zip). To fix it, I
blockedthe vanilla recipe in the .mcmeta file.Expected result: Custom suspicious stew (in this case a modified azure bluet suspicious stew) recipe outputs the water breathing effect.
Actual result: Azure bluet suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Suspicious stew recipes that don't override vanilla recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world (see sus_stew_example.zip
)
- Open world
- Craft azure bluet suspicious stew
- Craft flowering azalea suspicious stew
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Edit: I don't know if this will help, but I made a data pack that implements the vanilla recipes with the new components (see sus_stew_fix.zip
). To fix it, I use a block filter on the vanilla recipe in the .mcmeta file.
Expected result: Custom suspicious stew (in this case a modified azure bluet suspicious stew) recipe outputs the water breathing effect.
Actual result: Azure bluet suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Suspicious stew recipes that don't override vanilla recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world (see sus_stew_example.zip
)
- Open world
- Craft azure bluet suspicious stew
- Craft flowering azalea suspicious stew
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Edit: I don't know if this will help, but I made a data pack that implements the vanilla recipes with the new components (see sus_stew_fix.zip
). To fix it, I used a block filter on the vanilla recipe in the .mcmeta file.
Expected result: Custom suspicious stew (in this case a modified azure bluet suspicious stew) recipe outputs the water breathing effect.
Actual result: Azure bluet suspicious stew recipe defaults to the blindness effect, however, the recipe properly shows in the crafting table, but the result defaults to the vanilla output.
Description: Suspicious stew recipes that don't override vanilla recipes work fine (see suspicious_stew_from_flowering_azalea.json
). Thus, I believe that data packs recipes are not superseding the hardcoded recipes (in this case all of the "crafting_special_suspiciousstew" recipes).
Steps to recreate:
- Add the attached data pack to world (see sus_stew_example-1.zip
)
- Open world
- Craft azure bluet suspicious stew
- Craft flowering azalea suspicious stew
Proposed solution: Change all suspicious stew recipes to be data driven through data packs with the introduction of custom components in recipes outputs.
Edit: I don't know if this will help, but I made a data pack that implements the vanilla recipes with the new components (see sus_stew_fix.zip
). To fix it, I used a block filter on the vanilla recipe in the .mcmeta file.

Please attach a complete datapack .zip to help reproduce this issue
I have attached the datapack