Discussing Creepypastas that I love, particularly interesting Creepypastas I read in highschool, modern Creepypastas, and Creepypastas I think deserve more attention.
Please note that these enteries will contain content that may be distressing to some people.
I highly encourage you to read this story before I talk about it, because it's one of my favorite Creepypastas out there. The story spans over 13 parts, but isn't that long of a read. This entry will contain spoilers for the story, but I will hide them.
The story starts with the author playing The Legend of Zelda: Ocarina of Time, and discovering a strange girl NPC T-posing and hovering in the middle of a field, with red hair and a white dress and no other textures. The NPC starts to cause the game to glitch out horrendously, to the point where it becomes unplayable.
Upon posting the incident to a message board, the author is met with skepticism from everyone who reads it. Even though the game was still new at the time, many brushed it off as just a fake story. Seven years later, the author is contacted by someone who read his post on the board, and invites him to join The Princess Society, a group for those who have encountered this strange NPC in their games.
Spoilers beyond this point, click here to continue.Through this society, the author learns about how The Princess works, including her ability to kill if provoked enough.
He retells the story of Adam and Brian, two members of the society that attempted to summon The Princess in order to communicate with her. The tried several games before she finally appeared to them in Ocarina of Time, which seems to be her favorite game. This started a lengthy in-game battle between her and Adam, during which Adam became increasingly more and more invested to the point of madness, threatening Brian with a knife when Brian tried to turn off the game. Brian left, but that next morning Adam was found dead, looking like someone had beaten the absolute shit out of him.
This event happened before the author joined the society, but it certainly sent a shockwave through the society, and The Princess became something to be feared.
The sad things is, Adam was not the only fatality of The Princess. Years before the society started, Ellie, a ten year old girl, became infatuated with The Princess in such a way that her parents sent her to counseling. The Princess killed Ellie after she stopped believing she was real, and her older sister Faye was the one who discovered the gruesome aftermath.
MAJOR Spoilers beyond this point, click here to continue.At some point, the author learns the tragic origin story of The Princess.
The Princess was supposed to be a companion for the main character in an unfinished and unreleased game only known as Hero and Princess. It was made to compete with the newly announced Ocarina of Time, and the game's creator, Mr. Carver, had a lot of passion for it.
The Princess was meant to use an incredibly advanced AI system, completely free-thinking with her helpfulness in the game tied directly to how you treated her. However, the feature was much too advanced for the N64. When Mr. Carver repeatedly refused to alter it to better fit the console's limitations, the publisher forced The Princess' removal from the game entirely. This caused Mr. Carver to go into a deep depression, and his instability led to him being removed from the project. After this, he ended his own life. His apartment was discovered to be full of drawings of The Princess, many of them depicting her either in peril or t-posing with no face.
This is what is commonly theorized to have created The Princess entity.
After the tragedy, The Princess began showing up during the testing phase of Hero and Princess, even after repeated attempts to remove her from the game. One employee was even found passed out with a crumpled drawing of The Princess in her hand, and the drawing caused her to freak out and quit her job.
Hero and Princess was finally canceled, people were leaving the project and testers were unwilling to stay, and the studio moved on to another project.
Unfortunately, the executive producer of the project also ended his life six months after the project was canceled, presumably after encountering The Princess while playing Ocarina of Time in his office.
One of the testers who witnessed all of this, Dan, came to the society to tell his story, and also to get help with making contact with The Princess himself.
Already, he had played a variety of games, sometimes multiple at once, in order to increase his chances of encountering her. After getting her to appear in the Gamecube port of Ocarina of Time, he turned off his television, successfully trapping her inside of the game. But time is running out, his Gamecube has been on for probably days at this point, and The Princess is trying to fry the console in order to escape.
His plan is to get everyone in the society on a livestream, where he will confront and defeat The Princess once and for all.
Though, you can already tell just how well it goes, if we've learned anything from the incident with Adam.
And so, after everything he's learned and witnessed, the author puts this series out as a warning to others.
If you see her...turn off the game.
Yet another creepypasta that I will encourage you to read in full before I discuss it here. There are 8 chapters in all, chapters 5 and 8 are split into two parts, plus an epilogue.
Throughout the pasta, there's stunning pixel art of the different levels and enemies of the game. There's even a playable version you can download from the game's website. I think there may have been music tracks, specifically the music that was added to the game, on the website at some point, but maybe I'm remembering wrong. There's also a sequel that I haven't read yet. Though the last update to the sequel was Chapter 6 in March of 2023, but seeing as there was a 2 year gap between chapters 5 and 6, I don't think that the series is abandoned. I think that it just takes longer for them to make the art for the screenshots than it was for the original series, either that or there's just other stuff going on in the creator's life.
Anyway. This story is about the game Godzilla: Monster of Monsters for the Nintendo Entertainment System. Or, actually, it's about Zach, the player of a copy of the game that seems to be possessed by some demonic entity dedicated to tormenting him psychologically.
His friend finds him a used copy of the game, and he plays it for some good old childhood nostalgia, only to find that the game is different than he remembers. Initially chalking this up to some sort of prototype or beta version of the game with some glitches, but realizes that there's new levels, characters, and bosses that seem to be way too much for an average NES game. One such boss, which has become the face of the creepypasta, is known as Red. A large, intimidating, skeletal demon creature that chases Zach at the end of each chapter, before he finally gets to fight him in an epic final battle. (But that's getting a little too far ahead in the story.)
But as he keeps playing, he starts to notice that the game seems to be aware of him, and discovers that whoever, or whatever, created this nightmare seems to have done so SPECIFICALLY for him.
MAJOR Spoilers beyond this point, click here to continue.In fact, he turns out to be exactly right. As Red brings up an old wound from Zach's past in the form of a strange blue figure. This blue figure is his middle school sweetheart, Melissa, who was diagnosed with an unknown mental illness that caused her to go into strange trances where she would sit still and expressionless, speaking in clear and concise monotone, after which she would have a sort of recuperation period where she would tremble and hide her face and refuse to speak.
Tragically, while she and Zach were stargazing in a field one night, she had one of her usual episodes, and it caused her to run into traffic. She was killed after she was hit by a truck. Losing a someone like that at middle school age is already hard enough, but the game was taunting him about it through this blue figure.
Even worse, Zach discovers that it was Red who had been tormenting Melissa her entire life, and it was Red that caused her to run into traffic that night. It becomes very clear as the game goes on afterwards that now, for whatever reason, Red was back to finish the job.
This is a creepypasta that I discovered as it was being written, and I remember checking the website daily, even during school, to see if it had updated. I'm not afraid to admit that I shed a few tears at the ending. While not your standard creepypasta, it is certainly a well written one, and being accompanied by artwork makes it even better. Dare I say, this even could be viewed as a sort of ARG or unfiction series, due to the sheer amount of work put into it to make it feel real and tangible. Absolutely something you should read, or even listen to as there is an official reading of it, if you like creative works like this.
Ah, a classic creepypasta that holds a special place in my heart.
Pokemon Silver was my first Pokemon game. Well, mainline Pokemon game. Technically the first Pokemon game I ever played was Pokemon Snap at my babysitter's house on her son's N64. Still, though. Funnily enough, the save battery on my Silver cartridge died not too long after I got Soul Silver.
This one I won't mark spoilers for, since it's pretty well known. But if you want to go ahead and read it first, then feel free.
The story starts with our author excited for Soul Silver, but not being able to afford it quite yet. Feeling nostalgic, he decides to play Crystal instead, but remembers that his mother threw it away when he was younger, after the save battery died, along with his original Silver. No big deal, he decides to buy a used copy from Gamestop instead, for a relatively cheap price of $10.
But he soon finds that this copy is acting strange. It takes forever to boot up, and once it does it boots right into the game, no title screen or file select.
The player character is strange too, being named "…" and having the maximum of everything. He has all 251 pokemon registered in the pokedex, and yet his team is five unknown and a Cyndaquil named HURRY. Upon looking at the stats, the author finds that the unknown spell out LEAVE.
The player character is in some weird version of Bellsprout Tower, completely alone, not even any wild pokemon when walking around. Eventually, the author finds a ladder that leads to a dark hallway, needing to use flash to see where he's going, and the music stuck on the Alph Ruins radio.
He walks down the hallway and, despite using flash, it gets darker as he walks along. He comes to a sign saying "TURN BACK NOW" and is presented with a Yes or No choice. He chooses yes, and is taken to another dark room, the music being replaced with the Poke-Flute radio.
The cyndaquil faints upon using flash again, but when the author checks his team he finds that its changed to all unknown, spelling out HEDIED. Even stranger, the trainer sprite was missing his arms, and the trainer card claimed that he had 24 badges.
After wandering around a the strange, tiny room surrounded by graves, the trainer starts spinning slowly downwards and falls into a hellish red Sprout Tower. His team now has 5 unknown and one shiny Celebi, the unknown spell out DYING and the Celebi is cut in half and only knows one move, Perish Song. The trainer has now turned black and white and is missing his legs, with bloody tears and now 32 badges.
Walking along, the author comes across some NPCs who are just facing forwards, also black and white, and unable to be interacted with. He keeps going and encouters Red, being thrown into a battle. The Unknown Radio music starts up again, but this time backwards, Red throws out a Pikachu, while the player throws out Celebi.
Pikachu and Celebi battle it out, with Pikachu using Curse, Flail, Frustration, and Mean Look. Celebi can only use Perish Song, but unexpectedly uses Pain Split in the middle of the battle. Celebi ends up dying, instead of fainting, but Pikachu pulls out one more move before he dies as well, Destiny Bond.
Red appears, but his head is gone, and the trainer is sent back to the overworld. All that's left of the trainer on his profile is a head, with no eyes, and his badge count has shot up to 40. His unknown now spell out NOMORE.
The author makes the trainer glide around his room, as the sprite has no animation, and finds that he can't interact with anything. He goes downstairs, finding the trainer's mother is missing, and goes outside to a white void. He keeps walking, finding another trainer sprite who tells him "goodbye forever" before a mystery person uses Nightmare.
The trainer is sent back to the tiny room surrounded by graves, with the unknown spelling IMDEAD.
This is when the realization hits the author that the trainer is dead, and has been dead throughout the entire game. Not even resetting the game could bring him back to life.
Someone eventually made a playable game based off of this creepypasta, and the author returned at a later date to tell what happens when you picked no on the TURN BACK NOW sign. Though this option is, I think, exclusive to the game version.
While these are two different creepypastas, I'm pairing them together as they are both about Rugrats and also relatively short.
I should warn that Chuckie's Mom includes Chuckie having a seizure and themes of parental death, and Dil's Origin deals with the stillborn death of a newborn and the death of an infant due to neglect.
So, let's get started with Chuckie's Mom.
This story starts out claiming that there was to be an alternate version of Rugrats at some point with more adult jokes and humor, dubbed Rugrascals. A pilot was made, but it was decided that it was too disturbing, it never aired and was eventually lost to obscurity.
Somehow, a tv station in New Zealand ended up with a copy of the Rugrascals pilot, and played it during daytime tv hours thinking it was a regular episode.
Reportedly, the intro sequence was the same as Rugrats, and froze on the last frame of the milk landing on the screen. (Probably as a placeholder, this is never specified in the story but it would be believable.)
The pilot itself starts with the babies in the playpen, talking about their moms, and Chuckie has a nightmarish flashback. He's in the hospital, standing next to his mother while she sings to him. Everything seems normal until his mother starts singing backwards, and Chuckie is shown in front of live action footage of a chicken getting its head cut off.
Chuckie can only scream and turn away, but when he looks back his mother has a live-action mouth (much like Clutch-Cargo, I can imagine) and says in a man's voice "Don't worry Chuckie, it's time for me to move on."
Afterwards, several more disturbing scenes are shown such as a cow walking into a slaughter house, footage of the L.A. Roits, violent cartoons and, to quote the story "actual footage of a man suffering from AIDS being killed." Chuckie can be heard screaming over the footage the entire time. It cuts back to his mother, now with a chicken beak in place of her mouth, who asks him "Don't you remember where it all started?"
About a minute long clip of "child birth sonograms" (I think the author might have meant an ultrasound of a fetus) plays, with his mother chiming in with "Aren't you a lucky ducky, Chuckie?" and out of nowhere a harlequin fetus appears.
We cut back to the playpen, Chuckie is having a seizure, presumably due to his traumatic flashback, and the other babies are crying, having no idea what is happening to their friend. A paramedic arrives and starts trying to break Chuckie out of it, which Chuckie does after he coughs up blood and vomits.
We then see the paramedic and the other babies from Chuckie's point of view, all of them have photos of chicken beaks on their mouths and are clucking.
The episode ends with a zoom in on what I can only assume is a photoshopped image of a child made to look like Chuckie screaming.
The station went off air for 15 minutes after the credits rolled, with nothing but static. The author states that many children saw this broadcast incident, and that they are the only one who has ever spoken up about it.
Side note: maybe it's just me but I remember there being an extra scene where the paramedic explains to Chuckie's father that Chuckie is developing the same illness that his mother died from, and that he only has weeks to live. But maybe I'm either confusing this with The Rugrats Theory or another creepypasta.
Anyway, as a personal note, I think this pasta in particular was part of my inspiration to write Little Bear and the Big Red Book.
Now let's move on to Dil's Origin.
This one starts out with the typical "I was an intern" plot line, though the author is a janitor instead. But he doesn't seem to be too bothered by it. On one fateful day he was told there was a light out in "The Vault" and he was eager to see what all was in there. Upon placing the light, he does some exploring of "The Vault" (which he describes as more of a walk in closet) and finds that most of what is there were film reels of unfinished shows or shows that didn't make the cut.
He also finds a box with some flash drives in them, and finds one labeled Crybaby Lane (more on that one later) and one labeled Rugrats-Dil. With no regard to how it will affect his job, he slips the Rugrats drive in his pocket and continues about his day, planning to return it the next morning.
The drive contained only a single .avi file that was a short animation.
It opened without a title sequence, and was in the same style as the 1999 movie. The Pickles' house was dark and dusty, with the windows boarded up. Tommy was seen sitting in his high-chair with his head on the tray, emaciated, clearly having not eaten for quite a while.
It cut to the living room, though in between the scene-switch there was a strange sepia-tone shot of four adults dressed as the four main Rugrat's babies, with "Chuckie" pointing at the screen. I don't know where this image comes from, but to me it looks like some sort of low-budget play or live-action parody of some sort.
Didi was sitting in a rocking chair, crying and singing to whatever she's holding wrapped up in a blanket. To the author's horror, the shot pans behind her to show a shriveled up harlequin fetus (another one?) with a white crust of spoiled milk around its mouth. Didi is trying in vain to "feed" the fetus with an empty bottle. The credits sequence played, but the regular theme was slowed a bit and the text was in Cyrillic. (Why do people always try to make Cyrillic text scary?)
The author takes the drive back that next morning, just like he planned, and decided to never speak of what he saw. Though, at the end of the day, a staff member pulled him aside and revealed that they somehow knew that he had taken that specific drive. Instead of firing or reprimanding him, probably thinking that seeing the episode may have been punishment enough, they tell them the backstory of why the episode was made.
Back in the 90s era of the show, there was a writer on the team that the staff member only referred to as Susan. Susan was married with a young child and another on the way, and took leave to care for her soon-to-come newborn. Sadly, the baby was stillborn, and her husband left her over the resulting trauma.
After weeks of no contact with her, the other staff called for a welfare check. What the police found was horrific, set up much like the scene in the episode. However, Susan had passed away by the time the police found her, as did her infant son, who had been dead long enough that the state they found him in is...a bit too gross for me to describe here.
The episode on the flash drive was the last thing she had ever written, and also animated herself, before she took her leave. Which leaves not only a lot of questions as to how she knew what would become of her, her infant son, and unborn child, but also the question of why this led to the creation of Dil. Though I guess introducing Dil was probably a way to honor her memory, which is nice to think about.
The author worked at the studio for a few more years and eventually got a new job somewhere else, but he never touched the vault again.
