Bugs/glitches...
category: general [glöplog]
I was thinking and I wondered what is a term for a "positive" bug?
Remember the game "Super Mario Bros. 1". The 100 lives trick. This is by definition a "bug" in the game. And ONE (and not the only) definition of a bug is "something a program does that is not intented to do". But as it turned out, this "bug" in Super Mario turned out to be one of the must popular feature of the game. For me, I was pretty young and helped me ALOT in finishing the game. (Note: It's DEFINITLY NOT an easter egg as I read one interview with the or one of the original programmers, and he said when they reported it he was scared dead)
So for the context of this site, what if you coded a demo and when presented at a party there was a glitch/bug that actually created a stunning effect. And thus making you win first place. The chances of happening must be close to none but... Could we call this a "bug"? A bug has a VERY negative meaning and must be corrected.
Anyways how can we call a positive "bug"??
Remember the game "Super Mario Bros. 1". The 100 lives trick. This is by definition a "bug" in the game. And ONE (and not the only) definition of a bug is "something a program does that is not intented to do". But as it turned out, this "bug" in Super Mario turned out to be one of the must popular feature of the game. For me, I was pretty young and helped me ALOT in finishing the game. (Note: It's DEFINITLY NOT an easter egg as I read one interview with the or one of the original programmers, and he said when they reported it he was scared dead)
So for the context of this site, what if you coded a demo and when presented at a party there was a glitch/bug that actually created a stunning effect. And thus making you win first place. The chances of happening must be close to none but... Could we call this a "bug"? A bug has a VERY negative meaning and must be corrected.
Anyways how can we call a positive "bug"??
"in dolby surround"
Passing of bugs as features was quite popular back in the NES days. Back then, it was more common to say "hey, this bug is screwing up our gameplay, but it makes it even more fun!" than it is now (this was particularly the case in the first Metroid games).
I've coded several heavily bugged GFX effects which turned out to look way better than the "proper" versions, and I'm sure a whole lot of others have too, especially in the scene. ;)
I've coded several heavily bugged GFX effects which turned out to look way better than the "proper" versions, and I'm sure a whole lot of others have too, especially in the scene. ;)
the whole idea of democoding is to code bugs until one of them behaves in a pleasuring way, then you release the demo.
quote of the year.
Decipher: True! :) Unintended behavior in hardware is the staple of 8-bit coding in many ways :)
Quote:
Unintended behavior in hardware is the staple of 8-bit coding in many ways :)
alright.. I call it "8-bug"
one thing that springs to mind, although it's not technically a bug: the original video of the mfx demo Inflorescence had awesome video compression glitches that somehow enhanced the demo :)
(Actually, I guess under that you could also count all the demos that were quite shit, but looked much better on a low quality party stream ;)
(Actually, I guess under that you could also count all the demos that were quite shit, but looked much better on a low quality party stream ;)
If it's not a bug then it's a gub.
Quote:
one thing that springs to mind, although it's not technically a bug: the original video of the mfx demo Inflorescence had awesome video compression glitches that somehow enhanced the demo :)
Reminds me of the 3state intro Antimoney, that was running in some weird colour mode on my old ati. Years later, I thought seeing it in b/w was the bug, until someone told me that this was the original intention. I still think it looked better in colour. :)
