There’s an old saying that there’s nothing new under the sun. Hollywood does its best to fulfill that saying by copying itself year after year, remaking movies, following whatever trend is hot, and generally retelling, recycling, repackaging, and telling the same stories decade after decade.
And then there are the ripoffs.
For years now, the Asylum has specialized in making a seemingly endless amount of ‘mockbusters’ designed to cash in on whatever hit movie is in theaters at the time. Typically made on an impossibly tiny budget and rushed into production, the end result is rarely good, but every so often you can get an amusing gem that manages to entertain despite its grade-Z production values.
‘Atlantic Rim’ is not one of those movies.
In the pantheon of Asylum films, ‘Atlantic Rim’ is strictly in the middle: It’s not horrible, but not great either, with scenes that don’t add anything to the story, plenty of mindless fighting, and three robots whacking a monster with giant robot melee weapons for what feels like fifteen minutes before realizing that it isn’t working. Still, there are a few good lessons to be found here, so let’s suit up in duct-tape covered wetsuits robot control suits and take a look.
Consider having your reckless character actually face consequences for his/her actions
Mech pilot Red Watters (yes, that’s his name) is your typical hot-blooded, reckless military maverick who is the best at what he does, but goes his own way without respecting the chain of command. However, unlike many other mavericks, Red is arrested after going on his initial mission in ‘Atlantic Rim,’ and destroying a lot of property and lives, earning him a trip to the brig instead of begrudging praise from those higher up on the command chain.
In our own stories, having a military maverick actually face consequences for their actions tells our audience that the characters in your story expect competence and don’t fool around. While it’s fine to bend the rules in fiction, it can be more surprising to see them strictly enforced.
Avoid having characters describe what just happened to other characters
Shortly after Red defeats the first monster, he happily tells Tracy and Jim what just happened, gleefully describing his exploits. While it’s logical to tell others what they couldn’t have seen, we, the audience, saw the events described, making the scene redundant and eating up screen time that could have been devoted to something more interesting.
When faced with needing to inform other characters in our own stories about events that have happened, the best option is to either have said characters be told off-screen, or saying something like, ‘It only took a few minutes for Carl to breathlessly tell the others about the dangers he had faced, and what they would be soon going up against.’
Consider poking fun at love-triangle cliches
Near the end of ‘Atlantic Rim’s second act, Red, Tracy, and Jim are celebrating and drinking in a bar (despite not having done anything to stop the latest monster attack), when Tracy and Jim nervously tell Red that they kissed each other, making us think that we’re going to be subjected to a late-game love triangle… only to have Red laugh and brush it off, revealing that he doesn’t care. Moments later, the three set off to save New York, and the love triangle is never seen or heard from again.
Love triangles may be among the most irritating story conventions to be found in fiction, especially where they aren’t wanted or needed, which makes ‘Atlantic Rim’ s take on the matter refreshing. Doing the same in our own works will tell our audiences that we know how annoying these triangles are, and that we aren’t going to subject them to one.
Consider having your missing thing be used as a weapon by the monster
Tell me if you’ve seen this before: A well-equipped group is searching for a monster (or in territory where there are monsters) and one of their distant vehicles or team members suddenly goes silent. It’s all too common for everyone else to suffer the same fate moments later, but I like how ‘Atlantic Rim’ handles this tripe: A submarine goes silent while hunting for an undersea monster, and the aircraft carrier in command of a naval fleet tries to get in touch with them, only for the submarine to be then thrown from the water into the carrier, sinking it.
Aside from the visceral thrill of seeing two huge vehicles slam into one another, having your monster/villain throw their prey back at those who are looking for him/her/it can be a great moment to show that the monster is more than just a dumb brute: By throwing their prey back, they can show intelligence by using it to destroy something else, demoralize others by taunting them, or humor, as if saying, ‘Oh, looking for this? Okay, here you go!’
When all else fails, throw your enemies into space
After what feels like 15 minutes of whacking the final monster with melee weapons, Red realizes that such tactics aren’t going to defeat it. So, what does he do? Ram the beast, fly it into the atmosphere, and eject it into outer space (where it explodes). It’s a simple but effective method, as hurling your enemy into outer space is a nearly foolproof way of getting rid of them for good. After all, space is really big, and once your enemy is thrown into it (presumably without any rockets, jet packs, or engines), they have nothing to grab onto, ensuring that they can’t come back.
When your story has an egomaniac military maverick, have them face serious consequences for their actions, while also avoiding love triangles, not having one character tell others what we’ve already seen, having the monster of the story use a missing object/individual as a weapon to showcase their intelligence, and then defeat that monster for good by hurling it into the void of space.