Review: Diamondhead

Diamondhead

diamondheadcover

Patrick Robinson’s Diamondhead is in some ways the perfect book for this blog. Robinson was one of the few authors to get going as a new technothriller writer after 1991, when the genre was imploding. Robinson also has a reputation for being well, not very good. After reading Diamondhead, I can say that, at least judged from that book, that reputation is accurate.

But there’s more to it. This isn’t just a clunkfest like say, a later Tom Clancy or “Tom Clancy’s” novel. It was strangely fascinating in how so many elements of the “cheap thriller” had, by the year 2009, just sort of mushed together.

The military details are ridiculously inaccurate, from SEALS riding into battle inside tanks (yes, along with the regular crew) to Sidewinders being used as air-to-ground missiles. Where this is particularly bad is the MacGuffin of the book, the titular missiles. They’re a new, formally banned as too cruel (wha?) type of anti-tank missile that burns the crew of any vehicle it penetrates-you know, like any other ATGM with a shaped charge that shoots something very hot into something with a lot of fuel and ammunition inside it.

But even beyond that, the genre kind of comes full circle back to the vigilante style as SEAL Mack Bedford (those are two truck brands) gets excoriated by the EVIL MEDIA, subject to a court martial that reminded me, no joke, of Phoenix Wright with all the loud “OBJECTIONS!”, before he gets his revenge on the evil French businessman/politician who’s been providing these super-missiles to rogue Islamist groups-and personally aiding in the first deployment of them. 

This plot could very well have worked as one of the classic “Men’s Adventure” thrillers. But unlike those, it suffers from the two things that plagued the technothriller-bloat and self-seriousness. At least with one of those books, you tended to get a brisk, smooth, “when in doubt, fight it out” style. This plods and clunks through unsuspenseful “suspense”, and then Mr. Truck just turns into John Rourke when the time comes for him to actually fight anyway. It has cheap thriller implausibility but not cheap thriller whimsy or bombast.

And the sad part is that more and more of the big-name, big-published “mainstream” thrillers (the kind I could find in the small book section of a local grocery store) are like this. There’s a reason why I review very few “big-time big-name” authors. Part of it is expense and part of it is me wanting to highlight obscure authors who need all the recognition they can get. But to be honest, a big part is that most of these thrillers are like Diamondheads in the ways that count.

Review: The Bear’s Claws

The Bear’s Claws

(Full disclosure: I was a beta reader for this book and thus received an advance review copy)

Reading The Bear’s Claws was a pleasant surprise, the likes of which I hadn’t gotten from a WWIII book since Team Yankee. This tells the story of a Soviet mechanized infantry unit as it progresses through a World War III in 1982.

Now I could mention the book’s shortcomings-in particular, its character arcs are not exactly the most unpredictable. But given the small of World War III fiction in general, having a book with all the things it did right was delightful to experience.

  • The Soviets not only win, but win handily. This does make sense for 1982, but it’s still good to see that leap being taken in popular WWIII fiction. And to add to that, it’s not portrayed as a cakewalk for the people on the ground.
  • In great contrast to the stereotypical Red Storm Rising-style type of book where viewpoint characters hop around, the “camera” here stays tightly focused.
  • Finally, it has the kind of “plotnukes” that I would normally denounce. Yet they were handled in a way that didn’t have me going “oh, come on!”. The plotnukes featured a personal connection and just the right amount of explanation.

This sort of thing doesn’t come along often. So I’m very happy to give The Bear’s Claws my thumbs up.

Review: A Talent For Revenge

A Talent For Revenge

specialistcover

I think I may have found it. The apex. The apogee. The peak. The high point, the distillation of everything that “men’s adventure” fiction contained, all packed into A Talent For Revenge, the premier book in the “Specialist” series by “John Cutter” (a pen name of John Shirley).

