I will add a Config to disable the PFAA Detection so that it is easier to re-enable GT worldgen, but that detection will default to on, because of the aforementioned terrible lag that would cause.
Hmm. COG without PFAA already does this. It replaces GT ores with stone and runs its own generation of GT ores. With FastCraft at least, the lag does not seem prohibitive.
As Jason suggests, I guess the optimal solution would be for PFAA to tell GT via some sort of API when the PFAA ore generation is
disabled. I can access GT_Config, of course, but if I changed an option, GT would need to respond via ConfigChangedEvent. This would take a lot more work than the simple COG replacement.
It would seem there is a need for a mod that would allow mod pack users to see a few high-level options in the Forge config GUI. Just simplified, where setting a particular option can affect multiple options in different mods.