FADE was an exclusive Codemasters thing that died a while ago so I don't think it's listed anywhere as official copy protection.
I think this is why it wasn't listed under OPF on GameCopyWorld: "Operation Flashpoint (release) is NOT FADE protected! Version 1.10 and up are protected with the FADE protection!" - this was under the FADE page at GCW. Since 1.0 wasn't protected by FADE, it's not on the game page at GCW.
As for finding and disabling all the triggers in the code, I don't think you actually have to play the game to find them. Though, you do have to play through to test your fixes which is why games with TAGES sometimes have multiple cracks.
My point was that at least in one case (X2), the devs must have programmed the crippling triggers separately from the protection scheme, since that kind of protection is sometimes present in games that use non-trigger schemes (X2 uses SecuROM).
I remember using a crack that didn't completely wipe out FADE in OPF which resulted in my weapon accuracy decreasing to about 5%.
But the problems in X2 wouldn't be immediately apparent, unlike the accuracy problem in OPF. I'm talking about problems that only become obvious after hours of gameplay (such as gradually decreasing money).
If X2 was ever completely cracked (meaning the crack problems were resolved), I wonder how long it took? I suppose no developer could ever make a game crack-proof, but with enough triggers it could take a damn long time to crack properly.
EDIT: On closer inspection, it seems that later versions of SecuROM (including the one in X2) support triggers. It appears that a lot more devs could easily put triggers in their games, but they choose not to do so.
This comment was edited on Apr 22, 14:36.