I understand it would be impossible to ignore the NBT data of the inputs of a craft due to how that could be exploited. It would be nice, however, if we could ignore the nbt data of the RESULT of the craft so that AE2 will still consider the result of a craft successful if it receives something slightly different than expected due to added NBT data such as with Integrated Dynamics connectors. I don't believe this could result in any kind of exploitation given that the items are already crafted prior to this check.

This would fix the issue with Integrated Dynamics connectors monopolizing a crafting computer due to not recognizing the crafting results entirely.

AE2 has no idea if something entered the system as a result of the craft or not. Ignoring NBT generally is not a option.
The real question is, why the expected result differs from the actual result. I don't really know the whole AE2 crafting system that well, so i can't say more about this.

AE2 not knowing what entered the system as a result of a craft isn't really here nor there when it comes to this. The point here is to have a flag on a pattern that says "if anything enters the AE2 system that matches the output of this pattern regardless of NBT consider the craft successful" The reason the expected result differs is because the resulting craft is given an NBT that assigns it a new "group". That's the reason for ID connectors at least. I'm not sure why ignoring NBT on this would not be an option. Perhaps someone could gum something up on complex nested crafting operations when turning this feature on for something, but it wouldn't crash anything. It would just result in that operation failing... which it already does because it doesn't consider the original craft this feature request is wanting to ever complete.

#481