Hey there, folks! Games like Little Nightmares are the ones that break my heart the most. You see that gorgeous box art, hear the hype, and think, “Oh man, I’m gonna fall head over heels for this the second I start playing.” Then you boot it up, and… oof, it’s a letdown that hits like a ton of bricks. Honestly, it stings, and this game left me more frustrated than fulfilled.
Now, before you grab your pitchforks over the score I’m about to slap on this thing, stick with me, dear reader. I’ve got some solid reasons why this game didn’t live up to the hype, and I bet you’ll nod along once I break it down. So, let’s dive in!
1. Story
The story here is a bit of a cryptic puzzle. There’s no dialogue—just a cinematic vibe where the environment tells the tale. You’re supposed to piece it together like some artsy jigsaw as you creep through the world. I haven’t touched the sequel yet, so I’m not 100% sure how deep my grasp of this universe is, but I’ll give it this: the story’s pretty cool. Well, almost. Here’s the catch—I only figured out what the hell was going on after watching an explanation video post-credits. Seriously, I’m wandering around, jaw dropped at all the wild stuff happening, but I’ve got no clue what it means. The eerie locations and freaky monster-things gave me some guesses that panned out, sure, but for most of the game, I couldn’t care about the story—or rather, it didn’t give me a reason to. It’s a shame, because there’s something fascinating buried in there.
2. Technical Details
Buckle up, because this is where it gets ugly. Little Nightmares is a technical disaster—hands down the biggest trainwreck I’ve seen in a while. It’s like I’m trying to run an unreleased GTA 6 on my Nintendo Switch. Who ported this mess? And how did the testers not go, “Uh, guys, this is broken—maybe don’t release it”? I’m still in shock. The controls? Unresponsive as hell. The loading screens? Agonizingly long. Half my playtime was spent staring at that dull screen, wondering, “What are you even loading, dude? What are we waiting for?” Sure, it’s polished on the outside—stunning graphics, killer art direction—but those technical hiccups made it feel like a slog. I was so excited when this game got announced, but man, these flaws sucked the joy right out.
3. Gameplay
Gameplay-wise, it’s your standard “solve a puzzle, hop some platforms” deal. I didn’t expect much depth here—most games like this don’t deliver that—and I wasn’t crushed when it turned out as predicted. But oh boy, does it have issues. The perspective problems are a nightmare (pun intended). I get it, 3D platformers often struggle with this, but here’s the kicker: every little misstep—thanks to clunky controls or bad angles—sends you straight back to that godforsaken loading screen. One wrong jump, and you’re stuck twiddling your thumbs for minutes. I’m not asking for Mario-tier platforming, but come on, devs—a little effort? A shadow indicator under my jumps could’ve saved so much grief. Without those sluggish controls and constant deaths, I could’ve breezed through this in 1.5-2 hours instead of the 5 it took me (and that’s being generous).
4. In Summary
Here’s the deal: Little Nightmares is a technical mess wrapped in a gorgeous package. The art design, music, and atmosphere? Absolutely breathtaking. I’m fascinated by this eerie world, no question. But those long loading screens, unresponsive controls, and perspective issues turned my excitement into frustration. This game’s short—clocking in at 4-5 hours—but it felt like a struggle I nearly quit halfway through. Without all the tech garbage, it could’ve been a tight 2-hour gem. Instead, it’s clear the devs rushed it out the door, leaving us with something average at best, disappointing at worst. The stunning visuals and creepy vibes got drowned out by the flaws, and that bums me out. Final score? A grudging 4.5 out of 10. I might give the sequel a shot someday, but after this letdown, I’m in no hurry.
Final Score: 4.5/10