In the wake of rumors that the Halo movie will be pushed back from its rumored 2007 release date due to its rumored lack of a director and rumored delay of the rumored principal photography that was rumored to have taken place somewhere in New Zealand about now, but allegedly hasn't, several readers suggested I write something on how I thought the Halo movie ought to be done.
To a certain extent, to do so is a little unfair and perhaps counterproductive. Any idea for the film, if expressed in enough detail, would be indistinguishable from an unsolicited script thrown into a studio slush pile. Either it'll just be ignored (as most probably deserve to be) or it would be read. Having been read, if any ideas actually got into the movie, it could form the basis for complaints on the part of the author that the studio used them without compensation.
Or, worse still, a random coincidence between any idea in such a script and the film itself might be used as a basis for such a complaint. So, in a way, writing too much about cool things you'd like to see in the movie almost guarantees those things won't be, especially if it's something new and unique and interesting, rather than just something you've already seen in the games or read in the books.
Besides, the only fair way to do that would be to pen a complete script; and if I was capable of writing a good Halo movie script that would be a critical and commercial success I think there'd have been more of an indication of it before now.
However, what I will do is take some cues from the games, the books, the rumored script by Alex Garland, which I have previously spent time dissecting, and do something that's not allowed at the Movie Cynics Database at HBO. I'll write a simple list of things I think the Halo movie Should or Should Not do and explain why.
Click "read more" from the front page for the entire article.
Recent comments