Glitch

A Glitch (also known as a bug) is a fault in a program during runtime that causes it to function improperly.

The severity of glitches can vary. One glitch caused a player's username to appear as "null" immediately after login; another hard-to-find, yet serious bug allowed players to kill other players outside of the Wilderness. After the temporary release of RuneScape Classic in 2009, the "null" name glitch was still in effect.

Abuse of glitches, such as the World 111 Glitch that allowed players to attack other players outside of the Wilderness, is a severe offence that's punishable by a permanent ban under Rule 4 of the Code of Conduct.

Jagex has recommended that if a player finds a bug or glitch in RuneScape, the player should report it to Jagex immediately via the "Submit a Bug Report" interface on the RuneScape main page.

'''NOTE: All glitches listed on this page have been fixed by Jagex. Please do not list any glitches that have not been fixed yet.'''

World 111 Glitch
One infamous example of bug abuse was the World 111 Glitch - also called the World 111 Massacre or the Falador Massacre (after where the glitch occurred). On the day of 6 June 2006 (or 06/06/06, oddly enough) a player had a party at his house celebrating being the first player with level 99 Construction. He eventually expelled all of the guests because of major lag. There were massive amounts of people at the party, and when he expelled all of them, some say he overloaded the server, although this was not the reason. It was rather an error in the coding of the construction skill. Because he had not turned off PvP (player vs player) mode, those in the dungeon and fight arena were able to attack and kill any player anywhere. This resulted a PKing rampage that caused many deaths, the loss of items that Jagex could not replace, and the permanent banning of most participants. Although the player was not banned for the massacre, he was banned for real-world trading later on.. The reason Jagex could not replace the items lost was because many, many people claimed to have lost items, yet they had not even been logged on at the time.

Player Moderators tried to tell people to bank their items and 'glory' teleport but they were barely seen amongst the mass amount of followers.

This bug remained on RuneScape for about an hour and was fixed immediately after it became known to Jagex. The repercussions of this glitch are still being felt today, as some of those banned and/or killed owned rare items such as partyhats and other Discontinued rare items. The removal of the players meant the rare items were deleted also.

Chat Filter Glitch
This glitch could allow players to bypass the chat filter. When Alt Codes were introduced to the RuneScape chat system, specific Alt Codes allowed players to bypass the chat filter. When a certain Alt Code was typed in, it would register as a space to the chat filter but would not actually put a space in between the word itself. An example would be typing "Myspace" which normally would be blocked by putting My(Alt code)Space. So the chat filter registered it as My Space but appeared as MySpace. By doing this a player who spaced the letters out correctly could type anything without the filters blocking it. There was also a glitch in the chat filter which unblocked any word you could think of using alt key codes, this glitch had been fixed but recently surfaced once more.

μ Glitch
Another famous glitch would be the μ glitch. When a player pressed Alt+0181, the μ character was created (The Greek letter mu, used for the prefix "micro"). A player who typed in this character and actually said it would find that all nearby players including him/herself would be automatically logged out from RuneScape. Some players abused it horrifically in PVP worlds and Bounty Hunter to gain extremely unfair advantages, by putting their chat on "off" then saying the character μ. This would crash the other players, leaving the abuser to kill the other player with absolute ease. It was estimated that over 200 million coins were lost in the few hours the glitch was present. However, players could avoid the glitch by turning all chat filters to "Off". This glitch has now been fixed.



Noclip Glitch
In mid 2008, a bug known as the Noclip Glitch was discovered by a number of players. This bug gave them certain properties of "noclipping" (the ability to walk through walls) and performed many unusual bugs such as getting a level 3 player into the Legends' Guild. After months of the same few players being spotted in inaccessible areas, JaGeX finally patched it in 8 November. Most of the bug abusers who performed this bug are now banned, one has reportedly had his/her ban lifted recently but was banned again for continuing bug abuse.

Fight Pits Player Killing Glitch
During the first few hours after the new TzHaar look was released, while playing the TzHaar Fight Pit mini-game, players were able to attack other players who were waiting in the waiting room with magic or ranged attacks over the red barrier. This caused several players to lose their valuable items. Jagex moderators arrived almost immediately, disconnecting and subsequently banning anyone who abused the glitch.



POH Poison Glitch
Shortly after Construction was released a glitch was discovered, where players would go in the boxing ring and poison someone in it, the owner of the house would wait until the poisoned player was almost dead, then expel them from the house. The poison would remain and the player would die, losing their gear.

