With A Terrible Fate

Does Five Nights at Freddy’s Belong in the Video Game Canon?

The following is part of Now Loading, a series that renders verdicts on whether or not your favorite video games deserve a place in the canon of works that have contributed to video-game storytelling in landmark ways. Read the series’ full mission statement here.

“I, like God, do not play with dice and do not believe in coincidence.” –Scott Cawthon, Before Coincidence Handed Him the World on a Silver-Eyed Platter

Ladies and gentlemen, children of all ages beneath thirteen, hello and welcome to Now Loading…The Video Game Canon! The only weekly Internet column that takes a look at games from the past to determine whether they should be remembered in the future.

Well, Dear Reader, we’ve taken a look at a number of interesting games in the past few months, and while it seems like a fair number of you are enjoying the series so far, it would also seem that a fair number of that fair number of you are wondering why so many of the games I’ve been examining have been making it into the Canon.

Well, in keeping with this month of spooky games, the answer to that question just might scare you.

For you see, ladies and gentlemen, just like many creatures of the night that crawl from the inky blackness of our collective unconscious, I am a sort of monster. My life is spent ‘neath the moon, ruminating on the merits of good games and exalting them for all the wonderful things they have to offer the interactive medium. And yet, with each word of praise that falls from my lips, a sizable drop of vitriol forms in my mind and is stored away like some sort of… Hate Camel.

Yes, that’s right… For you see, with all the good that can come from games, there is just as much banal misery to be found within the confines of those ones and zeroes, and I must release the valve every now and again lest we all suffer a fate worse than death. The nature of that fate, you ask? Well, like Howard Phillips Lovecraft before me, I dare not speak on it.

I will, however, tell you that Five Nights at Freddy’s is an absolute garbage franchise that I hesitate to refer to as a game, and that this lazy, predictable, boring dumpster fire has only become a household name because of an incredibly fortunate (yet unfortunate) confluence of events that kept its insipid excuse of a creator pumping out sequel after sequel until even he seems to have realized that the true horror he hath wrought is not in the “horror game” he made, but rather the infuriating impact on storytelling that his dumb jump-scare simulator has had on not only horror games, but also on a large chunk of the independent development scene.

In his house at Fazbear’s, dumb Freddy lays collecting his residuals.

Let me be very clear here: Five Nights at Freddy’s is a terrible game that we only know about today because of Let’s Players, Internet Theorists who gave the “story” more credence than it ever deserved, and a young fan base who appear to be equal parts scared of and in love with the animatronic monsters that wander the halls of this haunted pizzeria.

This will not get into the Canon even in the sense that it is so bad that we can learn something from it. This game, and its creator, Scott Cawthon, are flukes: benefactors of Fortunia’s Wheel turning their way time and time again, without neither rhyme nor reason. This canon piece will not strictly be about what works and what doesn’t work in the game, but rather about how the seeds of horrible trends are planted with vague, dime-store, mystery-novel-writing hands.

Are you sitting comfortably? Then let’s begin.

This is actually the cover.

In the interest of being frank, let me tell you right now that we will only be looking at the first entry into this seemingly endless series because, as I see it, it was the inexplicable interest in this first game that led to the explosion of the franchise. Furthermore, the project of Now Loading is to take a hard look at one video game at a time, so raising arguments based on elements from the piss-poor sequels we got for this game will not sway me one iota.

Five Nights at Freddy’s is a “survival horror” game released on Steam on August 8th, 2014 to near instant success, which is a blight on humanity’s collective soul that I will explore further down the line. It was written, designed, developed, and produced by “game developer” Scott Cawthon, a man whose unbelievable monetary success and keen ability to franchise are rivaled only by George Lucas himself.

Now, there is a very easy comparison to be made between Scott Cawthon and two previous auteurs we have discussed: Toby Fox of Undertale, and Satoshi Tajiri of Pokémon. All three share an interest in video games as a medium, all three dabbled in game development before their big success, and all three had an intense degree of control when it came to the games they were creating. Where they differ, however, is in the quality of their content and their ability to produce well-crafted masterpieces. By my own criteria discussed in those two aforementioned articles, I have no choice but to classify Scott Cawthon as a video game auteur for the way he put his blood, sweat, and tears into this game that he alone funded and created.

But you know what, Dear Reader? That also means that director Ed Wood is an auteur, which is a fitting analogy considering Five Nights at Freddy’s has all the polish and aplomb of Plan Nine from Outer Space.

At least Plan Nine had shots like this.

