Although I suppose it could be useful to maintain OreDupeFix separately as an standalone addon (currently it requires IC2, however, but I could change this if desired).
You should really keep making this Addon. There are many people who hate it to use my Addon (too much nerfing for them, lol).
If there's anything I can do in OreDupeFix to make it compatible, I'm open to suggestions. It is highly configurable, in that an empty 'preferred ores' dict will change nothing and cause no incompatibilities, leaving it up to the user to choose the oredict items they wish to replace, but I include a default config as to make it useful out-of-the-box.
I have also a highly Configurable Unification, but only for certain Mods as I cant control everyones Mods. We are both doing the same thing, it would not make sence to install both Mods. Maybe you could just detect the GregTech Addon, and then do nothing.
Maybe your Unification API could be integrated into Forge?
Good Idea.
Yeah, that was my original approach, hit some serious problems. A base edit to the ItemStack constructor to forcibly replace all newly-created stacks with the unified oredict item *almost* worked, but since various mods initialize their items in different phases (TE in @Init, IC2 in @PreInit, so even editing the mcmod.info priority was ineffective), the replacement item was not always available at the time each mod initialized. Didn't get far enough to look into replacing the valid subtypes, but the dupes in NEI still annoy me.. there's has to be a workable solution to this problem, somehow.
Believe me, this will not work. Many Mods use a Hash System of Item ID's and their Metadata for their Recipes. It would break all these Mods, as you cant hack those HashCodes.
* Add IC2 scrapbox replacements
How exactly did you do that? My way of doing it, is removing the WHOLE LIST of Scrapbox Items in preInit adding one Scrapboxdrop to the List (to not let others Crash) and then in postInit I'm adding the correct (and partially nerfed) Outputs.