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.

Abuse of such glitches, such as during the World 111 Glitch (which allowed players to attack other players outside of the Wilderness), is a severe offence 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 haven't been fixed yet.'''

=Famous Bugs/Glitches=

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 named "Cursed You" held a party at his house celebrating level 99 Construction. He eventually expelled all of the guests. There were massive amounts of people at the party, and when he expelled all of them some say he overloaded the server. This was not the reason. It was rather an error in the coding of the construction skill. Because Cursed You 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 owner of the house 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 has now been fixed.

&mu; Glitch
Another famous glitch would be the infamous &mu; glitch. When a player pressed Alt+0181, the &mu; character was created (The Greek letter mu, also used for the prefix "micro"). A player who typed in this character and actually said it would find that all nearby players including himself 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 &mu;. This would crash the other players, leaving the abuser to kill the other player with absolute ease. It was estimated that over 200 million GP was 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.

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 and banned anyone who abused the glitch. Evidence of this Glitch can be found

Player (level: 1) Glitch
In the house containing the Customs Sergeant in Rimmington, you can 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. See Invisible player.

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, and the Duel Arena.

House Floor Glitch
When the new map and hitpoints bar was released, in dungeons of houses when players fell in to pits they couldn't get out of the swimming position unless they either died or were teleported. But when they climbed a ladder and went into a combat arena they were still in the swimming position ,also people could walk on top of fire without getting damaged and they could walk on top of pits without falling into them.

Unresponsive NPC's
As a result of updates on June 9th, 2009. A temporary glitch existed where monsters would not respond (attack back) to ranged attacks (range/mage). This allowed some players to solo really difficult bosses unfairly. The glitch was quickly removed.

House Wall Glitch
5 minutes after an update from Jagex on June 9, 2009, people walked into their houses expecting to throw a party. Soon afterwards people discovered that a wall blocked their rooms and they could not get in unless they used doors. One player, hellomoon15, was trying to throw a school, but when people said to expell guests and go to building mode, she was soon trapped in the room herself.

Then, people started to ask butler to go where the owner is, Causing the people to be trapped inside the 2nd story bedroom. 10 minutes later, Jagex did another update causing the glitch to be fixed and everything went back to normal.

Partyhat Duplication Glitch
The glitch was not an attempt to duplicate items. A player named SixFeetUnder 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."

Sledding Glitch
This glitch was witnessed in Varrock's bank, the player who was doing the glitch seems to be riding the sled from Troll Romance. But their sled was transparent, so it looked like the player was squatting and sliding along the ground.

Crossbow Glitch
Sometimes, when using a crossbow, the arrows seem to be fired without an animation. Normally due to lag.

Castle Wars Cape Glitch (Gnomecopter Glitch)
Free-to-play players were once able to float above the ground equipping | Castle Wars capes (which are Members-only items) that they managed to receive through a glitch involving the | Gnomecopter. They would fly a Gnomecopter to Castle Wars and click on a signboard that would bring them to either the Zamorak or Saradomin Castle. On the second floor of their chosen Castle, they would click once on the Respawn room and immediately click the "Report Abuse" button, allowing them to actually enter the said room. They would then finally exit the "Report Abuse" window and click on the Exit Portal and find themselves floating in mid-air back to the Gnomecopter area with a Members-only cape equipped[].

The glitch was fixed and shortly after this, the Gnomecopters were removed.

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.

Varrock Bank Glitch
On June 9,2009 (following the update of the "Rest") people were unable to use the Grand Exchange and Varrock banks. It is said that only 1 person throughout that 20 minute period could use it, but the facts remain unknown

=Miscellaneous Bugs=

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", "Lebo50", "AJS1992", "Zhixing Li", "TakJack", or "Zetardo", it would say "**yo1", "L*b***", "***1992", "******* **" Ta*Jack, or Zeta*do. 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. There is also a character called Fack_Youtube. 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.

=References=


 * RuneScape Game Guide
 * Reporting Bugs
 * Rule 4 - Cheating/Bug Abuse

= See also =
 * Item glitches
 * Player and NPC glitches
 * Environment glitches