Being an auteur simply means that you fall into certain patterns and use certain tropes that define your style as distinct from everyone else’s. In the case of Toby Fox, Undertale’s writing and characterization is like no other game’s. Satoshi Tajiri’s Pokémon games are drenched in childhood-wonder themes of bettering oneself through exploration and growth. Scott Cawthon has a penchant for tricking players into thinking his games are deeper than they really are, by alluding to a greater mystery, the answers to which he can’t be bothered to come up with.

Auteurs can be hacks, Dear Reader, and Scott Cawthon is right at the top of Hack City.

Now is the point in my article when I emulate every other Five Nights at Freddy’s commentator and bring up the fact that the game Cawthon made previous to this one, Chipper and Sons Lumber Co., was such a critical and commercial failure that it nearly caused him to pack up his game-making tools and head for a life of suburban fatherhood. And yet it was the wise words of Jim Sterling, the first of many YouTubers to lend their influence to this eventual franchise, that urged Cawthon to make a much scarier game. The animal characters in Chipper and Sons Lumber Co. looked so rubbery that they seemed like sentient animatronics, and so they gave off a much creepier vibe than old Scottie had intended.

This, Dear Reader, is the first of many coincidences-originating-from-failure that propelled this stupid game to super stardom. Cawthon’s game had faults, a critic lampooned those faults, then Cawthon took those faults and, instead of improving on his own skills, simply refashioned those faults and put them into a new game where the FAULTS WERE THE MAIN COMPONENT OF THE GAME.

“But Canon Boy!” I hear you all shouting fervently, assuming my title is Canon Boy, “You lauded Silent Hill for working within its limitations to make a better game, so why won’t you give Scott Cawthon the same slack for Freddy Fivenights?”

Yes, Silent Hill took its weaknesses like the low rendering capability of the PlayStation and turned them into strengths, but that was a creative way around a limitation that they could not resolve. The fog covering up the slow rendering became a staple of the series after the fact. Team Silent didn’t look at the PS1, realize it had low rendering capability, and then say, “Well you know what we oughta do? Make a game about low rendering capability!” Scott Cawthon was told he had a fault, refused to improve upon that fault, and instead simply made a game where the fault seemed like a feature. Sure, it was a deliberate choice, but so is driving stick and keeping the car in first gear the entire time even after your Dad told you not to do that. Yeah, you’re technically driving the car, but you’re doing a horrible job of it.

My vitriol hump is just getting deflated, so hop along this Hate Camel and let’s look at the game itself.

Story and Characters: I Have Run Out of Quotation Marks

TAKE ONE: WHAT SCOTT CAWTHON DECIDED ON

Okay. Here we go. I’m going to tell you the spooky story of Freddy Fivenights, and you’re going to have no choice but to agree with me because the literal text of the game is so barebones, skeletons are telling it to cover up and be a bit more modest.

You “play” as a character named Mike Schmidt, who has just started a job as a night-shift security guard at a pizzeria/arcade/Chuck E. Cheese knockoff. You are told by some guy on the phone (whom fans of the series have brilliantly named “Phone Guy”) that the animatronic mascot characters that play in the stage band for the kiddies get off the stage and wander around the place at night so that “their servos don’t freeze.”

This would be fine, except that when they see a human at night, they assume that the human is a robotic endoskeleton that is outside of its suit; so, if they catch you, they will forcibly stuff you into one of the robot costumes. Again, you’d think this would be fine, except that there are tons of motors, gears, and other mechanical gadgetry lining the insides of those suits, so being shoved into one is like being trapped in an iron maiden. The objective of the story is simply survive five nights of your security shift without being stuffed into a mechanical suit.

Also, Phone Guy hints that there were a number of kids who went missing, and that parents complained about strange smells and weird liquids leaking out of the animatronics’ facial features.

Ooky spooky.

EXPERIENCE TRUE TERROR! NOW AT THE OFFICE!

TAKE TWO: THE DECISION-MAKING PROCESS

There are so many noticeable, grade-school rewrites that Scott Cawthon no doubt made while coming up with the “story” of this game that I almost feel like a bully pointing them out. I’m going to lay out for you what I think the thought process of the story development was here, because I think it’s indicative of a bigger problem in Scott’s storytelling capabilities that I will explore later in this article.

So, first, Scott clearly came up with the gameplay idea. Now, Dear Reader, enjoy Scott Cawthon’s Inner Monologue Theater:

Sit the player in a room and do not allow them to move. Have a threat constantly trying to get into their room and give them limited means through which they can avoid that grisly fate. Okay, so far so good, but we run into a problem: What is the threat?

