Inside, a lone KX security droid stalks like some metallic werewolf, hunting unseen prey. That was Dan Gilroy’s vision for a stand alone episode of Andor - an entire self‑contained horror flick centered on K‑2SO, long before he ever met Cassian.
Gilroy pitched it as a monster episode. The tanker was a character in its own right: claustrophobic steel halls, flickering lights, the constant thrum of engines.
KX units are fast, strong, relentless:
In this story, one was trapped aboard, running down technicians and soldiers like a shark in a flooded submarine. Sound design would’ve been brutal: creaking bulkheads, alarms slicing the dark, K‑2SO’s servos scraping against metal as he turned corners.
Why didn’t we get it?
Money.
Visual effects budgets had already ballooned. Building that tanker ship environment, choreographing lengthy chase sequences, and staging intense kills would’ve broken the bank. Disney+ executives had to tighten the belt - Mon Mothma’s senate speech got bumped up, other arcs consolidated. The horror episode quietly dissolved.
It’s a shame. Introducing K‑2SO that way would’ve flipped our expectations. Instead of a one‑off monster, he arrives on Ghorman as a blunt instrument of oppression, then becomes the wisecracking partner we adore.
The horror draft leaned into the dark side of Empire tech - reminding us that these droids aren’t just tin cans - they’re mass‑murder machines when they’re not reprogrammed.
Tony Gilroy says the economics of streaming have shifted. Season 1 threw money around like confetti; season 2 had to pick its battles. Building half a battleship was fine; finishing it wasn’t. Still, the snippet we got - Cassian finding K‑2SO deactivated in a blood‑soaked protest—carries echoes of that horror DNA.
One day we might see the script scribbled out in dusty archives, a blueprint for what horror in a galaxy far, far away could be. Until then, it remains the 'Phantom Episode' - half legend, half regret, all atmosphere.
0 comments:
Post a Comment