Enigmatica 6 - E6 - 1.16.5

Enigmatica 6 - E6 - 1.16.5

1M Downloads

Refined Storage: Crafter not Recognizing Fluid Cells in inventory or recipe

kondram opened this issue ยท 3 comments

commented

Modpack Version

1.8.0

Describe your issue.

Refined Storage crafters can craft fluid cells, but do not recognize fluid cells for any recipes requiring them, such as the electronic separator or the chemical oxidizer. For instance I have 5 fluid cells created with refined storage in the storage, but i cannot use the recipe for the oxidizer because it says it needs 3a nd cant craft them. I have tried exact or not exact options.

Crash Report

No response

Latest Log

No response

Have you modified the modpack?

No

User Modifications

No response

Did the issue happen in singleplayer or on a server?

Singleplayer

Discord Username

No response

commented

It's the nbt on the item. You need to use a crafted one to set the recipes for the next steps

commented

Thank you. Using this i was able to fix the recipes listed in my previous comment so there is no issue there.

However I am still running into an issue with blazing rods and the blazing agitator. Regardless of which blazing rod i add to the recipe and regardless if i use exact mode or not, the blazing agitator will only accept the blaze rods in the NEI with time 0, power 60 RF/t, duration 20 ticks, but the blaze rods that are created from the energizing orb only have power 200 RF/t and duration 5000 ticks (and no time).
2023-04-12_09 05 09
2023-04-12_09 07 10

commented

For me, it worked in both cases with these steps:

  1. Craft the ingredient (i.e. the Fluid Cell or the Blazing Rod) with Refined Storage
  2. Put the freshly crafted ingredient directly from the Pattern Grid's inventory into according recipe slots of your target recipie - the ingredient itself should never touch you inventory in that process. Save the modfied target recipe to the Pattern.
  3. Enable "Exact" mode for the recipe e.g. of Blazing Agitator

Idk which step the issuer missed, but the issue could probably be closed.