The book stars supermerc Jack Sullivan as he’s hired by an heiress to kill an exiled African dictator. (Yes, the plot can be summed up in one sentence. This is men’s adventure). The men’s adventure-ness of this can be summed up by how the book blends more or less every single trend that these throwaway pulps put together.

  • 70s men’s adventure was notorious for sexual sleaze. Guess what this book has lots of?
  • 80s men’s adventure was notorious for ridiculously long descriptions of weapons. Guess what this book has lots of?
  • 70s men’s adventure frequently let its heroes get banged up. This happens to Sullivan, but….
  • 80s men’s adventure frequently turned its heroes into unstoppable fleshy Terminators. Sullivan also definitely qualifies as one.
  • Then there’s the constants, like a ridiculous amount of gore and a total lack of tastefulness.

By the late 80s, the genre had (with the obvious exceptions) begun to harden around the “80s, no sex, lots and lots of gun descriptions” style. The 90s commercially devastated it to such a degree that technothrillers looked untouched in comparison. When I came of age, “men’s adventure” in its purest form was down to cheap-looking Gold Eagles with awkward covers.

So I have a strange appreciation for this spectacle. If I had to show someone one book that would sum up “men’s adventure”, it would be this one.

Review: Kidnapped

Kidnapped!

Kidnappedcover

The Twilight 2000 tabletop RPG is a classic of the Fuldapocalyptic World War III genre. So it’s a little disheartening to debut it on this blog with what could easily have been the nadir of the franchise. But the “Kidnapped!” module is still a very interesting example of just a bunch of things all going on a bunch of different paths until it all just breaks.

The big “problem” is that T2K’s later modules were a victim of the very success of its initial premise. The initial European setting was a good way to square the circle of “we want you to be in the military, but we don’t want you to just have to follow orders and sit around until an artillery barrage kills you.” It was also a good balance between “We want to give you limited resources unlike a contemporary setting, but we also want to give you more toys than a full post-apocalyptic setting.”

Yes, this led to issues between the two tones of a “grim struggle for survival” and “like a classic tabletop RPG, only with tanks instead of dragons”. But I have to give GDW credit for making something distinct and adaptable. Then the question is “how do you follow up on that?”

Enter the North American modules, which became increasingly theatrical and bizarre. The “Airlords of the Ozarks” module made me use the term “Arkansas vs. The Blimps” to describe any long series that veers into craziness. It got to the point where it wouldn’t have been too surprising to see the heroes venture into an Upstate New York bunker to retrieve Adolph Hitler’s frozen corpse (as happened in the later Survivalist novels).  But Kidnapped takes the cake both for pure dissonance and poor design.

  • It starts with a description of the super-drought about to strike North America. Too bad the actual main focus isn’t about this Frostpunk-style societal triage. No, it’s about a Hitman/Splinter Cell-style “go and get a high value target”. The target is Carl Hughes, leader of the authoritarian New America, in his Shenandoah supervillain lair.
  • Hughes, the target of the adventure, does not get official stats or an official portrait. But there is a page devoted to a gang of Native American marauders (oh, you 80s action RPGs) and several pages devoted to an abandoned New American facility that does nothing but give a “clue” and a “We’re sorry, Hughes is in another castle” experience.
  • Is Twilight 2000 supposed to be semi-grounded? Good. Now plausibly take on a fortified lair with over a hundred guards and a target who needs to be captured alive (so you can’t just snipe him).
  • Naturally, to fit this mammoth Cadillac V8 into a Smart Fortwo and make the module even slightly viable, there are gimmicks like convenient gaps in the security camera coverage, guards who’ve lived and worked together for years being able to fall for players in simple disguises, and Hughes never going any more than one level deep in the four-level underground complex even when threatened.
  • There are lots of descriptions of places that are either irrelevant or “beef-gated” (too well guarded to realistically challenge), and the “listing of important characters” not only doesn’t have Hughes, but also doesn’t have anyone else actually living in Hughes’ lair. But it does have lots of throwaway bandits-of-the-week!

