Well I have to hand it to the writers - they've done a pretty decent job digging themselves out of a massive hole. This episode was one that should have aired in January, not now. They've left a significant number of unanswered questions though - that is definitely frustrating but I went into this episode knowing that that was really the only certainty. It'll be interesting to see where they pick things up from now.
For some reason, this explanation feels very unlike castle to me and not really believable the way they executed it. But probably the 2 month gap is the issue for me in believing the explanation.
At least we got some explanation. It feels like an explanation the news will tell the public about some mysterious sighting or explosion and we the public will believe it. Well that's what happened. Whether it was all the info or some the characters believe it, so lets just move on with it. I want to know later from the writers, if this was always the plan with this.
It looks like a mad dash to this season's finish line, and grabbing as many loose ends as they go flying by. Who would have thought that 7.23 would still be cleaning the mess of that 3 card Monty stunt of 6.23.
I'm really disappointed. Spies and a terrorist attack? Extremly creative - not. And it doesn't even explain why he was missing two months. If the attack was imminent and they stopped it, Castle should have gone home after a couple of days. That just can't be all. It just can't.
I thought the Pandora-Linchpin crapolafest can not be topped. (or going below that.) I was wrong. :((( Damn with my curiousity about what could they come up with.
Only way I can explain the 2 months. Would be the dream in parts were memories, in that they couldn't have Castle found with a bullet wound adrift. So they gave his wound time to heal.
All in all, since Andrew wrote 6x23, you have to give David some kind of credit for trying to come up with an excuse for what happen. Even if its unbelievable
That was another awesome episode. I loved it from the beginning to end. And I loved that I didn't know what had happened to him till the end. I will be re watching it again when I get in from work.
The explanation was rich. Some questions were answered regarding taking Castle on his wedding day. I loved the interaction between Kate, Martha and Alexis. I wish this season there had been more of same. Interesting in this ep, none of the usual Kate, Castle kissing and phone call interruptions.
I seemed like a cover story by the people involved because Castle was investigating his whereabouts. If it truly was for the country and for a H.S. friend, then why not just approach him normally? Why run him of the road, nearly killing him and abduct him? The story line was good from the perspective it gave closure if we don't get another season but leaves a lot of holes in case we do get another season.
not happy about this episode at all, the explanation for why Castle was missing for so long was super far stretched and very unbelievable, this show used to be so good and now the writers just keep screwing it up
They can't squeeze everything people want into 1 episode. Even this, some had to really talk fast to get in all their lines. It may be explained more in season 8. You never know what all you're going to get in an episode. You just can't please all the people all the time. I saw a comment somewhere that there were going to be 13 episodes in season 8. Does this mean a shortened series finale or just a typo of 13 instead of 23? Hope it's not the end. Has anyone heard?
I have still to understand this episode in its totality...I need to watch it again, but it got my attention for all the 45 minutes+ of episode...It was intriguing in its shady way
Typical Castle story, far fetched, he seems to be crazy, everyone doesn't believe him then slowly the things he says all hold validity. I liked it, but there are huge holes. I feel the Jenkins guy who saved him in the end told him what Castle needed to be satisfied to leave it alone. These people know him, well. I have suspected from the beginning his CIA father was involved somehow and Castle did end up doing and seeing thighs he didn't want to remember. My guess is he was told a partial truth about what happened, we will see more later..I did like it, a lot!!!
I really liked the episode. Yes, this may not be a full explanation of what really happened, but at least we got something. I think the full thing will take a while to come out. They may explore it in other episodes. But if not at least Castle is with (married to) the love of his life. That is what we waited for isn't it? I think each Castle episode is different yet continues the storyline in one way or another. some people want to deal with tramatic, difficult or unexplained situations, some people just want to forget and put it behind them. Rick did a little of both. I loved how supportive Kate was. Rick supported her searching for her mother's killer. Now it was her turn. The revelation was kind of a suprise, but we have a glimpse at what he went through. Hope the rest of the answers will come eventually.
I can never say I didn't enjoy a Castle episode, the missing two months still left me slightly confused the writers did try to wrap it up somewhat, I'm still left with questions, however I'll take what I can get for as long as I can have it!!!!
It was a good episode and I have pieced some of it together studying the dreams, Bilal and Jenkins. Will be interesting to see how it unfolds in the finale.
For me it was a turn-off, it should have aired much earlier, like others suggested above. I was hoping until the last moment for a connection to badass Dad and a two part-satisfying episode, but no. :/
I didn't really like it, seemed a bit far fetched. A little like the Pandora/Linchpin desaster. And how the hell do Castles good bye videos fit into this??
Remember the days where everyone said in Marlowe we trust? Oh how I miss those... I just don't get how the (essentially) same team of writers once was so good and now keeps screwing things up.
Contract negotiations are ongoing from my understanding.
With Mr. Amann leaving and A. Marlowe and T. Miller moving on, (if we get a season 8) I hope Rob Bowman will take the helm and Chad and Dara Creasey will take over writing.
This ep was too small. It felt too much like a regular episode and not the ep that does a major season long story reveal. Castle was off. He was too calm. Espo tells him his story never held up for him...and Castle didn't really react at all. Huh? And the sophisticated mind wipe...complete with breaking into Castle's home and replacing photographs and year books? I would have been happier if Rick had had a traumatic head injury or something that he psychologically block...or something.
And where was Rick's father? This would have been the perfect episode to bring James Brolin back...or if he couldn't be on screen at least mention or reference him. I was diasppointed.
The episode was awful. This show is awful. I don't like going on forums to trash other people's shows, but I need to vent this publicly for some reason... I have watched every episode of Castle because I like Nathan Fillion, and with every potentially good setup the writers have shat all over it. I only have vague memories of what I hated about previous episodes so I'll just stick to this one. First off Castle says that every day he's been haunted by what happened to him, yet the writers had no interest in building that up throughout the season. They just told us suddenly in this episode. I like to see what a character is thinking and feeling, not just be told about it. Nathan Fillion is a strong enough actor that they could have thrown in subtle mentions throughout the season to let us in on how Castle is feeling about this. It's like the writers are afraid of ever going past the surface with these characters. So we waited all season with barely a mention, thinking the writers have to have something really good planned, otherwise, why would they have dug such a hole for themselves... nope. What we got was a ridiculous implausible partial explanation, revealed almost entirely in a long-winded expositional monologue (something this show revels in, weak writing), which added nothing of any substance to the characters, and, yet again, used sci/fi explanations. Selective memory erasing/rewriting is not possible, neither are invisibility suits, and nor is cosmetic surgery that makes people look exactly like someone else. There were a couple other magic episodes which I can't remember now because I'm so tired of this crap show... I was really hoping Nathan Fillion was not going to sign that contract. Sure, they could revisit the storyline to fill in some of the gaping holes, but Castle at the end of the episode seemed satisfied, which in and of itself is ridiculous. That would not have been good enough for Castle. I was far from satisfied and I wasn't the one who was shot and asked to have my memory erased still for a completely unknown reason. He doesn't even know if his worst case scenario is what happened, despite what Alexis said.
NOTE: Name-calling, personal attacks, spamming, excessive self-promotion, condescending pomposity, general assiness, racism, sexism, any-other-ism, homophobia, acrophobia, and destructive (versus constructive) criticism will get you BANNED from the party.
That was ridiculous and confusing but I love the explanation anyway. Okay then. He saved the world! A+, Castle.
ReplyDeleteIt was a typical Castle episode where there is no lighting for any kisses!
ReplyDeleteGonna need to re-watch the episode for clarification. I just understand that he saved the world.
ReplyDeleteWell I have to hand it to the writers - they've done a pretty decent job digging themselves out of a massive hole. This episode was one that should have aired in January, not now. They've left a significant number of unanswered questions though - that is definitely frustrating but I went into this episode knowing that that was really the only certainty. It'll be interesting to see where they pick things up from now.
ReplyDeleteFor some reason, this explanation feels very unlike castle to me and not really believable the way they executed it. But probably the 2 month gap is the issue for me in believing the explanation.
ReplyDeleteAt least we got some explanation. It feels like an explanation the news will tell the public about some mysterious sighting or explosion and we the public will believe it. Well that's what happened. Whether it was all the info or some the characters believe it, so lets just move on with it. I want to know later from the writers, if this was always the plan with this.
ReplyDeleteNow lets get back to more fun episodes
It looks like a mad dash to this season's finish line, and grabbing as many loose ends as they go flying by. Who would have thought that 7.23 would still be cleaning the mess of that 3 card Monty stunt of 6.23.
ReplyDeleteI'm really disappointed. Spies and a terrorist attack? Extremly creative - not. And it doesn't even explain why he was missing two months. If the attack was imminent and they stopped it, Castle should have gone home after a couple of days. That just can't be all. It just can't.
ReplyDeleteI thought the Pandora-Linchpin crapolafest can not be topped. (or going below that.) I was wrong. :(((
ReplyDeleteDamn with my curiousity about what could they come up with.
I read somewhere that this episode had "partial" revelations. so I think it´s not all:)
ReplyDeleteYou have to admit its better than any other time. B+ for the lighting crew
ReplyDeleteOnly way I can explain the 2 months. Would be the dream in parts were memories, in that they couldn't have Castle found with a bullet wound adrift. So they gave his wound time to heal.
ReplyDeleteAll in all, since Andrew wrote 6x23, you have to give David some kind of credit for trying to come up with an excuse for what happen. Even if its unbelievable
It doesn't take a rocket scientist to work out that the term "partial" is probably a bit generous. I'd expect only the surface has been scratched.
ReplyDeleteI hope nowhere. Forget this whole BS for good. It's the best for everybody.
ReplyDeleteThat was another awesome episode. I loved it from the beginning to end. And I loved that I didn't know what had happened to him till the end. I will be re watching it again when I get in from work.
ReplyDeleteAnd it doesn´t take a "rocket scientist" to work out that adding a ":)" means I was being, ot at least trying, to be funny:):)
ReplyDeleteThe explanation was rich. Some questions were answered regarding taking Castle on his wedding day. I loved the interaction between Kate, Martha and Alexis. I wish this season there had been more of same. Interesting in this ep, none of the usual Kate, Castle kissing and phone call interruptions.
ReplyDeleteI seemed like a cover story by the people involved because Castle was investigating his whereabouts. If it truly was for the country and for a H.S. friend, then why not just approach him normally? Why run him of the road, nearly killing him and abduct him? The story line was good from the perspective it gave closure if we don't get another season but leaves a lot of holes in case we do get another season.
ReplyDeleteglad to hear that. not a lot episodes left this season though and renewal is uncertain.
ReplyDeletenot happy about this episode at all, the explanation for why Castle was missing for so long was super far stretched and very unbelievable, this show used to be so good and now the writers just keep screwing it up
ReplyDeleteThey can't squeeze everything people want into 1 episode. Even this, some had to really talk fast to get in all their lines. It may be explained more in season 8. You never know what all you're going to get in an episode. You just can't please all the people all the time. I saw a comment somewhere that there were going to be 13 episodes in season 8. Does this mean a shortened series finale or just a typo of 13 instead of 23? Hope it's not the end. Has anyone heard?
ReplyDeleteI have still to understand this episode in its totality...I need to watch it again, but it got my attention for all the 45 minutes+ of episode...It was intriguing in its shady way
ReplyDeleteTypical Castle story, far fetched, he seems to be crazy, everyone doesn't believe him then slowly the things he says all hold validity. I liked it, but there are huge holes. I feel the Jenkins guy who saved him in the end told him what Castle needed to be satisfied to leave it alone. These people know him, well. I have suspected from the beginning his CIA father was involved somehow and Castle did end up doing and seeing thighs he didn't want to remember. My guess is he was told a partial truth about what happened, we will see more later..I did like it, a lot!!!
ReplyDeleteI really liked the episode. Yes, this may not be a full explanation of what really happened, but at least we got something. I think the full thing will take a while to come out. They may explore it in other episodes. But if not at least Castle is with (married to) the love of his life. That is what we waited for isn't it? I think each Castle episode is different yet continues the storyline in one way or another. some people want to deal with tramatic, difficult or unexplained situations, some people just want to forget and put it behind them. Rick did a little of both. I loved how supportive Kate was. Rick supported her searching for her mother's killer. Now it was her turn. The revelation was kind of a suprise, but we have a glimpse at what he went through. Hope the rest of the answers will come eventually.
ReplyDeleteI can never say I didn't enjoy a Castle episode, the missing two months still left me slightly confused the writers did try to wrap it up somewhat, I'm still left with questions, however I'll take what I can get for as long as I can have it!!!!
ReplyDeleteI suppose, though I felt like I was being lied to while watching the episode.
ReplyDeleteIt was a good episode and I have pieced some of it together studying the dreams, Bilal and Jenkins. Will be interesting to see how it unfolds in the finale.
ReplyDeleteFor me it was a turn-off, it should have aired much earlier, like others suggested above.
ReplyDeleteI was hoping until the last moment for a connection to badass Dad and a two part-satisfying episode, but no. :/
I didn't really like it, seemed a bit far fetched. A little like the Pandora/Linchpin desaster. And how the hell do Castles good bye videos fit into this??
ReplyDeleteRemember the days where everyone said in Marlowe we trust? Oh how I miss those... I just don't get how the (essentially) same team of writers once was so good and now keeps screwing things up.
Contract negotiations are ongoing from my understanding.
ReplyDeleteWith Mr. Amann leaving and A. Marlowe and T. Miller moving on, (if we get a season 8) I hope Rob Bowman will take the helm and Chad and Dara Creasey will take over writing.
One thing that I don't understand is why NF still signed on for another season even after doing this ep.
ReplyDeleteHere's my review for the ep:
LOL.
This ep was too small. It felt too much like a regular episode and not the ep that does a major season long story reveal. Castle was off. He was too calm. Espo tells him his story never held up for him...and Castle didn't really react at all. Huh? And the sophisticated mind wipe...complete with breaking into Castle's home and replacing photographs and year books? I would have been happier if Rick had had a traumatic head injury or something that he psychologically block...or something.
ReplyDeleteAnd where was Rick's father? This would have been the perfect episode to bring James Brolin back...or if he couldn't be on screen at least mention or reference him. I was diasppointed.
The episode was awful. This show is awful. I don't like going on forums to trash other people's shows, but I need to vent this publicly for some reason... I have watched every episode of Castle because I like Nathan Fillion, and with every potentially good setup the writers have shat all over it. I only have vague memories of what I hated about previous episodes so I'll just stick to this one. First off Castle says that every day he's been haunted by what happened to him, yet the writers had no interest in building that up throughout the season. They just told us suddenly in this episode. I like to see what a character is thinking and feeling, not just be told about it. Nathan Fillion is a strong enough actor that they could have thrown in subtle mentions throughout the season to let us in on how Castle is feeling about this. It's like the writers are afraid of ever going past the surface with these characters. So we waited all season with barely a mention, thinking the writers have to have something really good planned, otherwise, why would they have dug such a hole for themselves... nope. What we got was a ridiculous implausible partial explanation, revealed almost entirely in a long-winded expositional monologue (something this show revels in, weak writing), which added nothing of any substance to the characters, and, yet again, used sci/fi explanations. Selective memory erasing/rewriting is not possible, neither are invisibility suits, and nor is cosmetic surgery that makes people look exactly like someone else. There were a couple other magic episodes which I can't remember now because I'm so tired of this crap show... I was really hoping Nathan Fillion was not going to sign that contract. Sure, they could revisit the storyline to fill in some of the gaping holes, but Castle at the end of the episode seemed satisfied, which in and of itself is ridiculous. That would not have been good enough for Castle. I was far from satisfied and I wasn't the one who was shot and asked to have my memory erased still for a completely unknown reason. He doesn't even know if his worst case scenario is what happened, despite what Alexis said.
ReplyDelete