Complications Ensue: The Crafty Game, TV and Screenwriting Blog
Complications Ensue:
The Crafty Screenwriting, TV and Game Writing Blog


April 2004

May 2004

June 2004

July 2004

August 2004

September 2004

October 2004

November 2004

December 2004

January 2005

February 2005

March 2005

April 2005

May 2005

June 2005

July 2005

August 2005

September 2005

October 2005

November 2005

December 2005

January 2006

February 2006

March 2006

April 2006

May 2006

June 2006

July 2006

August 2006

September 2006

October 2006

November 2006

December 2006

January 2007

February 2007

March 2007

April 2007

May 2007

June 2007

July 2007

August 2007

September 2007

October 2007

November 2007

December 2007

January 2008

February 2008

March 2008

April 2008

May 2008

June 2008

July 2008

August 2008

September 2008

October 2008

November 2008

December 2008

January 2009

February 2009

March 2009

April 2009

May 2009

June 2009

July 2009

August 2009

September 2009

October 2009

November 2009

December 2009

January 2010

February 2010

March 2010

April 2010

May 2010

June 2010

July 2010

August 2010

September 2010

October 2010

November 2010

December 2010

January 2011

February 2011

March 2011

April 2011

May 2011

June 2011

July 2011

August 2011

September 2011

October 2011

November 2011

December 2011

January 2012

February 2012

March 2012

April 2012

May 2012

June 2012

July 2012

August 2012

September 2012

October 2012

November 2012

December 2012

January 2013

February 2013

March 2013

April 2013

May 2013

June 2013

July 2013

August 2013

September 2013

October 2013

November 2013

December 2013

January 2014

February 2014

March 2014

April 2014

May 2014

June 2014

July 2014

August 2014

September 2014

October 2014

November 2014

December 2014

January 2015

February 2015

March 2015

April 2015

May 2015

June 2015

August 2015

September 2015

October 2015

November 2015

December 2015

January 2016

February 2016

March 2016

April 2016

May 2016

June 2016

July 2016

August 2016

September 2016

October 2016

November 2016

December 2016

January 2017

February 2017

March 2017

May 2017

June 2017

July 2017

August 2017

September 2017

October 2017

November 2017

December 2017

January 2018

March 2018

April 2018

June 2018

July 2018

October 2018

November 2018

December 2018

January 2019

February 2019

November 2019

February 2020

March 2020

April 2020

May 2020

August 2020

September 2020

October 2020

December 2020

January 2021

February 2021

March 2021

May 2021

June 2021

November 2021

December 2021

January 2022

February 2022

August 2022

September 2022

November 2022

February 2023

March 2023

April 2023

May 2023

July 2023

September 2023

November 2023

January 2024

February 2024

June 2024


Wednesday, April 30, 2014

Jim Henshaw over at The Legion of Decency has a wise post about "The Scene You Don't Write," referring to a particularly shocking scene in the last Game of Thrones but one, involving what went down in a tomb. Also, there was a similar scene he was asked to write years ago, which he refused to write, because it would have destroyed the hero as a character.

(There are not, technically, spoilers in what follow, but clever readers will probably figure stuff out, so if are you are behind in your GoT watching and zealously avoiding social media, read not on.)

I've noticed that certain directors and certain network execs have a very different point of view than I do about what we're putting on screen. I'm all about the story and the characters. I want to tell a story that moves the audience. I've noticed that many directors want most of all to thrill the audience. They want wow factor. They want spectacle. They pay lip service to story and character, but what they really want is cool moments, especially if they can put those cool moments on their reel. How those moments figure into the story is sometimes secondary.

"Why? Because it's cool, that's why."

I'd like to say that these directors' movies don't turn out well, but it's not true, depending on your definition of "turning out." Just about everyone I know thought the STAR WARS prequels were embarrassing, but they made Panamax-sized boatloads of money.

What happens between Cersei and her loving brother is not in the novel. So one wonders what was going through the writers' heads as they wrote the scene. Was it a dictum from HBO? Their mandate is basically, "stuff you can't put on TV":

Well, you certainly can't put the Cersei/Jaimi scene on broadcast TV, now can you. So that is all win. Right?

Of course, it does make Jaimi despicable, which the writers address by having the characters never, ever bring up what happened ever again, sort of like the Supreme Court and Bush v. Gore. That's what makes me suspect that the scene didn't come out of the writing room, but was a network dictum. If the writers had come up with it, they'd have run with it.