So Kidnapped! is something I’d recommend only for Twilight 2000 completionists or people fascinated by “How NOT to make an RPG module.” It’s at the point where, if people were running a T2K game in North America and the GM wanted them to take on Hughes, I’d recommend just writing a scenario from scratch instead of consulting this.

For a second opinion on Kidnapped, you can check the the Twilight 2000 Wargaming Blog. That opinion is also not complimentary.

Review: Day Of The Delphi

Day Of The Delphi

delphicover

Despite being the sixth in the series, Day Of The Delphi is actually the first Blaine McCracken book I’d heard of. How had I heard of it? Well, it’s quite a story. Shamus Young, one of my favorite video game commentators, had listed it as one of his least favorite books ever. Naturally, this piqued my interest and I found the greatest thriller protagonist name ever. A little later, I heard the name “Blaine McCracken” again, got The Omega Command, and never looked back.

As for Day Of The Delphi itself, it’s excellent-by Blaine McCracken standards. The previous entry, The Vengeance of the Tau was still good, but it suffered from having the first disappointing central gimmick in the series. McCracken returns to form in this ridiculous epic.

The tone of this book (and the whole series) can be summed up by a scene disappointing to me. The disappointing scene did not involve any inconsistency, by now routine super-gambits, or laughably inaccurate designations of weapons. All those are in the book, but they aren’t the disappointing part of it.

No, the disappointing scene was a fight in a slaughterhouse that failed to take advantage of the potential to use live cows as weapons. McCracken uses the ramrod to kill an enemy. It needed more “battle cattle”. Other than the lack of battle cattle, this was a ridiculous Blaine McCracken spectacle extraordinaire. Yes, even by the standards of other books in the series.

It doesn’t have a MacGuffin that’s weird, but it makes up for by having an incredibly ridiculous (the plan of this book’s super-conspiracy ranks as dumb even by the standards of Blaine McCracken super-conspiracies) main plot. Some might reasonably think that’s bad. To me, I view it as part of the fun.

Review: The Samurai

The Samurai

cascacover

With the nineteenth entry in the series, The Samurai, Casca swings and misses dramatically like a called-up minor leaguer facing Nolan Ryan. Of all the Casca books I’ve read, this is the worst of them (so far). I’ve heard conflicting answers as to who was actually writing the later Casca books before Sadler’s death, but whoever was did not succeed here.

Knowing the history of the series, I was expecting a clumsy, stereotypical depiction of ancient Japan. And I got it. But it also has very blocky, clunky prose and flat fight scenes that take away the biggest strength of the Casca series-the ability to have effective action despite its protagonist being, you know, immortal.

Not that it really matters much, because here Casca himself might as well just be a second-rate hired gun in a dull story about dull rivals fighting for power in dull battles. Having all the weaknesses of the Casca books but none of the strengths, The Samurai is something I wouldn’t recommend even to fans of the series.

Review: SEAL Team Seven Direct Action

SEAL Team Seven 4: Direct Action

directactioncover

The SEAL Team Seven series, however much I enjoyed the first installment, is not the kind of series where reading every book in order is the most appropriate. So I decided on Direct Action for two main reasons. The first is that the summary seemed a little interesting. The second is that it’s the first book after original author William Keith was replaced by another writer under the “Keith Douglass” house name.

So, Lt. Blake Murdock (it’s not quite Blaine McCracken but it’s close) has to lead his SEALS into Lebanon to destroy a plant producing counterfeit American money, fighting Hezbollah and the Syrian Army in the process. The prose is a little clunkier and the action somewhat more extreme than the first book, but it’s still a good cheap thriller.

In fact, this book manages to have its cake and eat it too in a good way. It manages to have its SEALS scything their way through enemy fighters, soldiers, commandos, BMPS, and helicopters while at the same time throwing semi-plausible bits of “friction” in their path to make them earn their mission-and not without loss.

