13 Times Star Trek Broke Its Own Prime Directive
2. A Taste Of Armageddon - Original Star Trek
This breach of the prime directive seems justified until you actually start thinking about it for more than a few seconds.
Kirk and friends find themselves caught between a war between Vendikar and Eminar VII, a very strange war where not a single shot is fired, and yet the death toll is IMMENSE. This is because both sides share a supercomputer that calculates how any given conflict would go for either side, and calculates who specifically would die. Those selected are then ordered to report to a machine that disintegrates them.
Seeing this for the insanity that it is (senseless violence with extra steps) Kirk of course destroys the machine and forces the two races to actually engage in real violence if they want to keep killing each other. The two opposing sides of course don't want that, so they sign a peace treaty.
All seems well, until you consider after about three seconds of thinking that a few years after Kirk leaves, these two sides will be right back at it all over again because no way is several generations of violence going to go away just because you smash up their primary means of killing each other. All Kirk has actually done is make all their future conflicts more chaotic and destructive. Don't think you quite thought this one through, Jimmy.