Obscure Game Bug Trivia Crashes Oblivion
Description
A screenshot of a Twitter thread. The top tweet, by user "Kiro | Pre-debut Vtuber IT", responds to a question from "Aaron & Tommy: Super Po..." which asks, "What is the most useless piece of video game knowledge you know?". Kiro's answer details a hyper-specific bug in the game "The Elder Scrolls IV: Oblivion," stating that if a player adds bread to the inventory of an NPC named Salmo the Baker, he will attempt to eat it at an inn, causing the game to crash. The tweet is illustrated with two in-game images: a close-up of the character Salmo's face and a 3D model of a loaf of bread. This meme appeals to developers by highlighting the absurdly specific and often hilarious nature of software bugs, especially in complex systems like open-world games. It's a perfect example of an edge case that likely slipped through QA, resonating with anyone who has ever discovered or caused a bizarre, unreproducible bug
Comments
13Comment deleted
This is why QA needs a 'chaotic evil' test suite: `assertNotCrashes(npc, BREAD_OF_DOOM)`. Some bugs aren't found, they're achieved
Slip one loaf into Salmo’s inventory, the AI calls take_bite(), derefs a null crumb pointer, and the whole engine faceplants - the Tamriel equivalent of adding a new enum value without updating the switch
This is the gaming equivalent of discovering that adding a semicolon to line 4,827 of your legacy codebase causes the entire authentication system to interpret all passwords as 'admin123' - completely inexplicable, utterly reproducible, and the kind of edge case that makes you question whether deterministic computing is just an elaborate lie we tell ourselves
This is the software equivalent of discovering that your distributed system crashes when a specific user named 'Salmo' receives a message containing the word 'bread' - perfectly reproducible, completely absurd, and somehow makes it to production. It's a beautiful reminder that no matter how sophisticated your state machine, there's always that one edge case where giving an NPC carbs triggers a segfault. The real question is: how many sprints would it take your team to prioritize fixing a bug that requires players to deliberately sabotage a baker's diet?
Insert(bread) -> pathfindTo(inn) -> bite() -> nullptr; the only pipeline where a missing crumb brings down the whole stack
Turns out “give NPC bread” is an end‑to‑end fuzz test - consumption reenters the AI while it iterates inventory, invalidates the iterator, and Oblivion eats a null pointer for dessert
Infinite bread exploit meets unhandled NPC bite: Oblivion's elegant stack overflow via crumbs
Oblivion is an eternal game Comment deleted
No one said it's great, but it's forever in our hearts (for many reasons) Comment deleted
A good one, actually (but I'm in an annoying fan mode) Comment deleted
That's still so weird to me, honestly. Like, why, don't NPC's eat bread all the time? Why does this specific instance crash the game? Comment deleted
you shouldn't give the baker a piece of bread Comment deleted
Не's a He's a gluten intolerant. Comment deleted