A part of me has “glass half empty” thoughts where I think “what if the big-name technothriller writers did a slightly higher-brow version of this instead of clunking along with an increasingly obsolete Cold War thriller model?” and lament what wasn’t. But another part of me has “glass half full” thoughts where I can just enjoy this well-done cheap thriller for what it is.

A Tag Change

For my 150th post on Fuldapocalypse, I’ve decided to make a few announcements. First, I made the tag cloud bigger again (It kind of needed to be). Second, I decided to break away from one of the most-used tags.

The “Infantry” category is perhaps the most awkward one on Fuldapocalypse. I first used it for a technothriller that did include infantry. Then it expanded to not only include special forces and sci-fi infantry, but also vigilantes and secret agents. The result was that, even though infantry “grunt fiction” isn’t exactly one of my favorite subgenres, “infantry” became one of the biggest and most used tags in Fuldapocalypse.

So while I’m not trying to edit existing posts, I’ve decided to specialize rather than generalize for “infantry”. So on the occasions that I do review ordinary infantry, I can keep the normal tag. Otherwise, stuff like “Secret agent” or “Special Forces” or “Vigilante” can work.

There’s obviously going to be tricky choices, but I think I can handle those on a case by case basis.

 

Review: War Breaks Out

War Breaks Out

When I got Martin Archer’s War Breaks Out, I was expecting a plodding Cold-War-Turned-Fuldapocalyptic-Hot story. The initial premise and the mediocre experience of the previous book I’d reviewed, Israel’s Next War, made me think that. Instead, I got one of the most crazy and just plain out-there examples of a World War III story I’ve ever read.

  • The timestream got scrambled. There are Eurofighter Typhoons and people who were injured in the Iraq and Afghanistan wars, but at the same time there’s a 1980s WWIII and everyone is using M60s and T-62s. Oh and Belgium has F-15s for some reason.
  • We’re introduced to the main character (who frequently appears in a weird form of first-person similar to that present in Israel’s Next War) immediately. He’s a one-star general who gets a quick promotion worthy of spacesuit commandos. The president decides he’s just that good, and needs a fighter, not those deskbound bureaucrats! (To be fair, this is officially the third in a series with the same main character, but still).
  • Said main character promptly comes up with a bunch of gimmicky tricks and special ops to turn the tide of the impending war against the USSR. These range from tricking Soviet AWACS with mass transponder changes to landing troops with ferries in the Baltic. Naturally, they all work.
  • The actual battle scenes themselves are the least amusing and most clunky and repetitive. Except for something I haven’t seen in a while-the attempted Soviet invasion of Iceland! It’s been a while, Ísland. I missed you!
  • The book ends with one of the most ridiculously blatant examples of “Foreshadowing” for the next installment in the series that I’ve seen. It’s not foreshadowing so much as building a city of giant neon signs indicating the plot point, then causing it to be lit up in a giant fireworks display that’s internationally televised, telling the plot point in a Super Bowl commercial, and then carving the plot point into the moon for good measure.

 

This was an experience. It’s probably as bad as “World War 1990” in terms of pure writing quality, but I had a lot more fun reading (and reviewing) it. I guess a better example would be an even more rough version of Ian Slater.

Review: Steel World

Steel World

steelworldcover

For BV Larson’s Steel World, I returned to a familiar place-the land of spacesuit commandos. Almost every single value checks out. Dystopian background? Check. The main character is a super-special spacesuit commando in a super-special spacesuit commando unit (in this case, a secret dirty tricks “Legion”)? Check. The main characters use nothing more than power armor and ray guns that don’t seem to really do much? Check. The tactics are iffy and everyone uses Roman ranks? Check.

The only novel feature, besides the use of “rules of war” that are clearly structured to enable the plot, is revivification. However, in practice all it does is remove tension, best summed up by having people -multiple times at that- want to be “killed” for the sake of convenience.

For all my complaining, Steel World manages to dodge the biggest problem with the subgenre. Its training sequences are not overly long, and I was thankful for that. And for all its issues, it’s still readable and fun as a mindless spacesuit commando novel.