All right, well, that Jim Sterling guy said my characters look like creepy animatronics, so let’s make the threat be these demonic robots hell-bent on killing the player. That’s good, that’s good… but why do they want to kill the player?

Oh! I know, they are capable of delineating between robots and non-robots, and they stuff people into empty suits if they think they’re non-robots! Huh. But wait, why don’t they do that during the day when they see all the kids in the restaurant? Hmm… well, it only happens at night! Wait, but why would these animatronics even be an issue at night? Oh, duh, I’ll say that the owners don’t want their servos to lock up, so they can roam freely at night! Robots have servos, so that’s a perfect fix.

So we’re nearly done coding here, and… oh, wait. Why would being stuffed into a suit be such a bad thing? I mean, if it’s just an empty mascot suit, people wear those at theme restaurants all the time, no problem. Hmm…well, what if the empty mascot suits actually have like, gears and wiring in them? Like they aren’t suits, but they’re empty robots? Yeah! And that way, if the robots see a human, they think it’s a robot out of its robot suit, and they’ll shove it down into a pit of broken wires and stuff! Damn, this game wrote itself.

“Booooooo! Get F****d!”–Harry S. Plinkett

And, scene.

Now who knows, maybe it didn’t happen like that. Maybe Scott Cawthon had it all planned out from the beginning, and his weird writing choices were all in service of later installments, and the puzzle of convenience would all come together at the end of Five Nights at Freddy’s 12: The Freddening. Maybe I’m wrong and millions of fans are right, and he’s the enigmatic writing genius that everyone thinks he is.

Maybe, but no. Nope. He’s a hack who can’t write.

Speaking of which!

Gameplay, Visuals, and Music: I’ll Take “Three Things We Don’t Have Here,” Alex

Due to its nature, horror is allowed to be a very ambiguous genre. In fact, vagueness and ambiguity often help make something even more terrifying than the author may have originally intended. The classic example here is the shark in Jaws, which was famously made even more terrifying because we couldn’t see it for the majority of the movie. The human mind is capable of conjuring far scarier things than any outside stimulus can, and it is our own thought processes, anxiety, and paranoia that truly scare us when we engage with a horror story.

We’ll never know, and that’s what terrifies us.

What doesn’t terrify us is loud, obnoxious screaming that we know is coming. Five Nights’ gameplay, if you can call it that, includes keeping the power running so that you can look at your cameras so that you can keep an eye on Freddy and Friends, so that you can close the doors on either side of you when they are about to run in and scare you to death.

So here’s the thing, Dear Reader: I will give kudos to this game because it keeps you planted firmly in one spot, giving you no choice to run away from the monsters that are trying to chase you. In pure horror terms, this is a great idea. It turns the whole scenario into a sort of waking nightmare from which there is no escape, and it takes away the one instinctual piece of agency that every one of us has deep down within us: flight. Where the game completely wrecks this interesting concept is with the implementation of jump scares.

This is what you’re all so scared of.

The only penalty you have for death, the ONLY penalty, is a jump scare. A loud, startling noise, complete with one of the animatronics jumping in your face. This is such a cheap tactic that I’m even surprised by my dime-store novelist straw man using it in the first place.

Imagine how much more terrifying this game would be if you were locked in place and something steadily creeped into your security room. You know it’s there, doing something, but, as if you’re in a bout of sleep paralysis you can’t run away, you can’t move. You can’t even scream.

But nope! It’s a loud noise, blasted at full volume to catch you off guard. Except even this fails after a while, because once you know what’s coming, even the jump scares lose the power to startle you. There is nothing redeeming about the scares in this game. You may as well be slamming your hand down on a joy buzzer every time one of those stupid robots pops into your field of vision.

The visuals are, shock of all shockers, rubbery and stupid-looking. I will admit that the atmosphere of the derelict pizzeria is pretty creepy, but with a giant bear, duck, bunny, and fox running around it, the scary sheen sort of falls away after a while. See, animatronics are kind of like clowns. You can claim that they scare you all you want, but I just refuse to buy the fact that anyone is creeped out by them to the point that they are viable horror icons.

This is the part of the article where I usually talk about the game’s music, but there is no music in this game. I would usually make a point to discuss the ambient sound in place of the music, if there is any, but Five Nights’ ambient music is so generic and “spooky house” themed that I swear Scott Cawthon got one of those “Fifty Haunted House Tracks to Boost Your Halloween!” CDs and only used the “creepy breathing” track. With the odd exception of distorted laughter being played in either one of your headphones, there’s not much to speak of musically in this game except for a boring, dull hum that persists throughout the entire game. Oh, and I guess the constant, high-pitched screaming from the jump scares.

