Refined Storage - Filters not working correctly with certain mods' items
Danekjovax opened this issue ยท 2 comments
Issue description:
When applying a filter to a crafting grid, sometimes the items specified in the filter aren't being specifically displayed the items list, but the whole mod's of related items instead. For example, I place a lead ingot from Thermal Foundation into the filter's items list, then place it into the crafting grid, the grid then shows all of the Thermal Foundation items in the system. I will note that the mod filter option is not checked when this happens.
Screenshots attached.
(originally posted at Freebi85/Dungeons-Dragons-Space-Shuttles#205 -referred here by modpack author)
What happens:
When placing the filter into the crafting grid's filter slot, the items displayed do not show the expected item(s) filtered.
What you expected to happen:
The list of items should only match the items placed into the activated filter. (with mod filter not checked).
Steps to reproduce:
- Have a Refined storage system running with various mod's of items in it.
- Make sure the RS system includes a crafting grid.
- Get an RS filter and place an item from one of the mods into it (see below for observed mods displaying this problem).
- Place the filter into one of the (4) filter slots of the crafting grid.
- You should see that the items listed do not specifically match what was placed in the filter.
Version (make sure you are on the latest version before reporting):
Minecraft: 1.12.2
Forge: 14.23.5.2836 (latest recommended version for the Dungeons Dragons and Space Shuttles modpack)
Refined Storage: 1.6.14
Does this issue occur on a server? YES
Known mods' which items are showing this:
Tech Reborn, ProjectRed Core, Thermal Foundation, Mystical Agriculture, NuclearCraft, Actually Additions, Mekanism
Play around with the damage/NBT options. Many mods register their items with the same name but different metadata or NBT.
There is not really a way to make it work well in 1.12 and the issue will mostly resolve itself in 1.14 so this will probably not get fixed.