top | item 20940341

Bugs That Became Features

94 points| xwenf | 6 years ago |birdeatsbug.com

72 comments

order
[+] liquidgecka|6 years ago|reply
1 is not even close to true. I was a Gmail SRE at the time. Sends did not take 5 seconds at the time, they were handed off to the MTA right away. The MTA had the ability to delay delivery due to other projects and Gmail decided to use that feature to build undo send.
[+] ajford|6 years ago|reply
Was gonna say, I remember that being a Gmail Labs feature for a while. I opted in the first time I noticed it in the labs, and I feel like it took a long while to reach the public.
[+] batuhanw|6 years ago|reply
What is MTA?
[+] doctoboggan|6 years ago|reply
One of my favorite bug to feature stories is hidden files in unix starting with a period. In unix the current directory is . and the previous directory is .. Early on those directories where simply hidden by not showing anything that started with a period. Quickly though people realized they could not show their own files simply by starting the filename with a period.
[+] cavanasm|6 years ago|reply
Really should have had skiing in Tribes on there. Holding down the jump button reduced friction to zero, so players could slide down hillsides at high speeds and launch themselves into the air by going over bumps. Every attempt at reviving the franchise has struggled with implenting skiing as a properly intentional feature, and not quite recaptured the magic.
[+] ru552|6 years ago|reply
Former comp tribes player reporting in.

Skiing didn’t work by holding the jump button though. You had to continuously jump while going down a hill to “ski”. This lead to players writing a script that continuously jumped and binding that to a button that was held to “ski”.

51504lyfe

[+] joshstrange|6 years ago|reply
Dear god... Starsiege: Tribes, now that's a name I haven't heard in years. I used to play this for hours at a time with friends. Now that I think about it, other than the Battle Royal stuff, it was a lot like Fortnite (or what I understand of Fortnite anyways). I loved the building, laying armor plates over laser cannons, flying over a wall only to get obliterated on the other side... Damn, now I want to see if I can still run that game and if anyone still plays...
[+] meowface|6 years ago|reply
And also everything in GunZ.
[+] ollybee|6 years ago|reply
They should add Nuclear Gandhi from the Civilization games as one of the most amusing examples of this.
[+] kabdib|6 years ago|reply
There was a similar bug in the Robotron 2084 arcade game; rather than rushing you, an arithmetic overflow would send some enemies to the far side of the screen, where they would continue to fire at you (and were much harder to hit). It was a bug that the developers liked so much that they kept it in.

Then there's the game Goat Simulator, where the developers promised to intentionally keep many bugs in the game, for amusement value. I think it worked well.

[+] directionless|6 years ago|reply
The Fog of War video game idiom predates both Silent Hill, and every platform it runs on.

I'm not really sure we should be touting the sexism in bust size as bug or feature here. It's mostly just sickening.

Deep Blue making a random move doesn't sound like a bug to me. Certainly not in the usual sense. It seems like a fairly reasonable choice, if no better one is presented.

[+] thanatropism|6 years ago|reply
> sickening

Game boobs are certainly cringeworthy and maybe symptomatic of a sexist worldview that's unfair and therefore, to use a trumpism, sad.

But if commercially-driven fanservice made out of pixels is sickening, what word have we got left for clitoris mutilation and burqas and other such uncomfortably extreme instances of oppression?

[+] bigmattystyles|6 years ago|reply
Correct - I've heard that's why Doom had so many double doors and sharp corners, to shorten the size / depth / view angle of what would need to be rendered. Completely agree with you on #2 as well - I'd go further, it sounds like an excuse you make when you wanted to do something but knew it wasn't normally justifiable. If that account is true, it's sad as well as plain sexist.
[+] stinos|6 years ago|reply
a software bug - when the machine did not know what to do, it made a random move

Depending on the specs that's not really a bug. I mean, it's not like "when the machine did not know what to do, it invoked undefined behavior"

[+] wodenokoto|6 years ago|reply
If the random move was invoked when an exception was caught, I think I can defend saying a bug saved the game, but the wording makes it sound like the machine did what it was supposed to and the Deep Blue team just godt lucky.
[+] growt|6 years ago|reply
My favourite story about a bug in a game is GTA. The police cars were supposed to stop you nicely by braking right in front of you. But a small bug cause the cops to crash into the players car at full speed. End of the story: they decided to keep the psycho cops.
[+] AdmiralAsshat|6 years ago|reply
I think maybe a few additional details should be mentioned.

1) GTA was originally envisioned as a racing game.[0] You would race against other players in inner-city settings, but this meant you could end up ramming other cars, running over pedestrians, etc. If that happened too many times, cops would pursue you.

2) The cops were supposed to come out and pursue you if you did too many bad things and, as you said, do it "gently". The bug in the cop AI, however, made them insanely aggressive to the point that they would also hit other cars, run over pedestrians, and cause just as much damage as the player in pursuit of pulling them over.

3) The devs thought the "psycho cops" were so hilarious that they didn't just keep them in--they reoriented the entire game around the concept of causing mayhem (rather than racing).

[0] https://www.engadget.com/2011/03/22/race-n-chase-original-gt...

[+] everdev|6 years ago|reply
A surprising amount of CSS development would probably fit the bill as well. So many times I've produced unexpected results that looked just as good or better than my original intent.
[+] asdfman123|6 years ago|reply
That's the whole artistic process though.