Player (level: 1) Glitch


In the house containing the Customs Sergeant in Rimmington, one could right click the floor by the sergeant to see an invisible level 1 'Player', which gives you an examine option saying "Invisible player". This glitch was fixed during a patch in May 2009. This also seems to occur when you summon the magic elemental game in a Player owned house.

Monster Death Glitch
This glitch often involved the deaths of monsters that were killed while fighting players, but could also happen in areas with high mortality rates, such as Castle Wars. The glitch made the monster, or player, appear in the 'prone' (dead) position (after death for monsters, randomly for ordinary players). The 'dead' monster could still move, attack, etc. from the prone position while players could train skills, etc. It has also happened a few times at Bounty Hunter. This glitch was not sighted very often as it was considered highly uncommon. This Glitch also has happened in the Fist of Guthix minigame, the Duel Arena, Earth warriors and the Rock Crabs in Relleka.

Party hat duplication glitch
The glitch was not an attempt to duplicate items. A player had been experimenting with RuneScape by using a third-party program called AutoRune in an attempt to simply trade the scythe. Although the player never managed to trade the scythe, he did discover how to create any non-stackable item. Therefore, the glitch did not duplicate existing items, but instead created new ones. The use of any such third party software to gain any advantage was, of course, against the rules of RuneScape.

The glitch was performed by trading with a player, and then using AutoRune to enter the numerical value that corresponded with a certain non-stackable item to have an item pop up and be traded to the other person. For example, the number for the Rune 2-handed sword was 81, so that value would be entered into AutoRune and the player who was trading with the player using AutoRune would be able to receive that item.

In his excitement, the experimenter revealed to very few people how to execute the glitch. These players then duplicated several items, the most expensive at the time: specifically a cracker with a present 'toy' of a purple partyhat, rune two-handed swords, and Dragon square shields. The most expensive item, the purple partyhat, was created most amongst them. That day, though, one of these people revealed that the glitch existed.

Jagex also offered life-time memberships to players that showed them how to do the duplication. Several players did this, but instead of a life-time membership, all they got were permanent IP bans.

Because of all of the purple partyhats created, Jagex was not able to find all of the offenders, thus it became the least expensive partyhat. With the advent of RuneScape 2, the name was changed from the generic "partyhat" that all of them carried to "purple partyhat."

This glitch has had a lasting effect on the economy. The purple partyhat was originally the most expensive partyhat in the game but, due to the large amount of them created they became, and remain, the least expensive. Unless Jagex injects a surplus of other colour party hats into the Grand Exchange, it is unlikely that the inflation caused can be reversed.

Blood Rune Duplication Glitch
This glitch allowed players to take blood runes out of the minigame Barbarian Assault and is commonly referred to as "The Blood Rune Dupe" even though it did not involve duplicating blood runes. The smuggled blood runes could then be sold to other players through trade or through the Grand Exchange. There has been multiple occurrences of players performing this glitch using different strategies and so Jagex finally fixed this bug completely by replacing the blood runes with elemental and catalytic runes in Barbarian Assault during June 2009. The players that abused this glitch all got permanent bans.

Item Highlight Glitch
This is a rather small glitch that can be made when a player drops an item then quickly clicks on it, as a result any other item that is put into the inventory space that the dropped item is in will be highlighted but with out the "use on" option (This is very difficult to do with a item that has a wield, bury, eat, or any other 4th option, but it is possible to do if you act fast by dropping the item then right clicking and very quickly clicking use.) It is impossible to do this with more then 1 item. With this glitch it is possible to have two items highlighted. At Blue Moon inn the table was called Mavis Grey, and when you put a beer there, it would be floating. This has not been fixed.

P.O.H. Bench Glitch
The POH bench Glitch was a very popular glitch among many concerning Construction. In this bug, the player was able to move while standing in a bench that is "cloned" by a player. However, walking, going down dungeons and trapdoors and the like of actions happens very slowly, and it would seem as though the player teleported to said area, or otherwise "slide" quickly to it.

Doing this glitch required the player to have food in their inventory, and sit on a Dining Room bench, then right-clicking the bench and select "remove", and immediately clicking the food several times to assure that the player has eaten it. The bench turns sideways, and having a servant and Bell-pull will be convenient if the player is not the house owner and the owner is in the house in a different room. The player rings the bell, summoning the servant and bringing the player to the room that the house owner is in. The player would then move in the bench.

