The Robins square off against the Talons while Grayson makes his way to the roost of The Court of Owls! That actually sounds a lot more exciting than it turned out to be…
For those of you not reading any of the other Bat-titles and only reading Robin: Son of Batman, you probably opened this issue and were very confused. What is going on? How did Damian get here? What is up with the art? Let me help clear up some of that for you. Robin: Son of Batman #7 is part 5 of the currently on-going “Robin War” storyline. If you have no interest in picking up the other books, or you just want a reminder of what happened, you can check out my review of part 4 here that also includes synopses for part 1-3.
“Robin War” has been very entertaining and a real fun read….so far. Having said that, this is the first issue that I felt really dropped the ball in terms of quality and content. The first thing you’ll notice upon opening the book is that Patrick Gleason does not provide the internal art for this issue. Instead, Scott McDaniel is on pencils. While McDaniel does an acceptable enough job, his art is leaps and bounds away from being as beautiful and refined as Gleason’s. It also comes as a shock since Gleason has handled all the art for Robin: Son of Batman thus far, covers and internal. Picking up this issue and seeing his art on the cover as usual but then not inside was somewhat of a surprise. In many ways, Robin:Son of Batman is his baby since he provides the story and art for the series. Now this is just me spitballing, but I wonder how much he felt that this storyline was invading his space. Maybe he passed on art duties because he didn’t care to pencil a narrative that had nothing to do with his vision for the character. (I swear, I’m not trying to start a rumor that Gleason has a problem with DC)
Next comes the story. Once again, it’s acceptable, but there are definitely some problems that need addressed. First off, it felt to me like they tried to cram way too much material into one book. What was here could have easily been broken up into two issues. Instead, we have abrupt changes in locale without a real lead-in to the scenes in question, characters show up without any explanation as to how they got where they are, and other characters who have no business being alive make appearances. It feels like they didn’t completely map out “Robin War” before they got to work on it. They just went about telling their story and were told at the last minute by DC that the next issue was the conclusion so they had to squeeze everything they had left to say into this one.
Not only was the content here worth spreading out, but some of the narrative deserved and could have easily supported a more lengthy story. This would have allowed for more time to flesh out and explore some of the ideas presented within this arc . As it stands, certain elements felt like they came to an abrupt ending when they still had plenty of mileage left in them. We still have the next issue to look forward to, but I can’t imagine how we are going to get the kind of payoff that could possibly measure up to the possibilities that this arc teased.
I know a lot of people are really enjoying this arc, so I have no desire to spoil the story for anyone. Check the tag for some of the specifics I found troublesome.
- You’re reading “Robin War”. This is part 5 of the arc.
This was a real low point for “Robin War”. I’ve greatly enjoyed this story arc up till now, but part 5 fails to deliver. The art was below standard and the story was overly stuffed, which in turn caused jarring transitions and unexplored shifts in character outlooks.
SCORE: 4 / 10