"Hey, wait a minute, that wrong note actually sounds really cool there. Let me try to build upon it."

[+] kiddico|6 years ago|reply
Sums up most of my experiences when I try web dev haha.

"Oooh that's neat... Not sure how I did it though."

[+] teilo|6 years ago|reply
Not a single one of these things is a bug. Design decisions, workarounds for hardware limitations, etc. But not bugs.
[+] pflenker|6 years ago|reply
I disagree. Without knowing the details, there is no way to know for sure if the source of the 5 second delay was an actual bug. And the way programs where written back then, the space invaders issue looks like an unintended bug which was then simply kept in.
[+] codezero|6 years ago|reply
My two favorite bugs that became features:

1. "true black" dyes in Ultima Online [0]

2. Skiing in the game Tribe [1]

[0] https://www.raphkoster.com/2010/11/24/how-uo-rares-were-born...

[1] https://tribes.fandom.com/wiki/Skiing

[*] wow, the numbering here is real confusing!

[+] mikorym|6 years ago|reply
Not to be prescriptive, but that is why I don't do the "hip" thing of numbering from 0.

The question of whether 0 is a natural number or not, is from a category theorist's point of view, rather quixotic. The category theorist in question would either say: "of course it is a natural number" or "of course it is immaterial".

The only situation in which one should panic, I think, is if the answer is "of course it is not a natural number". In this latter instance I think that you have a problem and that the ring theorist from the office next door has taken polyjuice potion and tied your professor up in the magical trunk, frow which you can probably by now hear feint moaning.

[+] kobbe|6 years ago|reply
1. Not necessarily a bug. Just slow software. 2. Not a bug. 3. A real stretch to call this a bug. 4. Seems lika a real bug without researching more. 5. Not a bug.
[+] johnmaguire2013|6 years ago|reply
I'm not exactly sure I'd call 4 a feature though either -- just dumb luck.

And from the reading, it sounds like this was intentional behavior: Make a random move if there is no clear good move.

[+] TeMPOraL|6 years ago|reply
4. absolutely does not sound like a bug at all. Making a random move if you don't know what to do is the obvious right thing to do.
[+] fitzroy|6 years ago|reply
When using ScreenSharing on the Mac, CMD + Tab used to switch between apps on the local Mac (like using any other app). Which means, to switch apps on the remote Mac, you needed to use the Dock or some other method.

Then at some point a few years ago, CMD + Tab changed to switching between apps on the remote Mac, which also makes sense since you're working on the remote computer. But then you need another way to switch out of ScreenSharing on the local Mac.

Then for a year or two, it seemed random which computer's app switcher you'd yet.

Now it seems to take into account whether an actual window on the remote computer has been given focus since switching over to ScreenSharing or not. I can't quite place the logic, but it seems to do what I expect most of the time now.

I have no idea which of these scenarios was actually the bug and which is/was the feature.

[+] weberc2|6 years ago|reply
Halo 2 had the bxr bug (sequence of the “b” button, the “x” button, and the right-trigger). If you executed the sequence with the right timing, aim, and proximity, it would immediately kill a nearby opponent (“b” triggered a melee which took down enemy shields, “x” cancelled the cooldown animation of the melee to begin the “reload” animation, and the right trigger would cancel the reload animation and shoot the opponent. Headshots on does with no shields were one-hit kills. This was a great bug because anyone could do it, but it required a lot of skill to execute. https://youtu.be/H8HtTQOXKA4

Superbouncing on the other hand was just annoying.

[+] sgarman|6 years ago|reply
The problem with bxr is the rest of the game, maps, modes, weapons etc were not balanced around the br one shotting people. As someone who used it frequently I was not a fan and it only felt fun when other people didn't know how to do it yet which is bad game design.
[+] weberc2|6 years ago|reply
*foes, not "does" (autocorrect / missed the edit window)
[+] mikorym|6 years ago|reply
I am glad Kasparov and Deep Blue is mentioned here. Kasparov still does active research in chess (and especially computer aided human chess). And all the while I was under the impression that chess had been "solved" in the 90's...
[+] wodenokoto|6 years ago|reply
Zelda 3, a link to the past on SNES has a coin room, known as Chris Houlihan's Room.

Basically what happens is if an exception is caught during a screen transition, instead of crashing the game, it will load this room.

I believe a lot of older games had something like this, in order to run for a very long time, which was usually demanded by console publishers.

https://zelda.fandom.com/wiki/Top_Secret_Room

[+] ASalazarMX|6 years ago|reply
A list of FIVE random, questionable bugs, I thought it was something more serious.

Well, speaking of bugs, the Skyrim Giant Space Program[1] is my favorite so far, probably because it caught me by surprise the first time. Your first giant encounter usually happens after you killed an actual dragon, the top predator. How tough could these guys be?

[1]https://www.youtube.com/watch?v=EWV9hSDXTkg

[+] arthurjj|6 years ago|reply
The DeepBlue one doesn't seem to be a bug to me. If multiple moves seem equally good then choosing one at random seems like a fine decision making process
[+] aledalgrande|6 years ago|reply
Add the PostIt by 3M to the list. Failed glue project.