There is nothing redeemable about the gameplay, music, or visuals in Five Nights at Freddy’s.

Nothing.

Impact on Gaming and Culture: Go Straight to Hell, YouTube

So we all know that this game took off straight to the moon and was followed by a number of quickly released sequels that were all basically the same game, and that there were two novels released and a movie coming out whenever Warner Bros. stops raking in the cash from IT. And if you didn’t know about all that, that’s pretty much what you need to know, as far as I’m concerned. I’m far more interested in how this hot garbage pile of a game actually made it as far as it did in the first place.

Ignoring Jim Sterling as the proto-culprit who inadvertently inspired Scott Cawthon to make a horror game, the first person to really popularize Five Nights at Freddy’s was the YouTube Let’s Player, Markiplier. Mark played this game just two days after its initial release, titling the video “WARNING: SCARIEST GAME IN YEARS”, which naturally attracted the attention of his millions of subscribers, who subsequently clicked on it and lost their minds.

Why? Well, I can only assume they were reacting less to the game and more to Mark’s charming overreactions as he played it. His hyperbolic way of playing games naturally endears you to him, and, through a weird sort of transitive property, that endearment rubs off on whatever game he is playing. That first video he put out currently has 62 million views, which is by far the most viewed video he has. Those numbers are very attractive.

See? That’s charisma, baby.

Naturally, this led to Markiplier completing the game, and those views essentially soul-bonded him to the concept of playing every single sequel that would ever be produced. And I have to say, Dear Reader, that I don’t blame Markiplier for the massive explosion of popularity that this game had. He played the game and put out a number of videos referencing the game to garner views, but they were all quality videos that were enjoyable to watch. Like I said, Markiplier is immensely likable, so it’s not too hard to believe that those videos would be successes. And what’s more, Mark never once even hinted at the idea that this game was more than it was. He played the game, he was spooked, and that was it.

Had it ended there, I wouldn’t be talking about this festering pustule. No, it’s what came after. It’s all the hype-mongering, lore-theorizing, seeing-more-than-what-was-there tomfoolery that really inspired Scott Cawthon to keep making these games, and keep making more and more money.

Enter Game Theory and MatPat.

“Are you sure you want that to be the photo? You’re serious? All right, whatever.”

It started with one video callously comparing the events of the game’s “hidden lore” to a real-life shooting that took place in a Chuck E. Cheese. The connections were tenuous at best, but the video gained a huge following. Suddenly, “Game Theory” rapidly became “Five Nights at Freddy’s Theory,” with each new installment of the series bringing in a new “theory” video from MatPat. The views skyrocketed, and Scott Cawthon seemingly kept making the games just so that MatPat and others like him would keep making videos about the increasingly vague storyline that the games kept shoddily cobbling together. Soon it became an arms race between MatPat and Scott Cawthon, the former trying desperately to piece together the lore, timeline, and basic plot that the latter was thinking up on the spot. And maybe it was because they were so deep into it at this point, or maybe it was because the videos that MatPat produced and the games that Cawthon made were just too profitable at this point, but both of them refuse to admit the simple truth that there is no story.

There is no grand design slowly being pieced together by Scott Cawthon. There is no true timeline of events, there is no true identity to the hinted-at child killer from the first game, and there is no point to any of this—other than a perpetual boost to the creator’s ego, as well as his wallet. No amount of obfuscating the plot will change the fact that Five Night’s at Freddy’s is a poorly designed, bad game.

This retro avatar will give me legitimacy, right?

BONUS LEVEL

Nope.

VERDICT: What Do You Think

Well there, ladies and gentlemen: my vitriol hump has been exhausted, and this Hate Camel will recede back into darkness of the night. I cannot wait to hear all the people who are no doubt already chomping at the bit to tell me just how wrong I am, and that the story behind these games is too complex and terrifying for my little mind to understand. To those people, I wish a swift recovery from their delusion, and a deep shame for trying to defend a horror game that is so objectively broken that it has used the very mechanism in your brain that typically allows for horror to work and turned it on its head completely. This game is so laughably bad, with just enough vagueness in its storytelling, that it has actually convinced people that it is good.

If only it could have used this power in conjunction with a functioning horror game, maybe I would have one good thing to say about it before forcibly returning it to the weeds.