Search
Search results
Mothergamer (1511 KP) rated the PlayStation 3 version of Assassin's Creed III in Video Games
Apr 3, 2019
Contains spoilers, click to show
So after a long hiatus, I finished Assassin's Creed III. Did I like the game? Yes, definitely. Did I love it? Not so much. First let's get the good things out of the way. I really liked that there was a new world to explore and a great part of history to be involved in; the Revolutionary War. This made for a lot of interesting missions, side quests, and battles. I did like the new costume designs for the game and I definitely liked the new weapons. I did like seeing quite a few historical faces in the game and some of them had some pretty good missions. The story was fairly interesting especially towards the end when further details are revealed answering a lot of questions from the previous game. While I did wish for more city exploration, I did enjoy exploring the frontier areas because it was new and there was some interesting things going on out there.
Now, let us get to the parts that I found mildly disappointing and the parts that were so infuriating they got A LOT of swearing from me.
1.Connor Is A Wooden Boy: Connor while an interesting character, came across as wooden and I wasn't really feeling the passion from him or any emotion really. Even when he was supposed to be angry, it just came across as angst filled teenager. Shouldn't he be angrier about some of the things that have happened? I mean I know I would be full on raging if half the stuff he survives in this game happened to me. Speaking in a flat monotone in every situation is just not working for me. I also wish they had done a bit more with the story about Connor's tribe because it seemed like they were just a blip of a plot point and not much else which was a little disappointing. There's also this sense of Connor just being along for the ride and even as a full fledged assassin he doesn't really get to shine, so his story seems lost and smacks of missed opportunity. Bottom line, the pacing is off and that's never good when your main character doesn't feel like he's the main character to you.
2. The damned lock picking: Really, how hard is it to have decent controls for lock picking the chests you find in the game? I suggest that all those game developers go play all the Thief games so they can see how it's done. There is no excuse that late in the game for shoddy controls. Hold both buttons down, swirl around to find the correct "signal" and realize that you have the skills of a drunken monkey when you can't get the damn thing open. Also file under "the right signal my effing ass" because it was ridiculous.
3. Paul Revere's Midnight Ride Mission: Yes, they did their research and yes, it was cool they had that in the game. However, never have I wanted so badly to shove a historical person off a horse. Having to constantly ask the man for directions while he yelled at me, "More to the left! No, more right!" made me seriously consider handing him over to the enemy. It was only for a minute, I swear.
4. THE DAMN NAVAL BATTLES: There is a good reason why that is in all caps. There is no real learning curve here. It's pretty much a learn or sink your ship situation here. While I get that the ships can't turn on a dime just like real ships from that era; the controls are pardon my French, utter shit. Not only are they clunky, there are some questionable load times for firing the various cannons and lord help you if you end up getting turned around and smashing on some rocks. One of the naval battles was so damn infuriating, my husband Ron had to step in and finish it for me. Yes, it was that bad.
5. The Chasing Lee Mission: This was the final mission in Connor's main story and it made me want to tear my hair out and scream out my frustration. I did scream in fact. Many times. First there's the optional objectives of don't shove anyone while you're running, followed by don't let any of the British soldiers touch you. So instead of oh I don't know getting to shoot murdering bad guy in the face, you have to run an obstacle course full of people, things, and a burning ship like you're an Olympic marathon champ. Then we factor in, how Lee is only five steps away from you but you get the desynchronization message if you don't get closer to him. At one point I was standing right IN FRONT of him in the burning ship; I could have had him right there, but because it wasn't part of the "story" he took off running and I got that message. I finally did finish that mission and the payoff for it wasn't really worth it; trust me.
6. Desmond Got Screwed Over: While I understand that Desmond's story was ending; the way they sent him off left no real resolution for him and it seemed as if they were just tired of him. Desmond needed a proper send off with some actual closure; not an ending that screamed, 'Hey, we're kind of bored and tired of this guy, so we're getting rid of him okay? 'Kay, see ya!'
Those were the big things that really disappointed me and made me nuts. My thinking was I couldn't believe they spent three years working on this game and this is what we got. I loved the previous Assassin's Creed games and I was genuinely excited for this one, but there were many things that disappointed me. While I liked the game and I did like the ending (not the thing that happened to Desmond because that was some bullshit), I didn't love it. It felt like perhaps they rushed a bit or just didn't test things out fully to make sure they worked right (I'm looking at you, lock picking controls team) or they couldn't be bothered. I'm not expecting perfection, but after working on something for three years, you better be able to deliver the goods. This is just my take on it, if you want to try it out by all means, go ahead. Just don't expect stellar, because that is not going to happen. Expect kind of good, but not great, and fun to play through once.
Now, let us get to the parts that I found mildly disappointing and the parts that were so infuriating they got A LOT of swearing from me.
1.Connor Is A Wooden Boy: Connor while an interesting character, came across as wooden and I wasn't really feeling the passion from him or any emotion really. Even when he was supposed to be angry, it just came across as angst filled teenager. Shouldn't he be angrier about some of the things that have happened? I mean I know I would be full on raging if half the stuff he survives in this game happened to me. Speaking in a flat monotone in every situation is just not working for me. I also wish they had done a bit more with the story about Connor's tribe because it seemed like they were just a blip of a plot point and not much else which was a little disappointing. There's also this sense of Connor just being along for the ride and even as a full fledged assassin he doesn't really get to shine, so his story seems lost and smacks of missed opportunity. Bottom line, the pacing is off and that's never good when your main character doesn't feel like he's the main character to you.
2. The damned lock picking: Really, how hard is it to have decent controls for lock picking the chests you find in the game? I suggest that all those game developers go play all the Thief games so they can see how it's done. There is no excuse that late in the game for shoddy controls. Hold both buttons down, swirl around to find the correct "signal" and realize that you have the skills of a drunken monkey when you can't get the damn thing open. Also file under "the right signal my effing ass" because it was ridiculous.
3. Paul Revere's Midnight Ride Mission: Yes, they did their research and yes, it was cool they had that in the game. However, never have I wanted so badly to shove a historical person off a horse. Having to constantly ask the man for directions while he yelled at me, "More to the left! No, more right!" made me seriously consider handing him over to the enemy. It was only for a minute, I swear.
4. THE DAMN NAVAL BATTLES: There is a good reason why that is in all caps. There is no real learning curve here. It's pretty much a learn or sink your ship situation here. While I get that the ships can't turn on a dime just like real ships from that era; the controls are pardon my French, utter shit. Not only are they clunky, there are some questionable load times for firing the various cannons and lord help you if you end up getting turned around and smashing on some rocks. One of the naval battles was so damn infuriating, my husband Ron had to step in and finish it for me. Yes, it was that bad.
5. The Chasing Lee Mission: This was the final mission in Connor's main story and it made me want to tear my hair out and scream out my frustration. I did scream in fact. Many times. First there's the optional objectives of don't shove anyone while you're running, followed by don't let any of the British soldiers touch you. So instead of oh I don't know getting to shoot murdering bad guy in the face, you have to run an obstacle course full of people, things, and a burning ship like you're an Olympic marathon champ. Then we factor in, how Lee is only five steps away from you but you get the desynchronization message if you don't get closer to him. At one point I was standing right IN FRONT of him in the burning ship; I could have had him right there, but because it wasn't part of the "story" he took off running and I got that message. I finally did finish that mission and the payoff for it wasn't really worth it; trust me.
6. Desmond Got Screwed Over: While I understand that Desmond's story was ending; the way they sent him off left no real resolution for him and it seemed as if they were just tired of him. Desmond needed a proper send off with some actual closure; not an ending that screamed, 'Hey, we're kind of bored and tired of this guy, so we're getting rid of him okay? 'Kay, see ya!'
Those were the big things that really disappointed me and made me nuts. My thinking was I couldn't believe they spent three years working on this game and this is what we got. I loved the previous Assassin's Creed games and I was genuinely excited for this one, but there were many things that disappointed me. While I liked the game and I did like the ending (not the thing that happened to Desmond because that was some bullshit), I didn't love it. It felt like perhaps they rushed a bit or just didn't test things out fully to make sure they worked right (I'm looking at you, lock picking controls team) or they couldn't be bothered. I'm not expecting perfection, but after working on something for three years, you better be able to deliver the goods. This is just my take on it, if you want to try it out by all means, go ahead. Just don't expect stellar, because that is not going to happen. Expect kind of good, but not great, and fun to play through once.
Zuky the BookBum (15 KP) rated Nightmares: A New Decade of Modern Horror in Books
Mar 15, 2018
Also read my review here: http://bookbum.weebly.com/book-reviews/nightmares-a-new-decade-of-modern-horror-by-various-authors
NOW AVAILABLE IN THE UK!
I decided that instead of rating this book overall, it would be better to rate each individual story, so that’s what I’ve done. Obviously I had to rate the overall book so I actually calculated the average of all the ratings lol.
<b><u>Shallaballah</b></u> by Mark Samuels
<i>1 star</i>
Not a good start to the book for me. I was over the stitched up face appearance, creepy hospital, shady operations kind of horror story long ago, so this did pretty much nothing for me. Yes there were creepy elements to it but not enough. I also get what it was trying to do with the whole vanity, television thing, but it didn’t really work and so for me, added nothing to the overall plot.
<b><u>Sob in the Silence</b></u> by Gene Wolfe
<i>3 stars</i>
This was a pretty good creepy story, I much prefer stories that don't really have any paranormal elements to them and are more about the madness of the human brain. This short story had a bit of both to it so it was much preferable to the last! Didn't like the weird abrupt ending though, it felt like the story had been cut short.
<b><u>Our Turn Too Will One Day Come</b></u> by Brian Hodge
<i>4 stars</i>
This definitely had my skin crawling a bit. I love this kind of horror story that incorporates creatures and family secrets, kind of gave me The Village vibes… Is that the name of that film? Anyway, yes, great short!
<b><u>Dead Sea Fruit</b></u> by Kaaron Warren
<i>3 stars</i>
This short was pretty good, the Ash Mouth Man was pretty freaky but the writing was a bit all over the place and I felt too much was squeezed into such a small story. I'd love to read a full length story about this Ash Man, that would definitely be disturbing to read!
<b><u>Closet Dreams</b></u> by Lisa Tuttle
<i>4 stars</i>
Really well written and completely terrifying! I hate abduction stories so much because it could happen to anyone. It's not like the demonic ghost stories that you choose to believe or not believe, men who rape and steal little girls are <b>real.</b> The ending was… Predictable… Done before… Boring… But the rest of it was good enough to warrant it 4 stars!
<b><u>Spectral Evidence</b></u> by Gemma Files
<i>1 star</i>
?????????????????????????????????????????????????????????????????
I didn’t like the way this was set out, very frustrating to read on a Kindle! Also, I didn’t really get it, it was so all over the place I forgot what was happening previously.
<b><u>Hushabye</b></u> by Simon Bestwick
<i>2 stars.</i>
I wanted to like this one but there was too much missing from the story, maybe it was meant to be mysterious but in my eyes it just felt unfinished. Like what was the man sucking out of the children? And what really happened to Hardiman? Also I thought the narrator was a woman until we finally learnt his name was Paul, don’t know why, I just imagined him that way.
<b><u>Very Low-Flying Aircraft</b></u> by Nicholas Royle
<i>3 stars</i>
I’m not really a big fan of war based novels / stories so from the get go I knew I wasn’t going to get on that well with this story but it wasn’t so bad. I didn’t feel like this story explained itself enough or maybe it did and I just didn’t get it? Like why did it matter that Frankie looked like Victoria and why did Flynn go to the clinic? Also, I didn’t think it of a horror story really, though it was scary and horrible, it didn’t give me the heeby-jeebys like some of the others have done.
<b><u>The Goosle</b></u> by Margo Lanagan
<i>2 stars</i>
Seriously, seriously grotesque. If you have a weak stomach, <i>avoid this.</i> A very peculiar branch off the traditional Hansel and Gretel story we all know. This isn’t my kind of horror at all. I much prefer scary, mysterious human crime and occasionally a paranormal story. Torture porn is not at all my thing. This was very well written though, so props to Lanagan for that.
<b><u>The Clay Party</b></u> by Steve Duffy
<i>4 stars</i>
Again, not exactly what I’d classify as a horror story, but a great read nonetheless. Excellently written and enjoyable the whole way through, up until the end… the ending definitely wasn’t my kind of style so that was disappointing for me personally, but I’m sure others would love it!
<b><u>Strappado</b></u> by Laird Barron
<i>3 stars</i>
Definitely one of the strangest of the shorts in this novel. I thought it was excellently written but I didn’t quite get it? Maybe I was just having an off day when I read this but it didn’t really do anything for me.
<b><u>Lonegan’s Luck</b></u> by Stephen Graham Jones
<i>4 stars</i>
This is one of those stories I don’t know why I like. I never used to be into these kinds of rural town, religious apocalyptic kind of books, but ever since reading Mammoth, I’ve begun to enjoy reading them. Admittedly this had me a little confused to begin with, there were what felt like a lot of characters, but in the end none of the mattered anyway, they were just there to set the scene.
<b><u>Mr Pigsny</b></u> by Reggie Oliver
<i>3 stars</i>
I feel like I’ve read this book a million times. It’s one of those stories that's been redone time and time again with just slight changes here and there. It isn’t a bad plot per say, I certainly enjoyed it, it just had nothing unique about it.
<b><u>At Night, When the Demons Come by</b></u> by Ray Cluley
<i>4 stars</i>
One of the longer stories in this book but also one of the best. It had a pleasing twist to it and some interesting characters. I guess I quite like the whole apocalyptic feel when it comes to stories. I personally don’t feel this one was a horror story, more like a fantasy thriller.
<b><u>Was She Wicked? Was She Good?</b></u> by Mary Rickert
<i>4 stars</i>
This was a sad horror story, but in a way, it was also quite beautiful. I really liked the plot, it was something quite different to all the others in this collection and I thought the way it was written flowed well. Enjoyable short story!
<b><u>The Shallows</b></u> by John Langan
<i>2 stars</i>
I liked how this was written but I didn’t get it? I got bored halfway through it too, it was a half an hour read and I just couldn’t understand it so I skimmed the last 10 minutes or so. Yawn.
<b><u>Little Pig</b></u> by Anna Taborska
<i>3 stars</i>
Meh. This was well written and very different to the rest of the stories in this collection but was it a horror story? No. It was tragic, but not scary. Disappointing because whenever I see the word “pig” in relation to something “scary” I think of AHS.
<b><u>Omphalos</b></u> by Livia Llewellyn
<i>3 stars</i>
<b>TRIGGER WARNING: SEXUAL ABUSE</b>
This story was definitely very unique to the rest of the stories in this collection in the terms that this was a horror story that focused more on the real life horrors of families rather than made up monsters and ghouls. This story isn’t for the faint-hearted, it was horrific and gruesome and very upsetting. It wasn’t the best story in the collection when it came to plot or writing style, but it did bring out strong emotions in me, which other stories have been unable to do.
<b><u>How We Escaped Our Certain Fate</b></u> by Dan Chaon
<i>5 stars</i>
I liked how this was a different take on a classic zombie story - <b><i>”It wasn’t the end of the world… of course, a bite would infect you, but they weren’t terribly aggressive, in general.”</b></i> This was by far my favourite story in the entire book, it was so sad and emotional. It was beautiful.
<b><u>That Tiny Flutter of the Heart I Used to Call Love</b></u> by Robert Shearman
<i>4 stars</i>
Creepy, creepy, creepy. Dolls terrify me thanks to modern horror, although, really, I’ve always felt unsettled by them. Enjoyable story though. Poor Julian.
(This story almost had my name in it! “Suki” is close enough to Zuky.)
<b><u>Interstate Love Song (Murder Ballad No.8)</b></u> by Caitlin R. Kiernan
<i>3 stars</i>
Hmm, why did the shorts at the end of this book get all meaningful and loved up? I think that kinda ruined this for me. Granted it was disturbed and pretty grotesque at times but sadness of the ending ruined that creepy effect of the book and just left this kind of hanging in the space between horror and tragedy.
<b><u>Shay Corsham Worsted</b></u> by Garth Nix
<i>4 stars</i>
This was an interesting story and I liked our harsh but caring main character, Sir David. I wish this story was a little longer so we could find out more about Shay because I feel the missing backstory left this plot wide open. Enjoyable nonetheless.
<b><u>The Atlas of Hell</b></u> by Nathan Ballingrud
<i>3 stars</i>
I really enjoyed this to begin with though I thought it had a little David Wong influence, a writing style I’m not into. All was going well for this story until I got towards the end of it, where it completely lost me. Whether this is down to the annoying man sat on the train next to me, speaking into his phone at 32596 decibels, or just because the plot went AWOL, we’ll never know.
<b><u>Ambitious Boys Like You</b></u> by Richard Kadrey
<i>4 stars</i>
I like these kinds of creepy stories! They’re not particularly unique anymore, because they’ve been done so many different times in so many different, but similar ways, but they’re still fun to read. The old man was especially disturbing just because he was so witty and chilled out. I liked that this story had elements of humour to it, it made a nice change to the more recent emotion filled stories.
I’d like to thank Netgalley and Tachyon Publications for giving me the opportunity to read this in an exchange for an honest review.
NOW AVAILABLE IN THE UK!
I decided that instead of rating this book overall, it would be better to rate each individual story, so that’s what I’ve done. Obviously I had to rate the overall book so I actually calculated the average of all the ratings lol.
<b><u>Shallaballah</b></u> by Mark Samuels
<i>1 star</i>
Not a good start to the book for me. I was over the stitched up face appearance, creepy hospital, shady operations kind of horror story long ago, so this did pretty much nothing for me. Yes there were creepy elements to it but not enough. I also get what it was trying to do with the whole vanity, television thing, but it didn’t really work and so for me, added nothing to the overall plot.
<b><u>Sob in the Silence</b></u> by Gene Wolfe
<i>3 stars</i>
This was a pretty good creepy story, I much prefer stories that don't really have any paranormal elements to them and are more about the madness of the human brain. This short story had a bit of both to it so it was much preferable to the last! Didn't like the weird abrupt ending though, it felt like the story had been cut short.
<b><u>Our Turn Too Will One Day Come</b></u> by Brian Hodge
<i>4 stars</i>
This definitely had my skin crawling a bit. I love this kind of horror story that incorporates creatures and family secrets, kind of gave me The Village vibes… Is that the name of that film? Anyway, yes, great short!
<b><u>Dead Sea Fruit</b></u> by Kaaron Warren
<i>3 stars</i>
This short was pretty good, the Ash Mouth Man was pretty freaky but the writing was a bit all over the place and I felt too much was squeezed into such a small story. I'd love to read a full length story about this Ash Man, that would definitely be disturbing to read!
<b><u>Closet Dreams</b></u> by Lisa Tuttle
<i>4 stars</i>
Really well written and completely terrifying! I hate abduction stories so much because it could happen to anyone. It's not like the demonic ghost stories that you choose to believe or not believe, men who rape and steal little girls are <b>real.</b> The ending was… Predictable… Done before… Boring… But the rest of it was good enough to warrant it 4 stars!
<b><u>Spectral Evidence</b></u> by Gemma Files
<i>1 star</i>
?????????????????????????????????????????????????????????????????
I didn’t like the way this was set out, very frustrating to read on a Kindle! Also, I didn’t really get it, it was so all over the place I forgot what was happening previously.
<b><u>Hushabye</b></u> by Simon Bestwick
<i>2 stars.</i>
I wanted to like this one but there was too much missing from the story, maybe it was meant to be mysterious but in my eyes it just felt unfinished. Like what was the man sucking out of the children? And what really happened to Hardiman? Also I thought the narrator was a woman until we finally learnt his name was Paul, don’t know why, I just imagined him that way.
<b><u>Very Low-Flying Aircraft</b></u> by Nicholas Royle
<i>3 stars</i>
I’m not really a big fan of war based novels / stories so from the get go I knew I wasn’t going to get on that well with this story but it wasn’t so bad. I didn’t feel like this story explained itself enough or maybe it did and I just didn’t get it? Like why did it matter that Frankie looked like Victoria and why did Flynn go to the clinic? Also, I didn’t think it of a horror story really, though it was scary and horrible, it didn’t give me the heeby-jeebys like some of the others have done.
<b><u>The Goosle</b></u> by Margo Lanagan
<i>2 stars</i>
Seriously, seriously grotesque. If you have a weak stomach, <i>avoid this.</i> A very peculiar branch off the traditional Hansel and Gretel story we all know. This isn’t my kind of horror at all. I much prefer scary, mysterious human crime and occasionally a paranormal story. Torture porn is not at all my thing. This was very well written though, so props to Lanagan for that.
<b><u>The Clay Party</b></u> by Steve Duffy
<i>4 stars</i>
Again, not exactly what I’d classify as a horror story, but a great read nonetheless. Excellently written and enjoyable the whole way through, up until the end… the ending definitely wasn’t my kind of style so that was disappointing for me personally, but I’m sure others would love it!
<b><u>Strappado</b></u> by Laird Barron
<i>3 stars</i>
Definitely one of the strangest of the shorts in this novel. I thought it was excellently written but I didn’t quite get it? Maybe I was just having an off day when I read this but it didn’t really do anything for me.
<b><u>Lonegan’s Luck</b></u> by Stephen Graham Jones
<i>4 stars</i>
This is one of those stories I don’t know why I like. I never used to be into these kinds of rural town, religious apocalyptic kind of books, but ever since reading Mammoth, I’ve begun to enjoy reading them. Admittedly this had me a little confused to begin with, there were what felt like a lot of characters, but in the end none of the mattered anyway, they were just there to set the scene.
<b><u>Mr Pigsny</b></u> by Reggie Oliver
<i>3 stars</i>
I feel like I’ve read this book a million times. It’s one of those stories that's been redone time and time again with just slight changes here and there. It isn’t a bad plot per say, I certainly enjoyed it, it just had nothing unique about it.
<b><u>At Night, When the Demons Come by</b></u> by Ray Cluley
<i>4 stars</i>
One of the longer stories in this book but also one of the best. It had a pleasing twist to it and some interesting characters. I guess I quite like the whole apocalyptic feel when it comes to stories. I personally don’t feel this one was a horror story, more like a fantasy thriller.
<b><u>Was She Wicked? Was She Good?</b></u> by Mary Rickert
<i>4 stars</i>
This was a sad horror story, but in a way, it was also quite beautiful. I really liked the plot, it was something quite different to all the others in this collection and I thought the way it was written flowed well. Enjoyable short story!
<b><u>The Shallows</b></u> by John Langan
<i>2 stars</i>
I liked how this was written but I didn’t get it? I got bored halfway through it too, it was a half an hour read and I just couldn’t understand it so I skimmed the last 10 minutes or so. Yawn.
<b><u>Little Pig</b></u> by Anna Taborska
<i>3 stars</i>
Meh. This was well written and very different to the rest of the stories in this collection but was it a horror story? No. It was tragic, but not scary. Disappointing because whenever I see the word “pig” in relation to something “scary” I think of AHS.
<b><u>Omphalos</b></u> by Livia Llewellyn
<i>3 stars</i>
<b>TRIGGER WARNING: SEXUAL ABUSE</b>
This story was definitely very unique to the rest of the stories in this collection in the terms that this was a horror story that focused more on the real life horrors of families rather than made up monsters and ghouls. This story isn’t for the faint-hearted, it was horrific and gruesome and very upsetting. It wasn’t the best story in the collection when it came to plot or writing style, but it did bring out strong emotions in me, which other stories have been unable to do.
<b><u>How We Escaped Our Certain Fate</b></u> by Dan Chaon
<i>5 stars</i>
I liked how this was a different take on a classic zombie story - <b><i>”It wasn’t the end of the world… of course, a bite would infect you, but they weren’t terribly aggressive, in general.”</b></i> This was by far my favourite story in the entire book, it was so sad and emotional. It was beautiful.
<b><u>That Tiny Flutter of the Heart I Used to Call Love</b></u> by Robert Shearman
<i>4 stars</i>
Creepy, creepy, creepy. Dolls terrify me thanks to modern horror, although, really, I’ve always felt unsettled by them. Enjoyable story though. Poor Julian.
(This story almost had my name in it! “Suki” is close enough to Zuky.)
<b><u>Interstate Love Song (Murder Ballad No.8)</b></u> by Caitlin R. Kiernan
<i>3 stars</i>
Hmm, why did the shorts at the end of this book get all meaningful and loved up? I think that kinda ruined this for me. Granted it was disturbed and pretty grotesque at times but sadness of the ending ruined that creepy effect of the book and just left this kind of hanging in the space between horror and tragedy.
<b><u>Shay Corsham Worsted</b></u> by Garth Nix
<i>4 stars</i>
This was an interesting story and I liked our harsh but caring main character, Sir David. I wish this story was a little longer so we could find out more about Shay because I feel the missing backstory left this plot wide open. Enjoyable nonetheless.
<b><u>The Atlas of Hell</b></u> by Nathan Ballingrud
<i>3 stars</i>
I really enjoyed this to begin with though I thought it had a little David Wong influence, a writing style I’m not into. All was going well for this story until I got towards the end of it, where it completely lost me. Whether this is down to the annoying man sat on the train next to me, speaking into his phone at 32596 decibels, or just because the plot went AWOL, we’ll never know.
<b><u>Ambitious Boys Like You</b></u> by Richard Kadrey
<i>4 stars</i>
I like these kinds of creepy stories! They’re not particularly unique anymore, because they’ve been done so many different times in so many different, but similar ways, but they’re still fun to read. The old man was especially disturbing just because he was so witty and chilled out. I liked that this story had elements of humour to it, it made a nice change to the more recent emotion filled stories.
I’d like to thank Netgalley and Tachyon Publications for giving me the opportunity to read this in an exchange for an honest review.
5 Minute Movie Guy (379 KP) rated Godzilla (2014) in Movies
Jun 26, 2019
Godzilla's gigantic scale is impressive. (1 more)
Bryan Cranston gives a terrific performance.
Aaron Taylor-Johnson is a horribly lifeless protagonist. (2 more)
The film repeatedly obscures our chances to see Godzilla or cuts away from him completely.
There seems to be very little sense of panic or concern despite Godzilla and MUTO's destruction.
As promising as this new Godzilla movie may appear to be, it falls far short of expectations, and dare I say, it isn’t even much better than the 1998 version.
This year marks the 60th anniversary of the original Godzilla film, when the King of the Monsters first emerged from the Pacific and terrorized Tokyo, Japan. Roughly 10 years after America dropped two atomic bombs on Japan to end World War II, Godzilla was artistically created to be a physical, living representation of the destructive force of those bombs. Even the texture of his skin is modelled after keloid scars, which were found on survivors as a result of the radiation. Godzilla’s arrival and subsequent attacks were spurred by the use of nuclear weapons, and he as a character wholly embodies the consequences of nuclear warfare.
60 years later, Godzilla remains a global icon, having spawned dozens of movie sequels, while introducing several other enormous monsters to battle with. Then 16 years ago, he was reimagined as he first came to America in Roland Emmerich’s lackluster 1998 film Godzilla, leaving many fans severely disappointed with not only the film, but also the new rendition of the famous monster. While Godzilla is visually depicted much more accurately in Gareth Edward’s new 2014 Godzilla than he was in ’98, his entire presence is surprisingly different than usual. This isn’t the angry, vengeful Godzilla of the past. He actually now seems almost entirely indifferent to humans. Unfortunately, as promising as this new Godzilla movie may appear to be, it falls far short of expectations, and dare I say, it isn’t even much better than the 1998 Godzilla.
Godzilla (2014) starts off pretty well, strengthened by the performance of Bryan Cranston, who plays Joe Brody, a nuclear power plant engineer living in Japan. Brody is present when an unknown disaster occurs at the plant, costing many innocent lives. Despite what the trailers suggest, Cranston’s Brody is not the main character of the film. Nor is it fellow all-star actor Ken Watanabe. The main character is actually only seen for about 4 seconds of the film’s original 2 and a half minute trailer. It’s Joe Brody’s son, Ford, played by Aaron Taylor-Johnson, in a performance that is decent but far from engaging. The protagonist Ford Brody is a character that is largely uninteresting, and who just casually wants to get back to his family after the monster invasion. He fails to convey any genuine sense of urgency amidst the chaos, although the same can be said for the entire cast, with the exception of Cranston’s Brody. Cranston’s performance is the only one that has any emotional weight to it, but he can’t carry the film alone. Meanwhile, Ken Watanabe is essentially reduced to being the quiet, ever-present voice of reason that no one wants to listen to. The film has a solid cast of actors, but they’re not given enough to work with in this convoluted mess of a movie.
For a movie that has so much death and destruction, the people in the film never seem all that concerned. You get no sense of global panic and hysteria. You have a 300-foot-tall monster destroying cities, with millions of people dying, and yet nobody seems all that freaked out by it. It’s almost like the situation isn’t treated as a serious threat, and there’s a major lack of suspense altogether. There’s rarely any edge-of-your-seat terror or excitement, and the lack of emotion just makes the action come off as sort of flat and dull. Not only that, the majority of the destruction that’s taking place isn’t even seen, with the movie instead opting to show you the aftermath. Throughout the first two-thirds of the movie, the camera continuously cuts away from the action you’ve been waiting for. Rather than showing you what you want to see in full-glory, the movie frequently will take you to a different location where you’ll briefly see a few seconds of the catastrophe being watched by someone on television. It feels like a cheap trick to build up to some amazing climax, but it’s incredibly frustrating. It’s like when watching a reality TV show and then the show cuts to a commercial break before revealing the winner. Perhaps it would be more forgivable if the end was enjoyable, but even though it does give you a full display of the showdown, it’s bogged down by a tiresome human story and still lacks any real emotional punch. Despite the fact that the movie tries to convey a serious tone, it’s also incredibly cheesy. To the extent that the big finale that this movie has been trying so hard to build up to ends up being almost laughable. Ultimately the movie ends up just being unsatisfying, disappointing, and overly long.
There are a lot of ways in which Godzilla goes wrong, despite the film’s great potential. One of my issues is with the musical score, which ends up coming off like a bad punchline. Music is supposed to accentuate the action and drama of a film, yet the film feels emotionless and boring. The only time the music really stood out to me was when it was being used to heighten the suspense of the climactic battle, and essentially narrate who was winning. It was done so ineffectively that it was both kind of comical and embarrassing. I also have an issue with all of the special effects, which are being touted as absolutely amazing. They’re not. However, I will say that the use of special effects in the movie is quite ambitious, but it works to the film’s detriment. There’s simply too much of them, and this excessive nature of the film is, I think, its biggest mistake. Godzilla (2014) is ridiculously CGI-heavy, and while their scope is admirable, I really think the quality would have been substantially improved if they didn’t overdo it so much. I think a less-is-more approach would have benefited the film in many ways. It’s excessive to the point of making good things turn bad. Everything is way too over the top, causing the action to lose its impact. It’s evident the filmmakers were trying so hard to make this big-budget movie as epic as possible, but this enormous scale ends up backfiring. The rampage covers two continents, multiple cities, and even traverses the length of the Pacific Ocean. I can appreciate their attempt, but the movie is trying to do too much. In other words, Godzilla (2014) bites off more than it can chew.
I also have some problems with the film’s treatment of the titular character, Godzilla. First of all, for a movie named after him, he sure doesn’t appear much in it. He’s the reason why we want to see the movie, but he’s absent for the majority of the film. Even when he’s around, he’s largely obscured by CGI smoke and storm clouds, up until the final moments of the movie. I’m also not particularly fond of his appearance. He just doesn’t quite look like Godzilla to me. It’s like looking at a T-Rex head on Godzilla’s body. I’m aware that Godzilla’s facial appearance has changed many times over 60 years, but something just doesn’t look quite right here. Additionally, I feel that Godzilla’s face is actually too expressive in this new film. I wonder if this was done to cause viewers to feel more sympathetic to him, because in the film, Godzilla is actually depicted as something of a tragic hero, rather than a colossal beast. This is my biggest concern with the movie’s handling of his character. Godzilla’s destruction in the film is treated like it’s all unintentional, and just a result of his massive size. Even though humans attack him, he’s not angry about it or anything. Never mind the movie’s claim that all of America’s nuclear bomb tests after Hiroshima and Nagasaki were actually secretive but unsuccessful attempts to kill Godzilla. He doesn’t mind. He’s just a poor gentle giant that’s misunderstood. Really, Hollywood? Give me a break!
To say that Godzilla (2014) is almost as bad of a film as Godzilla (1998) is a statement that I don’t take lightly. It’s a bold and controversial thing to say, and it may seem a bit absurd considering that this film goes in the right direction, whereas the previous film was all wrong from the beginning. Yet while the new movie has all the right pieces for greatness, it extends its reach too far and attempts to do too much, while never managing to make any of it very good. In all seriousness, I was more entertained with the ’98 film than I was with this one. I can hardly comprehend how a movie with a giant 300-foot-tall monster destroying cities can be so boring. Godzilla (2014) focuses so much on trying to build up to an epic conclusion that it forgets to worry about making the audience care, or even about keeping them entertained, and it just gets worse as it goes on. It repeatedly tries to raise the stakes, as well as our expectations, while attempting to delay gratification until the end. It’s a risky move, and unsurprisingly, it certainly doesn’t pay off. On the bright side, Godzilla (2014) is probably a pretty sweet movie if you’re a 12-year-old. There’s plenty of action, some cool special effects, and he’s still a pretty awesome monster. However, for me, I was totally pumped up for this movie, but an hour and a half into it, I had endured enough and wanted to walk out. Godzilla (2014) disappointed me on so many levels. It’s a movie without a beating heart. It’s predictable, overly long, has uninspired characters and a weak story, and the action just never hits the right note. A little more emotion and a little less CGI could have a gone a long way in making this movie better. As a fan of Godzilla, I felt frustrated, detached, and perplexed with how they were able to do so much wrong when they had the groundwork for something great. You know, perhaps I’m wrong in claiming it’s comparably bad as Godzilla (1998). After all, the last time I saw that movie was in the theaters when I was 12.
(This review was originally posted at 5mmg.com on 5.17.14.)
60 years later, Godzilla remains a global icon, having spawned dozens of movie sequels, while introducing several other enormous monsters to battle with. Then 16 years ago, he was reimagined as he first came to America in Roland Emmerich’s lackluster 1998 film Godzilla, leaving many fans severely disappointed with not only the film, but also the new rendition of the famous monster. While Godzilla is visually depicted much more accurately in Gareth Edward’s new 2014 Godzilla than he was in ’98, his entire presence is surprisingly different than usual. This isn’t the angry, vengeful Godzilla of the past. He actually now seems almost entirely indifferent to humans. Unfortunately, as promising as this new Godzilla movie may appear to be, it falls far short of expectations, and dare I say, it isn’t even much better than the 1998 Godzilla.
Godzilla (2014) starts off pretty well, strengthened by the performance of Bryan Cranston, who plays Joe Brody, a nuclear power plant engineer living in Japan. Brody is present when an unknown disaster occurs at the plant, costing many innocent lives. Despite what the trailers suggest, Cranston’s Brody is not the main character of the film. Nor is it fellow all-star actor Ken Watanabe. The main character is actually only seen for about 4 seconds of the film’s original 2 and a half minute trailer. It’s Joe Brody’s son, Ford, played by Aaron Taylor-Johnson, in a performance that is decent but far from engaging. The protagonist Ford Brody is a character that is largely uninteresting, and who just casually wants to get back to his family after the monster invasion. He fails to convey any genuine sense of urgency amidst the chaos, although the same can be said for the entire cast, with the exception of Cranston’s Brody. Cranston’s performance is the only one that has any emotional weight to it, but he can’t carry the film alone. Meanwhile, Ken Watanabe is essentially reduced to being the quiet, ever-present voice of reason that no one wants to listen to. The film has a solid cast of actors, but they’re not given enough to work with in this convoluted mess of a movie.
For a movie that has so much death and destruction, the people in the film never seem all that concerned. You get no sense of global panic and hysteria. You have a 300-foot-tall monster destroying cities, with millions of people dying, and yet nobody seems all that freaked out by it. It’s almost like the situation isn’t treated as a serious threat, and there’s a major lack of suspense altogether. There’s rarely any edge-of-your-seat terror or excitement, and the lack of emotion just makes the action come off as sort of flat and dull. Not only that, the majority of the destruction that’s taking place isn’t even seen, with the movie instead opting to show you the aftermath. Throughout the first two-thirds of the movie, the camera continuously cuts away from the action you’ve been waiting for. Rather than showing you what you want to see in full-glory, the movie frequently will take you to a different location where you’ll briefly see a few seconds of the catastrophe being watched by someone on television. It feels like a cheap trick to build up to some amazing climax, but it’s incredibly frustrating. It’s like when watching a reality TV show and then the show cuts to a commercial break before revealing the winner. Perhaps it would be more forgivable if the end was enjoyable, but even though it does give you a full display of the showdown, it’s bogged down by a tiresome human story and still lacks any real emotional punch. Despite the fact that the movie tries to convey a serious tone, it’s also incredibly cheesy. To the extent that the big finale that this movie has been trying so hard to build up to ends up being almost laughable. Ultimately the movie ends up just being unsatisfying, disappointing, and overly long.
There are a lot of ways in which Godzilla goes wrong, despite the film’s great potential. One of my issues is with the musical score, which ends up coming off like a bad punchline. Music is supposed to accentuate the action and drama of a film, yet the film feels emotionless and boring. The only time the music really stood out to me was when it was being used to heighten the suspense of the climactic battle, and essentially narrate who was winning. It was done so ineffectively that it was both kind of comical and embarrassing. I also have an issue with all of the special effects, which are being touted as absolutely amazing. They’re not. However, I will say that the use of special effects in the movie is quite ambitious, but it works to the film’s detriment. There’s simply too much of them, and this excessive nature of the film is, I think, its biggest mistake. Godzilla (2014) is ridiculously CGI-heavy, and while their scope is admirable, I really think the quality would have been substantially improved if they didn’t overdo it so much. I think a less-is-more approach would have benefited the film in many ways. It’s excessive to the point of making good things turn bad. Everything is way too over the top, causing the action to lose its impact. It’s evident the filmmakers were trying so hard to make this big-budget movie as epic as possible, but this enormous scale ends up backfiring. The rampage covers two continents, multiple cities, and even traverses the length of the Pacific Ocean. I can appreciate their attempt, but the movie is trying to do too much. In other words, Godzilla (2014) bites off more than it can chew.
I also have some problems with the film’s treatment of the titular character, Godzilla. First of all, for a movie named after him, he sure doesn’t appear much in it. He’s the reason why we want to see the movie, but he’s absent for the majority of the film. Even when he’s around, he’s largely obscured by CGI smoke and storm clouds, up until the final moments of the movie. I’m also not particularly fond of his appearance. He just doesn’t quite look like Godzilla to me. It’s like looking at a T-Rex head on Godzilla’s body. I’m aware that Godzilla’s facial appearance has changed many times over 60 years, but something just doesn’t look quite right here. Additionally, I feel that Godzilla’s face is actually too expressive in this new film. I wonder if this was done to cause viewers to feel more sympathetic to him, because in the film, Godzilla is actually depicted as something of a tragic hero, rather than a colossal beast. This is my biggest concern with the movie’s handling of his character. Godzilla’s destruction in the film is treated like it’s all unintentional, and just a result of his massive size. Even though humans attack him, he’s not angry about it or anything. Never mind the movie’s claim that all of America’s nuclear bomb tests after Hiroshima and Nagasaki were actually secretive but unsuccessful attempts to kill Godzilla. He doesn’t mind. He’s just a poor gentle giant that’s misunderstood. Really, Hollywood? Give me a break!
To say that Godzilla (2014) is almost as bad of a film as Godzilla (1998) is a statement that I don’t take lightly. It’s a bold and controversial thing to say, and it may seem a bit absurd considering that this film goes in the right direction, whereas the previous film was all wrong from the beginning. Yet while the new movie has all the right pieces for greatness, it extends its reach too far and attempts to do too much, while never managing to make any of it very good. In all seriousness, I was more entertained with the ’98 film than I was with this one. I can hardly comprehend how a movie with a giant 300-foot-tall monster destroying cities can be so boring. Godzilla (2014) focuses so much on trying to build up to an epic conclusion that it forgets to worry about making the audience care, or even about keeping them entertained, and it just gets worse as it goes on. It repeatedly tries to raise the stakes, as well as our expectations, while attempting to delay gratification until the end. It’s a risky move, and unsurprisingly, it certainly doesn’t pay off. On the bright side, Godzilla (2014) is probably a pretty sweet movie if you’re a 12-year-old. There’s plenty of action, some cool special effects, and he’s still a pretty awesome monster. However, for me, I was totally pumped up for this movie, but an hour and a half into it, I had endured enough and wanted to walk out. Godzilla (2014) disappointed me on so many levels. It’s a movie without a beating heart. It’s predictable, overly long, has uninspired characters and a weak story, and the action just never hits the right note. A little more emotion and a little less CGI could have a gone a long way in making this movie better. As a fan of Godzilla, I felt frustrated, detached, and perplexed with how they were able to do so much wrong when they had the groundwork for something great. You know, perhaps I’m wrong in claiming it’s comparably bad as Godzilla (1998). After all, the last time I saw that movie was in the theaters when I was 12.
(This review was originally posted at 5mmg.com on 5.17.14.)