Another part of the bench glitch was, while sitting in the glitched bench and wielding an item i.e. boxing gloves, and eating and equipping a new weapon really fast, the new weapon would be held the same way as the other weapon. The fix isn`t complete yet because if you equip, for example, a 2h sword, go sit on the bench and open up the equipment menu, you'll still be able to equip a new weapon which will be held the same way as the 2h sword. This appears only in the menu though.



P.O.H. Owner Glitch
The POH owner glitch was quite popular, mainly used in World 31 at house parties. If a player walked onto a trap in the dungeon of another players' house, then used Teleport to House, then trap would force them back into the other players house while still being registered as teleporting to their own house. While someone was 'owning' another house, players could still enter that person's original house. The glitched owner could also pick up and plant Wintumber trees, which resulted in Wintumber Tree duplication if two or more players tried to pick one up at the same time. If the owner of the house turned challenge mode off, the glitched owner could turn it on and attack people in the dungeon while being unattackable.

Construction Mode Party Glitch
The construction mode party glitch was not widely used. It consisted of a player in construction mode (and often an empty house) going into a combat ring and committing suicide via nitroglycerin or poison. The player would then spawn outside the ring and other players could enter the house. Many players didn't use this glitch because they thought other players would delete furniture from their house, although all items are perfectly safe.

Filtered usernames
Since Jagex's filter blocks some offensive language, naturally there were cases where there were loopholes. One of these loopholes, a very annoying one indeed, were the fact that some people's usernames were filtered as if they were a bad word. For example: "Puyo1" and "Xbith" might produce "**yo1" and "X****" respectivly. The name of some players would come out as asterisks, and would make communication for the players hard. Some of these were removed when Jagex updated the chat filter. Most of those cases were removed by that act, but some still remain. It is unknown if Jagex will do anything regarding it in the foreseeable future, but on the forums several mods have suggested it will be continually improved, and there is a thread where players can suggest words they think should/shouldn't be censored. This glitch has somewhat been fixed.



Adding glitch
After RuneScape's 8 July 2009 update there was a glitch were you could add yourself to your own Friends List by putting a space after the last letter of your name, or before the first. For example Ex1:"Jim" Then if you put "Jim_" "Jim" would have added himself, Jagex fixed this the next day after many players performed it. Players who added themselves during that first day did not have themselves removed though after Jagex's update. The same thing could also been performed to add yourself to your own ignore list, this was also fixed at the same time. Due to a recent update, players logged into RuneScape only to find "Changes will take affect on your clan in 60 seconds" and their usernames removed from their own friends list. It's no longer possible to re-create this glitch. When RuneScape added the Display Name Update on 1 October, you could add yourself to your friends list again if you had changed your name,this time by selecting "Add Friend" and typing your old username in. Although when logging back into RuneScape your name would have been removed.

Sometime in October when the display names came out, the glitch became available again. If you were a member and had changed your display name, you could have added your old name to your friends list and sent a private message to yourself. Whenever you logged out, it would also remove it automatically. This glitch was fixed sometime in October recently after the update.

In December this glitch was possible to do in runescape classic, but it is unknown if it has been fixed yet.

Game engine update glitch
On 9 June 2009, numerous glitches were found in the game after Jagex has changed the game's engine. During that time players could attack all monsters and these would not return with any sort of damage, including the greatest of bosses like Corporeal beast, or even the simple ones like Goblins. This also included non-responsive NPC's such as bankers and random events, which left players stranded inside random events such as the Sandwich Lady and Giles/Niles/Miles. The glitches were fixed a few hours after it has been confirmed by Jagex.

Right click box glitch
After the RuneTek5 update, if a player right-clicked anywhere on the page, and kept walking until a new section of the map loaded, (Loading... Please wait) instead of the Right click box disappearing, all the options were removed but the right click box remained, with the exception of "Cancel". This has now been fixed.



Empty box glitch
In October 2009, if a player accessed details on certain quests, such as Dragon Slayer, from the quest list, when they closed the quest details all the quests would disappear. This glitch was fixed.

Null item glitch
Somewhere in 2009 a rare glitch occurred in where if you select an item, 'Null' appears. This is resolved by simply clicking on the item again. This glitch has been fixed.

However, this glitch is still possible by equipping an item and, immediately afterwards, right-clicking on the item.