Tool to detect duplicate patterns across all sources in network

[sibir-ine]

Is your feature request related to a problem?

AE2 doesn't warn about having patterns in your network with the same output, it just picks one & ignores the rest. This becomes especially problematic with mods like PackagedAuto & Lazy AE2 as it's difficult to detect duplicates across multiple sources.

Describe the solution you'd like

I'd like a tool that scans your network for patterns from all sources, especially including sources from add-ons such as PackagedAuto & Lazy AE2, & reports all instances of duplicates along with the coordinates of their sources & toggleable trackers for each similar to other tools in this mod.

Alternatives you've considered

If you suspect there are duplicate patterns for a particular item, you can test by removing the source of a known pattern & checking if it's still craftable in your network. I can't see any alternative for duplicate patterns you don't realize you have (I happened to find one when I looked at the crafting tree for something I ordered & realized one of the nodes was using the wrong recipe).

Affected components or scope

• ME Interface & ME Fluid Interface
• AE2 Fluid Crafting's ME Dual Interface
• PackagedAuto's Packager & Unpackager
• PackagingProvider's ME Packaging Provider
• Lazy AE2's Mass Assembler

Additional context

N/A

[Aedial]

So, iterating all recipe providers, asking for their recipes, and identifying which ones are have duplicated encoded recipes (I guess we can include some other error cases in the lot, like recursive ingredients in a single pattern). I recall the API of providers being fairly straight forward, so I should at least be able to iterate them and query their recipes.
I'll need to check with the AE2 API if I can get the location and name of a specific provider. At worst, it could be no location and only a class name (which should somewhat tell the source, albeit a bit dirty). Packager + Unpacker may be annoying, as it's a 2-recipes process. I guess I'll need a pair-matching step when a package is detected.

It shouldn't be hard to bold it onto the NHS.

[sibir-ine]

Invalid recipe detection could be useful too, though I don't know exactly how PackagedAuto or Lazy AE2 handle them.

[Aedial]

ICraftingProvider gives you inputs and outputs for the patterns, and acts as a black box taking in inputs and spitting outputs. The tree is then decided by AE2, so the handling should be fairly similar regardless of how it works for each provider.
Validating CRAFTING patterns still being valid after mods update is another matter, and depends if I get provided the pattern type by the provider (CRAFTING/PROCESSING).