I used my internet prowess to cache back the original State of Play review so I could copy-paste then re-post it. Took down the poster and the script link so I don’t think there’s anything illegal going on here. Enjoy. :)

Genre: Political Thriller
Synopsis: A team of investigative reporters work alongside a police detective to try to solve the murder of a congressman’s mistress
About: Hitting theaters a week from Friday and landing on the 2007 Blacklist as the number 2 most popular script.
Writer: Matthew Michael Carnahan – Revisions by Billy Ray, Tony Gilroy, and Peter Morgan.

State of Play may be coming to theaters in a couple of weeks but why wait that long when you can get the lowdown right here and now. I won’t even charge you ten dollars. And yeah, it’s the shooting script. So we’re talking a shot-for-shot match here baby.

As I mentioned before, State of Play was the number 2 script on the 2007 Black List. Right behind a little script called “Brigands of Rattleborge”, which just so happens to be number 6 over there on my Top 25. Why isn’t State of Play above it? Cause I never read the damn thing. Everything about it sounded boring as hell. Look at the title: “State of Play”. What the hell does that even mean?? It’s stupid. And the logline doesn’t help matters: “A team of investigative reporters work alongside a police detective to try to solve the murder of a congressman’s mistress.” Ooh, can’t wait to dive into that one. If anything, it seemed like State of Play was trying its best NOT to interest me. Operation Success.

But then that damn trailer hit in high definition and my interest did a 180. This looked like a real movie. And I mean come on. Any film that believes its good enough to survive a Ben Affleck casting has got to be awesome. All of a sudden “State of Play” sounded kind of cool. The title began to make sense. It’s like a “state” of “play”. Or the “play” that goes on in the “state”. Meaning like the government. Clearly works on many levels.

I think you know by now what this film is about. A woman’s been killed, hit by a morning subway train, and that woman is linked to congressman Stephen Collins. The problem with this is that Collins is married. When he finds out that the woman has been killed, he’s put in a rough spot. His heart is broken because he loved this girl. But he can’t emote because he has a wife. On top of that, he has to survive the media’s determination to turn it into a scandal or his career is over.

Cal, the seasoned reporter, just so happens to be old friends with Collins. The paper knows this and comes down hard on him. They have a chance to break a huge story with inside information if only Cal does what Cal needs to do. So Cal is put in that classic reporter predicament. Do I do my job or do I help a friend? That’s the central theme of State of Play and it keeps poking its head up the deeper Cal digs. It’s also why I don’t love this script. I don’t exactly have sympathy for a character who’s willing to sell his friend out to get a goddamn newspaper story.

Luckily State of Play focuses just as much time on its mystery – and its mystery is a good one. Turns out the woman who was pushed in front of the train wasn’t just a congressional aid. She was working for a corporation called Pointcorp that has begun privatizing armies to fight in the Middle East with further plans to privatize armies and even government here in the United States. Collins, who is vehemently against privatization, is lobbying congress to stop these corporations. So Pointcorp bought this woman to relay all of Collins’ secrets.

In the meantime, Collins’ wife ain’t as mad as she should be. In fact, she’s more humiliated than angry. And it certainly doesn’t help matters that she’s sleeping with Cal. Yes, Collins’ best friend and newspaper reporter Cal. So you can see how intricate and complicated all of this gets.

Somehow Cal has to navigate this jungle to get the story, as well as avoid Pointcorp, who’s willing to do anything to make sure the story doesn’t break – putting almost everybody’s life in jeopardy. And of course in the end, he has to make that decision. Get the story or keep the friend?

