Tuesday, June 27, 2017

Injustice 2 #12 Review

Writer: Tom Taylor
Art by: Mike S. Miller and J. Nanjan
Cover Price: $0.99
Release Date: June 27, 2017

Last issue we got a big setting shift as we jumped to the origin of Kara Zor-El as the planet Krypton was being attacked by Brainiac. Although the circumstances of the planet's demise seemed changed it wasn’t until the end of last issue where we saw a possible big shake up in the character of Supergirl. How will it follow up the cliffhanger of Black Adam being to finder of Kara’s crashed ship? Find out after the jump along with my thoughts.

We catch up as Kara seems to first wake, now in room of Adam’s domain, as Black Adam attempts to get her to speak. With the attempts failing he sets Nawal to attend to Kara as he goes off to take care of any issues with the craft having been spotted while crashing.

Black Adam meets a military force at his border as what seems to be a militaristic show of force in order to force will upon Kahndaq to give up what ever crashed. What basically comes of this is little more than a show of force and a more dark introduction for the character than what we’re normally used to.

After Adam’s show of force of his own he races off back to his palace with word greeting him of Kara finally speaking. What follows this is basically a catch up to the Injustice years before us, only it’s from the perspective of Black Adam and obviously leans heavy on the Superman good, Batman bad. Eventually it leads to a possible plan to make Superman’s escape.

Overall there really wasn’t much to gain from this issue for any long time fans of the Injustice series. We get an intro to Black Adam and some catch-up. We get a small glimpse of what could come next but it doesn’t really progress much as it doesn’t even call the character insinuated by actual name. I’d mostly put this issue as a skip, and that’s pretty rare for comics in general.

Bits and Pieces:

What equates to a small dark intro to a character and mostly catch-up on the Injustice series as a whole I would largely say this issue is skippable.


No comments:

Post a Comment