So, per Slowpokes OP: What is targeted compatibility breaking code? (And specifically, this is a question
for Slowpoke / FTB policy)
Is adding recipes to the Forge recipe handler "targeted malicious code"? ...ever?
Nope
What if those recipes are copies of recipes previously removed by another mod?
Nope
What if that mod removing the recipes goes out of its way to make sure the recipes get removed, even if they are re-added?
Does it offer a way around the affected game play? If it does, then no. If it doesn't then yes.
What if the mod re-adding the recipes goes further out of its way to make the re-added recipes stick in-game, despite the fact that the removing mod goes out of its way to make sure they don't?
Again Does it offer a way around the affected game play? If it does, then no. If it doesn't then yes.
Does doing all this without a config option for the end-user change acts that were not considered compatibility breaking into acts that are considered compatibility breaking code?
Huh?
At what point does "going out of its way" to make sure a mods changes are not further changed itself constitute compatibility breaking?
huh?
Does a mod not following the configuration options
of an entirely different mod constitute compatibility breaking code?
No. But purposely acting on another mods changes by hacking his way around it does.
If so, wouldn't that mean whichever mod creates a config option first, effectively mean its the only one that can?
No
This boils down to: Is adding a recipe to the Forge recipe handler "modifying a mod in a way that is contrary to their wishes" and can the mod "add code to prevent [that]"? Considering the shared runtime environment of all mods and the central position Forge plays, is adding or removing a recipe even "modifying a mod"?
To wit, I link:
http://forum.industrial-craft.net/index.php?page=Thread&postID=121194#post121194
and
https://github.com/mDiyo/TinkersCon.../tinker/tconstruct/common/TContent.java#L1697