I liked State Of Play. I thought it was well done for a genre I don’t particularly like. But if I were a reporter, the story I’d be breaking is just how behind the times State of Play is. Rachel McAdams (my favorite actress EVER behind Audrey Hepburn) plays web blogger Della, who seems to be thrown in the mix for the sole purpose of feeling “current”. But if you eliminated her character it wouldn’t affect anything because the whole drive of the movie revolves around Cal trying to get the story in by print time for tomorrow’s paper. Um, excuse me, but when the fuck does that happen anymore? Someone gets shot these days and five minutes later it’s on Youtube. Stories get written in real time, published as keys are being pressed. When the hell do they have “newspaper deadlines” for breaking news anymore? In that sense, this could be the last time (sans period pieces) they make a movie like this. I think it also inspires a curiosity for a movie that fully explores the behind-the-scenes going-ons of the lightning fast news world of today. There’s a good movie to be written there.

Even so, State of Play is a solid thriller and a script worth reading – even with the knowledge that Ben Affleck is playing one of the leads. :)

[ ] trash
[ ] barely kept my interest
[x] worth the read
[ ] impressive
[ ] genius

What I learned from State Of Play: One thing I do when I’m enjoying a script is trace back to where the feeling started. It’s a great way to learn what works in a screenplay. In this case, a nameless woman is killed by a subway train. That’s not necessarily interesting. We meet Collins, who’s told that one of his assistants, a woman, was hit by a subway car. His reaction tells us there was something between them but we don’t know what. This makes the script more interesting but not necessarily “I have to keep reading” interesting. It’s when we see Collins break down in the press conference and learn that not only did he have a sexual relationship with this girl, but that he’s married. That’s when we become truly interested. Because we’re intrigued by characters who are put in terrible and/or complex situations. Because these situations force our character to make a difficult choice. And that choice is always interesting, whether we agree with it or not. What does he say to his wife? Does he tell her the truth? What does he say to the media? Does he tell *them* the truth? What does he tell his friends? And in the case of State of Play, what does he tell his friend who works for the very people he can’t tell anything to (the media). You see how complicated and interesting this gets? That’s good writing.

Well karma comes back to bite you in the ass, huh? The State of Play script review I posted today was taken down by Blogger because of a Universal legal threat. It’s not clear to me if it’s because I posted the review, used a picture of the poster, or posted the script. What pisses me off is that they erased the review not only from the blog, but from my personal blogger database, which means it doesn’t exist anymore. Not too happy about that. For those who are screaming, “why didn’t you back it up?”, my answer will ring true to anyone who’s tried to copy and paste a Word document into Blogger (my old method). The html goes nuts and requires 18,000 adjustments before you post. Therefore I just kept everything online.

So all you angry readers pissed off about my Inception review, you got your revenge! lol

Okay so last week got a little crazy with the Inception April Fool’s Day joke and I apologize to anyone who was offended (not really though). But my little made-up plot was good enough to convince a few people (Hey, it was a pretty fucking cool idea. I’d see that movie). They even had a little blurb about it at /Film. In order to sell the lie on April Fools’ Day I had to resort to some drastic measures, informing good friends that Warner Brothers was close to putting me behind bars. It wasn’t easy. To relive the fun, here’s the pretend review for Inception.

So we’re going to stay with the “bad joke sci-fi” theme and review a little script called “Battle: Los Angeles” – which should’ve been titled “Battle: For My Attention”. It does contain, however, the very first Scriptshadow embedded picture. So it’s a landmark in that sense.

For those of you who sent angry e-mails demanding a link to “The Details” script, I’ve finally posted one. Go back to the original review here: The Details and the link is at the bottom. Also, for all you development pimps, I’m trying to get my hands on a script called “Nonstop” which sold to Dreamworks last month, as well as Zach Braff’s latest script, “Andrew Henry’s Meadow.” I have a couple others I’m looking for in my appropriately named “Scripts I’m Looking For” list (down and to the right). They’re rare enough that if you can get me any of them, I will be your BFF for the remainder of 2009, and most of 2010. And of course if there’s anything hot out there that you want reviewed, send it my way.

This week’s first review is posted BELOW this post. Enjoy.