Oh, and Jaimi is superdecent to someone in the next episode, maybe by way of apology?

So what do you do when a director or a network wants to have a character do something that is horribly out of character, and will damage the story edifice you have carefully constructed?

This is a problem that every pro writer deals with constantly; because, unless you're writing a spec, you are responsible to whomever hired you. But you are also responsible to the story; and if your credits are a bunch of crap movies, it's unhealthy for your career (though it is healthier than no credits). It is hard being a good servant to two masters. You can attempt to explain why it's a horrible idea. You can threaten to quit (not recommended). You can actually quit (definitely not recommended).

Or you can try to modulate the bad idea in some way, and twist it so that it's not a bad idea.

The two best things you can do are (a) find the good version of their bad idea, so that you are indeed giving them the scene they want, but in a context where it is not a bad idea; or (b) offer them something equally or more spectacular that obviously will not work with the bad idea, so they have to choose one or the other.

If you can do either of these, people will love to work with you, and you won't feel like a hack or a whore.

I generally find that there is a good version of most "bad" ideas. Figuring it out starts with really isolating ad crystallizing what exactly it is that the client wants. They usually want to fix something they perceive as broken. Try to find out what's behind the bad idea, even if it's lonely-puppy syndrome. ("You haven't given me enough toys to play with, so I'm going to chew on the couch.")

If you have to write the bad scene, then write it so that it can be taken out of the script without damaging anything. I.e. don't put any important exposition or plot development in it. Maybe, with luck, it will get taken out in post when your exec or director realizes what he or she has done.

Always, always respond to a bad note on a different day than you get it. In the morning, it may not be such a bad note. That's why the phrase "I'll have a look at that" is your friend.

Of course, there are some situations, like Jim H's, above, where you really have to choose between a rock and a hard place. That's where you get to decide whether you want to be a righteous, proud writer, or a rich one. Up to you. "Pride, plus a sack, is worth a sack," as the Ferengi say. But, as we say in New York, if you can't live with yourself, it's going to be hard to find an apartment.


If you want to see how the series lines up with the books, here's a handy article and chart


Post a Comment

Sunday, April 06, 2014

The people at Final Draft were kind enough to send me a review copy of Final Draft 9, their snappy new edition of the software.

I've been using it on my current show; I'm not a big fan of Screenwriter's not-very-intuitive interface. I haven't run across any really dandy new features, except that Script Notes are now organized. I'm sure there must be other features; I was going to look them up next week.

However, now I've got a more basic problem. After, originally, activating the software with no problem, FD9 has now decided to deactivate itself. No problem, I put my customer number back in.

Nope, this time, it won't activate. I get a buggy error message:

No problem. I call up the activation hotline. I get a message saying FD9 can only be activated online. And here's where it gets serious:

The activation people only work Monday-Friday, during Pacific Coast work hours.

Uh, what?

Y'all do know that screenwriters work on weekends? And nights?

Are you effing kidding me?

In this era of 24-7 Bangalore help centers, it is really inexcusable to have a help desk that only works 40 hours a week, Pacific Standard Time.

They really, really need to fix this.

Oh, well. Back to FD8.

(Yeah, yeah, DMc. I know.)

UPDATE:  Final Draft 9 will also not update itself unless it thinks it's been activated. That's just dumb. Doesn't matter though; even if I update from outside the program, it still won't activate.

UPDATE #2:  Called the Activation Hotline. Something's wrong with that. It's the usual "press one for Final Draft 6 through 8..." except it doesn't wait for you to press a button before telling you "I didn't get that" repeatedly.

UPDATE #3:  This post solves the activation problem.


Post a Comment

Tuesday, April 01, 2014

According to FiveThirtyEight, the domestic Return on Investment of movies that pass the Bechdel Test is $1.37; for movies in which the women never get to talk to each other it's $1.22; movies that don't even have two named women, it's $1.00.
Since Hollywood believes that international markets don’t want to see women in film, we also broke down the median return on investment for films based on domestic (U.S. and Canada) and international box office numbers. We found that Bechdel-passing films still have comparable returns on investment when the movies “travel."

In other words, treating women characters as if they were human beings makes you money.


Post a Comment

This page is powered by Blogger.