 Glitches in video games are super common. Every game has their own glitches or bugs. Some are hard to find, while some are very easy to find. You can say that about Roblox too. The problem with Roblox glitches is that Roblox is a user-generated platform, meaning if there is a glitch, it's usually the game developers fault rather than the Roblox client. But what if I told you there is one, a glitch so rare, that there are only two reports of it ever? So what is this so-called glitch? Well, what would happen is that the client would suddenly have a greenish tint to it. It's really hard to notice at first, but over time the green tint becomes stronger and stronger, to the point that the whole thing is just green. If you think that's the only problem with it, then you're super wrong. A horrible screech would play. The screech was rumored to be so loud that it could break computer speakers. But how did people discover this glitch? Well, a user by the name of JWIO3982MM posted a forum post on December 15, 2010. In his post, he described this weird glitch, then he proceeded by asking forum users what caused this glitch. Most people on the forum thought it was either a 1x1x1x1 return, or a script put in the game that just scared players. Two years later, on the same day, another user posted a forum post about the same glitch. Forum users replied with dumb theories about how this happened, but none of them were proven true. Now how can we prove that this was a client glitch and not a script made to scare users? In 2016, a group of users noticed these two forum posts, and decided to find a way to replicate this bug. They went into the 2016 client code and found nothing. They found a 2010 client. After using some programs to get into the code, they found one piece of code that looked like it could activate this bug. That's odd. Why would a game company purposely put a bug in their own game? They tested to see if this was the right code, and it was. They decided to remove it to see what would happen, and when they got into the game and tested it, it happened again. There was no code to trigger this bug, but it still happened anyway. They went back into the code and saw that the code was back. They removed the code again and the same thing happened. But when they checked the code again, they saw a comment that was added in the code that just said, in all capital letters, stopped it. The group decided to stop messing around with the client code and disbanded straight away after this incident. Nobody still knows why this glitch exists or how it happens. Nobody knows who the people in the group who messed around with the code in 2016. Nobody knows what happened to the two forum users that got this glitch. But one thing we do know is that it's definitely not a code made by the original developers, but why does it only happen to the 2010 clients? Why did the glitch seemingly disappear after 2012? You would expect there to be more reports about this bug, but there aren't just those two forum posts. We may never know how this glitch happened or who is messing with the 2010 client code.