The ‘Star Wars: Episode VII’ Spoiler We Won’t Share

By October 2, 2014
  2

I’ve been as transparent as possible with you guys when it comes to the minutiae of Star Wars: Episode VII coverage we’ve done on this site. Personally, I’m not a fan of spoilers and set photos, but we’ve published plenty of them here because – and I don’t have the numbers to back me up on this – but I think it’s safe to say that the upcoming Star Wars film is actually the most anticipated movie of all time. But because J.J. Abrams, king of the Mystery Box, is directing it, that means that the production has been shrouded in secrecy.

We’ve said from day one that if Lucasfilm and Disney would just release little snippets of information along the way, then scoopers wouldn’t need to dig quite as deep to uncover every possible aspect of the movie before it’s even finished principal photography. Instead, Abrams and Disney have attempted to control the information flow (and basically released next to nothing in an official capacity), and so the scoopers have been diving in headfirst to find out everything they can about the film. We’ve published a lot of it here because it was mostly harmless – stuff like the film’s basic plot, which characters certain actors might be playing, the return of the Millennium Falcon, etc. – but last night, things took a turn for the worse.

Apparently a few of the Star Wars fan sites have picked up a massive spoiler that will completely ruin the film for you. Badass Digest says their source described it to them as the “I am your father” moment from Empire Strikes Back. That’s the level we’re talking about here – a huge, end-of-the-movie type “oh sh*t” moment that will have everyone talking when they walk out of the theater in December of 2015. Here’s what BAD had to say:

There’s still plenty of stuff for me to discover and share with you, but I fear we’re reaching a saturation level where we’re going to have the whole movie outlined before it even goes into post-production. This latest rumor feels very much like crossing a line in the sand, going from fun reveals of small details to experience-ruining disclosures.

At GeekNation, we’re about the celebration of film, television, and pop culture – we want to get excited with you, celebrate with you, dissect with you, and discuss with you. We don’t want to straight up ruin anything for you. Thankfully, I haven’t personally seen this Star Wars spoiler yet myself and I won’t seek it out, either. I actually still want to have a bit of fun when I finally sit down to watch the movie, and even though I’ve written a ton about it so far and have a working knowledge of most of the major reveals that have hit the web, I’m still hoping that Abrams is going to surprise me with something. But if every single reveal arrives online before the movie opens, that will hugely change the way we first interact with this film.

I’m a spoiler-phobe, and though I’d like to not know a single thing about the new Star Wars movie (for example, I haven’t seen a frame of footage from Interstellar yet because I’m looking forward to it so much), I’ve bitten the bullet and learned all of this stuff about it so I could talk to you guys about it in case you’re looking for a spot to discuss Star Wars. I’ve marked everything with clear spoiler warnings, and made sure to respect those of you like me who’d rather not know anything. I’m glad I don’t know what this huge Episode VII reveal is. I hope I don’t find out what it is until I’m sitting in the movie and it happens on screen.

I’m not going to stop writing about Star Wars: Episode VII, but I’ve seen a lot of sites say they aren’t going to spread this rumor around because there’s nothing to it other than just ruining a huge surprise. That’s no fun for anybody, and I’ll join them in taking that stand. I’ll still write about Star Wars (pretty regularly, I’m guessing), but it’ll be about little things akin to those we’ve written already – who the villains are, broad strokes about the plot, character’s names and how they fit into the larger picture, and stuff like that.

Wouldn’t you have been pissed off if you went into The Empire Strikes Back knowing that Vader was Luke’s father? Wouldn’t you rather have that gasp-inducing moment to remember for the rest of your life? I know I would, and I hope you would, too. Keep checking back here for more Star Wars news, but know that we’re not going to spoil anything for you unless we put a spoiler warning in front of it, and we won’t spoil anything huge just for the sake of spoiling it.

The following two tabs change content below.
Ben is a writer living in Los Angeles, California. His work has been featured at ScreenRant.com, FirstShowing.net, MySpace.com, GeekTyrant.com, and many more sites across the web. Some of his favorite movies include The Rocketeer, Anchorman: The Legend of Ron Burgundy, Tombstone, Lucky Number Slevin, Raiders of the Lost Ark, Ferris Bueller's Day Off, Collateral, Double Indemnity, Back to the Future and The Prestige. Follow him on Twitter: @BenPears.