Here is my two cents on the matter. I never really enjoyed GregTech, most of what it did was make things more difficult, much like those games were you end up dying every 10 steps, and after the 100th death, or in this case after the 100th machine built to build another machine which used to be beginning-mid game, I just get bored, there is not fun anymore just tedium, tedium isn't challenge, it never has been and never will be. In those games where you die every 10 steps, you always die the first time you encounter a challenge, no matter how skilled you are, but through a brute force method of trial and error you eventually learn the precise and only method of passing a certain point in the game without dying. That is exactly what GregTech is, pointless tedium which forces you to do everything his way, no fringe area for creativity, just pointless tedium. Sure there are some great machines you can makes after a few thousand hours of playing, which I still haven't used, and so haven't gotten to enjoy the actual GregTech mod, I've only experienced all his tweaks to other mods. That being said, he did have every right to mod the game in any way he saw fit including the modifying of other mods. My main gripe with GregTech was that FTB left the default config settings enabled, forcing most multiplayer FTB players to be stuck with the more difficult GregTech recipes, I also had a gripe with FTB using Thermal Expansion for ore generation and not changing the configs to produce a decent amount of ore, but that is entirely another matter. In any case, I was entirely fine to continue playing FTB, despite its flaws, at least until I saw this entire debacle unfold on the forums.
So apparently Tinkerer's Construct and Greg Tech both made modifications that enhance their own mods personally, which is good for them, and good for us, but interaction between the mods created what many have termed an "exploit", even though there is no such a thing as an exploit or overpowered feature in a sandbox game. This might get filed into the category of bug, since neither of the modders intended for it to happen. In my own personal opinion, it should be up to whomever has a problem with the bug to fix it as, like I said, this is a Sandbox game and there is no such thing as an exploit or overpowered feature. If one of the modders doesn't see a problem with the "exploit" then there is no reason for them to change it. In this case the responsibility fell on Gregtech since he was the one with the issue, but instead GregTech throws a hissy fit like a little girl and completely disables the other modder's feature. I admit that it would be a lot harder to fix from his end, but that could have been resolved with mature conversation with the other modder to work out a resolution that didn't force either of them to remove their feature, but prevented the bug. That right there is bad behavior, and should've been indication for everyone to abandon ship. I mean who sails on a temperamental boat right? Okay enough with the metaphors, the point is this matter was settled, but there was still bad blood between the two modders.
What happens next is Gregtech advances his vendetta against casual to moderate gamers by nerfing the MOST basic recipe of the entire game, wood. Which is his right, if I don't like it, I don't have to install it ... but other people liked portions of GregTech and hated that particular nerf, thus Tinkerer's Construct changed the recipe back as there was no config option. (and there really should've been when messing with vanilla recipes). This spark's their little lover's quarrel which all of us got caught in the fallout of: GregTech modifying the game such that it crashes when Tinkerer's Construct is installed. This is boldfaced MALWARE, a programming sin, and even the most stalwart GregTech defenders cannot dispute this fact, though they have apparently tried to by claiming that the crash is not a crash at all, it is a gracefully handled exception, which I say balls to. As a programmer myself, I can easily say that any exception, handled, unhandled, or otherwise, that causes the program to close unexpectedly (from the user's point of view, not the modder's) is a crash.
For those of you who don't know what an exception is, it is actually code generated by the programmers themselves to catch erroneous behavior. For example, if I have a grid of data, I will often program an exception to occur if the program (or user) tries to pull data from outside the grid boundaries, I can then either choose to catch the exception and handle it my way, or let the program calling on my program handle the exception, which often results in the OS itself handling the exception which has only one method of handling the exception and that is to close the program. If I choose to handle it my way, I can still be lazy and cause the program to close, though in some extreme cases the only way to handle the exception is to close the program. In almost all cases Exceptions are programmer defined, so if I knew the program would have a facial recognition software input I could cause the program to crash if the user had red hair, and everyone would agree with me, that would be an abuse of my power as a programmer. This is essentially what Gregtech did, it detected that Tinkerer's Construct was installed, threw an exception, and aborted the program. A very immature and lazy way to handle the problem at hand. He could have had a conversation with the other modder, he could've changed the recipe back to his version (which would've been immature and solved nothing), he could've (and this would be the best way to handle the problem) called on an outside party to resolve their dispute for them. He chose instead to harm the very community that supports him and distribute malware.
Though this last little bit is hearsay, if true, it really underlines the type of person the author of GregTech is and what kind of future behavior we can expect from him. That is that Gregtech was modified to scan for the username of the author of the Tinkerer's Construct mod and, if found, replace his helm with a pumpkin, and looped this programming code so that it was executed every tick. Very immature, but again, hearsay. So just going on what we know: GregTech crashes (or rather crashed, though that it happened at all is in very bad taste) Minecraft with Tinker's Construct installed, I think FTB should officially stop supporting this modder. We the users need to stop tolerating this kind of behavior from modders. The ultimate sin of programming is distributing Malware which Gregtech has unabashedly done. And what happens? we give the guy his own modpack? Seriously?! I can see giving the guy a second chance by allowing people to continue downloading it as an optional part of a larger modpack. But actually giving him his own modpack so he can throw his little child tantrums and get whatever he wants? I don't think so. Malware distributors in the modding community should be shunned by the modding community. Giving Gregtech his own modpack is only telling everyone out there that we are okay with malware on our computers, for right now it is limited to crashed minecraft clients, but it could easily expand into spyware, which is a much more serious issue.
In conclusion, though neither mod author showed very much maturity in the events that have transpired, GregTech committed the ultimate sin in programming, and should be forced to wear the metaphorical pumpkin of shame, not the virtual one he forced the Tinkerer's Construct author to wear, but by us as a community pulling the plug on his mod by refusing to download it.
Also, sorry for the poor grammar, run-on sentences, and uber long paragraphs, I tend to forget these things in the face of extreme stupidity (which is ironic, I know) and apologies to the author of Tinker's Construct, whose username I couldn't remember the exact spelling of. And finally apologies to the moderators of this forum for stepping on their rules here and there a little, but I could not see any other way to bring attention to the gravity of the situation. *awaits impending ban hammer and trolls*