Genre: Sci-Fi Action
Synopsis: Aliens take over Los Angeles. We try to take it back. I think.
About: This is being made into a movie to star Aaron Eckhart and directed by the guy who directed Texas Chainsaw Massacre: The Beginning.
Writer: Chris Bertolini

The original Battle of Los Angeles took place in 1945 right here where I live, in Culver City, California (a suburb of Los Angeles). Remember, after Pearl Harbor, the U.S. was gripped by the fear that their distance would no longer protect them. It wasn’t unlike 9/11 when we assumed that every plane we went up in was going to be hijacked (or at least I did). So the U.S. set up these gun stations to protect the major cities. Then one night, a strange object appeared in the sky. Huge sky lights pointed up at the air vehicle and the army blasted away at it with every bullet they could find. It was that night that this famous picture was taken.

(note: yes, Scriptshadow just went multimedia)

For those that care, I can see this very spot from my apartment right now!

Anyway, there are UFO pundits who use this picture as solid evidence that UFOs are real. Skeptics, however, point out that all the numerous lights do is distort the image, making it impossible to tell what it is. Although generals on the scene swore it was some sort of hovering craft, later on their statements changed, saying they weren’t sure what it was. Some even theorized that it was a commercial airplane (of which nobody knew where it originated nor where it landed – plus it was somehow able to avoid the collective firepower of the United States army) Some even say it was nerves. Just us being so afraid something was going to happen, that we created the scenario out of fear. I just think it’s cool that it happened a few blocks away from where I live.

The reason I bring this up is because it was this scenario – vaguely – that inspired Battle: Los Angeles, the script I was unfortunate enough to read last night.

Maybe it was because period pieces don’t sell. Maybe it was because the studio was too lazy to do the research. But somewhere along the way they decided to base their film in the present. And this is how we got one of the worst action scripts I have ever read.

So the movie starts off kinda cool. Meteors shoot into the ocean a couple of miles off the coast of Los Angeles. Minutes later, beachgoers witness a strange alien like army oozing out of the water “first ten minutes of Saving Private Ryan”-style. These aliens are nasty, they’re fast, and they kill on site. Within seconds they’re shredding the suntanning populace to pieces and moving into the city of Santa Monica.

And then the movie proceeds to turn into total and complete SHIT. Santa Monica evacuates, leaving this army of 50,000 aliens to take over apartments, houses, Pinkberrys, and Jamba Juices (thankfully Tito’s Tacos was spared). As night falls, someone in the army makes the decision to send 5 marines into the city to………I have no fucking idea why. Look around? Check things out? Yes, because it makes total sense to send 5 marines into a city overtaken by 50,000 lightning fast superhuman strength flesh-ripping aliens. Makes total sense to me. Particularly since their mission is so clear. To like….go in….and check things out.

The marines head into the city: At night. I guess cause going in there at night gives them an advantage over the aliens.

After getting into a few battles with the aliens, they find a group of people left behind. Their mission now becomes to get *out* of the very city they were just told to go into (for no reason).

That’s pretty much the movie right there. I’d tell you who the characters were but I forgot. They were so bland, so boring, that I instantly forgot who they were as soon as I finished the script.

I will not fault the writer for this mess. There is no way even the least talented writer in the world could’ve come up with something this bad. He had to be working with notes given to him by some clueless studio executive. This so wreaks of lack of imagination that it’s the only way I can explain it.

This is going to be a real movie. No, I’m serious. Out of words.

[x] trash
[ ] barely kept my interest
[ ] worth the read
[ ] impressive
[ ] genius

What i learned from Battle: Los Angeles: Nobody cares about your characters being in peril if we don’t know anything about or like the characters. And that’s this entire movie – is these marines in peril. Who cares? I don’t know a single one of these guys. None of them have any problems. None of them have any goals. None of them have done anything to help me identify with them. Take those extra few pages at the beginning of your action script and introduce us to your main characters. All the better if you do it in an entertaining way. Please see “Aliens” as the best example of this. Terrible.