Every video game has at least one odd little wrinkle. Maybe the jump feels floaty. Maybe the inventory menu looks like it was organized by a raccoon with a spreadsheet. Maybe an NPC walks directly into a wall while delivering a speech about destiny. Fine. Games are complicated. They are enormous haunted houses made of code, art, deadlines, coffee, and increasingly desperate Slack messages.
But then there are the design choices that go beyond “quirky” and sprint headfirst into “how did this survive a meeting?” These are not tiny bugs or one-off glitches. These are core decisions: mechanics, systems, endings, or monetization ideas that made players put down the controller, stare into the middle distance, and quietly ask whether anyone in the room had tried playing the game for more than eleven minutes.
This article looks at five infamous video game design choices that became notorious because they broke immersion, undercut player trust, or turned simple fun into digital dental work. The goal is not to dunk on developers, who often work under brutal time pressure, shifting publisher demands, and technical chaos. Instead, it is to analyze why these choices felt so baffling, why players reacted so strongly, and what modern game design can learn from them.
1. Superman 64 Turned the Man of Steel Into a Flying DMV Test
Few games are as permanently attached to the phrase “bad video game design” as Superman: The New Superman Adventures, better known as Superman 64. On paper, the pitch sounds impossible to ruin. You are Superman. You can fly, punch robots, use superpowers, rescue people, and generally behave like a one-man emergency response department wearing a cape.
And yet the game’s most memorable activity is flying through rings. Not one dramatic ring. Not a clever tutorial ring. Rings upon rings, floating in a foggy version of Metropolis that looks less like a city and more like Superman got trapped inside a bowl of pea soup.
Why It Was So Confusing
The strangest part is not merely that the game included ring challenges. Flight challenges can work. Pilotwings made aerial precision fun. Racing games use checkpoints all the time. The problem was that Superman 64 took one of the most powerful fictional characters in pop culture and designed his main gameplay loop around the least heroic fantasy imaginable: commuting through floating hoops under a time limit.
Superman should feel fast, strong, and free. Instead, the player wrestled with stiff controls, short draw distance, awkward combat, and repetitive objectives. The fantasy of being Superman collapsed because the mechanics kept reminding you that you were not saving Metropolisyou were failing a cosmic agility course designed by Lex Luthor after reading a traffic safety pamphlet.
The Design Lesson
A licensed game has to understand the fantasy at the heart of the character. Batman should make players feel clever and intimidating. Spider-Man should make movement itself exciting. Superman should feel powerful but morally constrained. Superman 64 accidentally made him feel like a balloon animal with homework.
The lesson for game designers is simple: mechanics are not neutral. A task can be technically playable and still be emotionally wrong. If the core activity fights the player’s expectation of the character, the whole game starts to feel like a prank.
2. Doom 3 Made Players Choose Between Seeing and Shooting
Doom 3 is a fascinating case because the controversial design choice was intentional, thematic, and defensible. The game shifted the classic Doom formula from high-speed demon demolition to slower survival horror. Darkness became part of the experience. Monsters jumped out of shadows. Hallways felt dangerous. The atmosphere was thick enough to spread on toast.
Then came the flashlight.
In the original release, players could not use a flashlight and a weapon at the same time. You could either see the demon or shoot the demon, but not both. This created tension, yes. It also created the mental image of a futuristic Mars marine who could operate plasma weapons but had never encountered duct tape.
Why It Became a Meme
The idea had merit: force the player to make a scary choice. But the mechanic often felt less like horror and more like artificial inconvenience. Players were not thinking, “I am vulnerable in a terrifying environment.” They were thinking, “My character is apparently the only person on Mars who cannot hold two objects.”
The community responded with the famous Duct Tape mod, which attached flashlights to weapons. That reaction says a lot. When players immediately create a fix for a core mechanic, they are not just complaining; they are voting with design instincts of their own.
The Design Lesson
Friction is powerful when it supports emotion. Limited ammo, fragile weapons, slow reloads, and restricted visibility can all deepen tension. But friction becomes annoying when players perceive it as illogical. A mechanic can be scary, but it still needs to feel believable inside the game world.
Doom 3 remains beloved by many horror fans, and its flashlight debate is still interesting because neither side is completely wrong. The “WTF” factor comes from how thin the line is between “brilliant tension” and “why is my space marine losing a fight to basic hand coordination?”
3. Mass Effect 3 Made Years of Choices Feel Like a Color Picker
The Mass Effect trilogy built its identity on choice. Players carried decisions across three games. They saved or sacrificed characters. They brokered peace, doomed species, romanced crewmates, shaped Commander Shepard’s morality, and spent dozens of hours believing that the galaxy was responding to their actions.
Then the original ending of Mass Effect 3 arrived, and many fans felt as if the series had taken their enormous decision tree and fed it into a vending machine labeled red, blue, and green.
Why Players Felt Betrayed
The backlash was not just about wanting a happier ending. Tragedy can work. Ambiguity can work. Sacrifice can absolutely work. The problem was expectation management. The trilogy had trained players to believe that accumulated choices mattered in visible, specific ways. The ending, in its original form, seemed to compress that long investment into a small set of abstract final options with limited closure.
BioWare later released the free Extended Cut, which added cinematics, epilogue scenes, and more explanation. That helped many players, but it also confirmed the core issue: the original ending had not given enough emotional or narrative feedback for a series built around consequence.
The Design Lesson
Choice-based games create a contract with the player. The more a game says “your decisions matter,” the more carefully it must show how they matter. This does not mean every decision needs a wildly different cinematic ending. It does mean players need to feel seen by the story.
When a game asks for 100 hours of emotional investment, the ending cannot feel like a software license agreement with mood lighting. The final moments need to acknowledge the journey, not just resolve the plot.
4. Metal Gear Survive Charged for Extra Save Slots
There are bad design choices, and then there are choices that sound like a joke invented by someone trying to parody modern monetization. Metal Gear Survive launched with microtransactions, including a system where players who wanted an additional character save slot had to spend premium in-game currency.
Yes, an extra save slot. Not a fancy costume. Not a big expansion. Not a pet robot that follows you around playing jazz flute. A save slot.
Why It Hit a Nerve
Players are used to controversial monetization in games: skins, battle passes, boosters, loot boxes, deluxe editions, founder packs, and other wallet-shaped confetti cannons. But save files occupy a different psychological category. They feel basic. They feel like infrastructure. Charging for them makes players feel as if the game is renting them a drawer in their own house.
The reaction was especially sharp because Metal Gear Survive already existed under a cloud. It was the first major Metal Gear release after Hideo Kojima’s departure from Konami, and fans were already skeptical. Adding paid save slots was like walking into a tense family dinner and opening with, “Who wants to discuss subscription-based forks?”
The Design Lesson
Monetization must respect player trust. Even when a system is technically optional, it can still damage perception if it appears to charge for something players consider standard. The more basic the feature, the more dangerous it is to monetize.
Players may tolerate paying for meaningful content. They may even enjoy cosmetics when the pricing feels fair. But when a game charges for convenience that used to be assumed, the business model starts to feel like the final boss.
5. Cyberpunk 2077’s Launch Police System Broke the Open-World Illusion
Cyberpunk 2077 has changed dramatically since launch. Updates, expansions, and major system overhauls have helped the game recover its reputation and become much closer to the ambitious RPG many players hoped for. But at launch, one design issue became symbolic of the whole troubled release: the police system.
In a believable open world, police response is part of the simulation. Commit a crime, and the city should react. Officers should pursue, escalate, coordinate, and create pressure. At launch, players frequently found that police could appear almost instantly near the player, sometimes in ways that felt less like law enforcement and more like supernatural guilt ghosts with badges.
Why It Felt So Bad
The issue was not simply that the police were too hard or too easy. It was that the system damaged the illusion of Night City as a living place. Open-world games rely on cause and effect. If the city’s response feels fake, the world begins to look like a stage set. The buildings are beautiful, the neon is gorgeous, the atmosphere is strongbut the moment the cops materialize like angry magicians, immersion takes a flying motorcycle off a cliff.
Later updates overhauled the police system, adding improved AI, vehicle combat, chases, threat escalation, and more believable responses. That improvement shows how important the system was. It was not a minor side feature; it was a key part of making Night City feel reactive.
The Design Lesson
Open-world design depends on consistency. Players will forgive abstraction if the rules feel stable. They will forgive limitations if the game communicates them clearly. But when a system appears to cheat, the player stops role-playing and starts testing the seams.
A city does not need infinite realism. It needs convincing behavior. If players can predict the rules and believe the consequences, the world feels alive. If enemies spawn out of nowhere, the world feels like a haunted spreadsheet.
Why Do These Choices Make It Into Finished Games?
It is tempting to imagine a room full of developers approving these decisions with villainous laughter, but reality is usually messier. Bad game design choices often survive because of deadlines, technical limitations, budget cuts, publisher pressure, late-stage pivots, or simple tunnel vision.
When a team works on a game for years, they can become accustomed to systems that new players immediately find bizarre. A mechanic that feels normal internally may feel absurd to someone encountering it fresh. This is why external playtesting matters. It is also why developers need honest feedback loops where people can say, “This is not working,” without being treated like they kicked a sacred cow.
Another common problem is design debt. A questionable system may start as a placeholder, then become too expensive to replace. By the time everyone agrees it is bad, the game is six months from launch, the animation pipeline is on fire, and someone has just discovered that the inventory menu breaks if the player owns too many hats.
What Modern Games Can Learn From These WTF Moments
The funniest bad design choices are often funny because they reveal a serious truth. Players do not judge systems in isolation. They judge how systems support fantasy, fairness, trust, and flow.
Superman 64 shows that mechanics must match the promise of the character. Doom 3 shows that tension must feel intentional rather than awkward. Mass Effect 3 shows that narrative payoff must honor player investment. Metal Gear Survive shows that monetization can turn neutral features into public relations disasters. Cyberpunk 2077 shows that open worlds need believable reactions, not just beautiful scenery.
Great game design does not mean every system is realistic. It means every system makes sense within the experience. Mario can eat a flower and throw fireballs because the world is built around playful nonsense. A space marine who cannot tape a flashlight to a gun feels strange because the world is otherwise asking to be taken seriously. Context is king. Consistency is queen. Playtesting is the exhausted royal adviser begging everyone to reconsider the ring level.
Player Experience: What These Design Choices Feel Like in Real Life
The most memorable WTF video game design choices usually do not annoy players all at once. They begin as tiny doubts. At first, you assume you are missing something. Maybe there is a better control option. Maybe the tutorial skipped a detail. Maybe the save slot menu is hiding another button. Maybe the police are supposed to appear behind you because Night City has invented teleporting law enforcement and forgot to mention it in the lore.
Then the doubt becomes testing. Players start poking the system. They repeat the same action to see whether the result changes. They commit a small crime in Cyberpunk 2077 and look behind them. They try to use the flashlight and shotgun together in Doom 3. They replay the ending of Mass Effect 3 and wonder whether a hidden variable will make the galaxy acknowledge their choices more clearly. This is the moment immersion breaks. The player stops living inside the game and starts auditing it.
That shift matters. Games are at their best when players think in verbs that belong to the world: explore, fight, sneak, rescue, negotiate, survive. Bad design forces players into outside-the-world verbs: tolerate, workaround, reload, Google, complain, mod. Once a player starts asking, “Why did they build it this way?” the spell is already cracked.
Anyone who has played games for years has a personal museum of these moments. The escort character who walks slower than your run speed but faster than your walk speed. The boss fight with an unskippable cutscene before every retry. The stealth mission in a game that has spent 20 hours teaching you to solve problems with explosions. The crafting system that requires twelve menus, three currencies, and the emotional patience of a monk. These experiences stick because they make the player feel disrespected, even when that was never the developer’s intent.
On the other hand, a flawed design choice can become part of a game’s identity. Some players genuinely defend Doom 3’s flashlight because it creates panic. Some fans can laugh about Superman 64 because its ring obsession became legendary. Even controversy can become cultural memory. The danger is that “memorable” is not the same as “good.” A burnt dinner is also memorable, but nobody asks for the smoke alarm tasting menu twice.
The best lesson for players and developers is empathy in both directions. Players are right to criticize systems that waste time, break promises, or feel exploitative. Developers are also working inside constraints most players never see. The useful conversation lives between those truths. A bad mechanic is not always proof of laziness. Sometimes it is proof of a deadline, a compromise, or a design goal that sounded better in a meeting than it felt in a living room.
Ultimately, these WTF choices are valuable because they clarify what players actually care about. They want control that matches the fantasy. They want challenge that feels fair. They want endings that respect investment. They want monetization that does not treat basic features like luxury items. And above all, they want to believe the game is on their side, even when it is trying to kill them with demons, robots, aliens, or a truly unreasonable number of floating rings.
Conclusion
Bad video game design choices are more than internet punchlines. They are case studies in expectation, trust, and player psychology. A strange mechanic can become infamous when it clashes with the fantasy, interrupts flow, or makes players feel that the game is wasting their time. The five examples above became notorious because they were not hidden in obscure corners; they sat near the center of the experience, waving cheerfully like design gremlins in a spotlight.
For developers, the takeaway is clear: test the fantasy, not just the function. For players, these moments are reminders that even beloved games are fragile magic tricks. When the design works, we see worlds. When it fails, we see the wires, the fog, the rings, and occasionally a police officer spawning behind us on a roof.