Glitch

A glitch (also known as a bug) is a fault in the program 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.

Abuse of a glitch which provides a player with an unfair advantage can result in anywhere from temporary muting to a permanent ban from RuneScape depending on the severity of the glitch, and how much a player abused it.

Falador Massacre
One infamous example of bug abuse was the Falador Massacre- also called the World 111 Glitch or the World 111 Massacre. 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 all the guests were causing large amounts of 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.

Mods tried to tell people to drop their items and 'glory' teleport but they were barely seen among the massive amount of followers.

This bug remained on RuneScape for about an hour and was fixed immediately after it became known to Jagex.

Chat Tricked 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. This glitch was abused quite often during the Pay to Pk riot, mainly to insult Jagex. 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. 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 numerous amount 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 around the 8th of November. Most if not all of the bug abusers who performed this bug are now banned.

Running button fault Glitch
When a player is out of energy after running, and presses the button to run when they have zero energy, the button will light up as if the player is running. However, the player is not running at all. This is not fixed. Players can double-click the running button to restore functionality of running.

Penguin Hide and Seek Glitch
The Penguin Hide and Seek Glitch was a glitch that occurred on 28 January 2009, on World 60, involving the Distractions and Diversions Penguin Hide and Seek. Players discovered the glitch when they found out they could spy on the same penguin over and over again. As a result, players could gain 50 points in a short amount of time, visit Larry, trade them in for experience, and then return to the penguin to earn more points. More than a hundred accounts were permanently banned and several more accounts were temporarily banned as a result of this bug.

Fight Pits Player Killing Glitch
During the first few hours after the new iron scimitar look was released, while playing the TzHaar Fight Pit activity, 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.

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 activity, the Duel Arena, Earth warriors, the Rock Crabs in Rellekka, Dust Devils in the Smoke Dungeon, and Guards at the West Ardougne Market.

A Variant of this glitch has been found in Late November 2010, after the release of Korasi's Sword. Extremley rarely, when a normal hit is blown followed by the special attack, if the targeted NPC is killed, it will drop it's normal items upon death, but continue to attack the player while being invincible. It is then attackable once it has had the chance to regain a few life points. This can continue until the special attack is used again, as this finally kills the NPC. This was first spotted by a player killing a Highwayman north of Seers Village on the 30th Nobember 2010.

Player-NPC Glitch
The Player-Npc glitch was first noticed in April 2010. This glitch makes a player name in the right-click menu will turn yellow as if it were a NPC name. It is not known what causes this glitch. It is not known if this glitch was fixed by Jagex as it cannot be reproduced purposely.

"Floating In Ground" Glitch
The "Floating In Ground" Glitch was first found on 5 January 2011. This glitch makes a player appear if they are floating in the ground, as shown in the image to the right. In addition, the player will occasionally twitch his/her head to the left. This glitch is also unfixed.

Party hat duplication glitch


The partyhat duplication glitch is one of the most famous glitches in RuneScape, with its effect on the rares market still being felt today. 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 on a massive scale over the period of a few days drastically affecting the RuneScape economy, specifically the rares market where the price of pink/purple partyhats dropping from being the most expensive party hat to the cheapest. Jagex didn't know how the items were being created and therefore offered a reward of lifetime membership to any player who could tell them how the glitch worked. A few players came forward and with the knowledge these players provided, Jagex fixed the glitch and subsequently banned them.

GreeGree + Easter Ring
During the first day of the 2006 Easter holiday event if a player went to Ape Atoll and would equip the greegree and then right-click the Easter ring, a player's character would become all weird & stretched-out. You could still use the agility course like you were a monkey.



The glitch was soon fixed and attempting to use the ring after would result in an "The ring doesn't seem to fit properly on your monkey finger." message.

This Glitch could also be done if a player was to travel to ape atol via fariy ring and rapidly clicking the gree gree while teleporting. Many abused this glitch to annoy players in the agility course. Having this glitch happen to you while doing the agility course caused alot of stretching and sometimes lag.

Blood rune duplication glitch
This glitch allowed players to take blood runes out of the activity 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. Most of the players that abused this glitch were permanently banned.

Bolt duplication glitch
The Bolt duplication glitch was leaked to the wider public on 22 February 2010. This glitch was patched without a system update on the 23rd of February. It enabled players to gain tens of millions of gp per hour by significantly multiplying the amount of dragon bolts during enchanting.

The player used a chisel with a cut gem. When the message pops up to cut into gem tips the player opened up their mage book and then clicked make-all on the gem. As soon as the player started making bolt tips they clicked enchant bolts on the dragon bolts. The first 10 bolts get enchanted, and then every 1 bolt after that turned into 12 enchanted bolts.

The glitch could be used to multiply any bolts, but due to the scarcity and value of dragonstone, combined with their frequent use in PvP, dragon bolts were the most widespread kind of bolts that were used while exploiting the glitch.

Jagex made an official statement about this bug on 2 March 2010, in which they said that they banned several high-levelled players, including one with a Total level of 2376 (The highest Level you could achieve before the release of Dungeoneering) and one with over 1000 days of total playtime. Several fan-site forums reported an increase in ban-risk for all types of offences in the days following the glitch; therefore, it seems Jagex temporarily increased its watchfulness in order to seek out those players who did participate in the glitch.

Stock glitch
The Stock Glitch, which occurred the 29 of May, 2010, was a bug that caused all stocks in world 169 to be immediately refilled after buying. After players began to notice it, players stood at shops and repeatedly bought the items that kept on refilling, making large amounts of profit. Jagex fixed it after a few hours.

Dungeoneering armour glitch


Some players were able to smuggle dungeoneering armour outside of the dungeoneering skill and wear the armour. Many other items have also been smuggled from the Dungeoneering skill, although only a few of the items are usable outside of Daemonheim.

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 will 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, the 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.The glitcher could also delete the owners butler but could not retrieve things from the bank.

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.

Turn-Back Glitch
The Turn-Back glitch (also referred to as the walk-block glitch by some) was and is a fairly common glitch, easily re-creatable under certain conditions. The Turn-Back glitch commonly occurred at several locations (such as near the Al-Kharid Bank and the Wilderness entrance on Demonheim). The Turn-Back glitch was basically a glitched wall, which existed in a certain location. If a player walked into the wall, the wall would automatically turn their character around. If attempted again, the same result would occur. The only way to penetrate the "glitch wall" was to run at it. However, even this is known to fail. The glitch can become extremely aggravating for a weighted-down character, especially near the Al-Kharid bank, which is a common location for F2P Smithers. The glitch has been mostly fixed as of now, but still exists in some locations.

Login screen player names after logout
This is a glitch where if you log out of the game by clicking exit to login then quickly right click players the names remain when you go to the login screen. Beware: you cannot click anything on the login screen to exit full screen etc.

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 "Hellsome" might produce "**yo1" and "****some" respectively. 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. This is not necessarily a glitch per se; as such 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 Self to Friends List 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 effect on your clan in 60 seconds" and their usernames removed from their own friends list. It is 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. This instance of the glitch has since been fixed.

In December 2009 this glitch was possible to do in RuneScape Classic; this has since been fixed.

Prayer Glitches
There have been a few Prayer glitches. When players would do a "shows above head" prayer, and then the Around the World in Eggty Days emote, they would leave their prayer behind. This was fixed with the 2009-11-09 update.

Another glitch, would cause a similar effect if players used a teletab while displaying a prayer icon.

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.

Clan Chat Player Duplication Glitch
This glitch happens rarely and is not that bad. This glitch happens when you log off one day in a different world and the next day you open your account and enter clan chat in a different world (the day before you must be in a clan chat) you will see yourself in the world you were in yesterday (example:yesterday world:85 next day:108, on 108 you enter your clan chat and there will be two of yourself, the world you're on is you and the other world (85) is the glitch. It is not known yet if fixed or not. NOTE: If you try to kick the glitched player then someone else in the clan chat will be kicked instead.

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 but seen again while Dungeoneering ...

Player Moderator Forums Glitch
In 2009, a major glitch was found by a couple players that allowed them to bypass site security and gain unauthorised access to the player moderator forums on the main RuneScape site. The bug abusers, using these exploits, viewed and archived confidential moderator information discussed on the forums and used them to repeatedly harass various moderators. One of the abusers created a mirror of the information, but Jagex took down the mirror within a week.

It is unknown whether this glitch has been patched or not. The bug abusers who exploited this bug were already banned several times before its discovery for previous instances of bug abuse, including noclipping.

Connection Lost Error
If you right click on anything and then immediately lose connection, you encounter an error in which the drop down right click box is open on the login screen and none of the other option on the login screen will be able to be used. There is no way to close the box.

World 901
After the game update on 23 March 2010, a new world could be seen on the world list called 'World 901 - [RS] Demo World.' Whilst the world list claimed there were a tiny amount of players on this world, it was inaccessible by regular players. Attempting to login would prompt the message 'Malformed Login Packet Please Try Again.' Mod Ac confirmed on the forums that it was a glitch. It was later revealed that this was the Instant Demo world, when the instant demo was released.

Barbarian Assault
A Glitch found while playing Barbarian Assault on wave 10 right before someone lights a fire infront of the trapdoor where the boss comes out. After the boss comes out the fires will freeze then burn out after they are done.

Glitch found while playing a game of Barbarian Assault. The Team Recruitment window is opened showing 2 of the 5 players have quit, yet in the game, no one has quit. All players are accounted for. This window Stayed through the whole game and did not go away. Game play was playable. Later in the game it showed all players were not on the team, yet everyone was accounted for during the game.

Log Out Glitch
After an update on June, 9, 2010, a player couldn't log out of the game nor to the lobby. When a player would choose the "Exit to lobby" or "Exit to Login" option, a message would appear in the right-hand corner saying "Connection lost. Attempting to Re-establish". After the message went away, it would appear as if you had never pressed the logout button. On the same day, a few servers also went down, mainly world 70.

Moonwalk Glitch
This glitch allows you to follow someone while only standing in 1 spot. The followed player can run all around, but the one following will just stay in 1 spot, rotating and walking in place. To perform this glitch, follow any player then just add a blank note to the notes section.

Amplified Head Glitch
This glitch basically amplifies any movement your head does, but your face disappears, with only your fighter hat remaining. From doing emotes to the idle animations, your head movements get amplified. To perform this glitch, you need a fighter hat, a skillcape, and you need to be a girl. This was discovered on 1 September 2010 along with the NPC and PC eye updates.

No items in bank glitch
This glitch occurs when a player right-clicks the banker and before the bank appears the player would right-click the banker again (keeping it open this time) and when the bank option appears the player selects bank banker again.

Headless NPC glitch
When a player uses the Saradomin godsword special attack on the shadowy stranger, the head disappears.





World 143 Members Glitch
Sometime around 9:00 EST on 9/7/10 at least 2 nonmembers were capable of logging into the Members world 143, and did it twice. All the benefits of being a member were capable to be exploited, as both the 2 confirmed nonmembers were able to kill unicorns and get horns.

The Disappearing Text/ Map glitch
This glitch could happen randomly and makes everything text related disappear, the map disappears leaving only yellow, green, and white dots.

Wrong weight in bank glitch
You can perform this glitch by opening the bank, taking or putting items into it and show equipment status.

Sawmill glitch
This seems to happen when you teleport out of the sawmill using a Magic tablet, this glitch has no purpose or use.

Note: If you wish to get rid of this, teleporting to your house or logging off will get rid of it.



Thessalia's Makeovers immobility glitch
On 25 August, 2010, a vast variety of clothing was introduced into the shop, which attracted a lot of players to change clothes. Most players trying to do so find them immobile and unable to teleport. It was able to escape from the bug by climbing the ladder, clicking randomly or logging out and back in. The glitch was fixed several hours later after it caused majority of inconvenience to fellow players.

Corporeal Spirit Glitch
When inside the Corporeal Beast's Cave, there is an invisible "Spirit" located in the corner behind the Corporeal Beast's spawn location. It has a very small right-clickable area and you are only able to examine it.

Tree 'Snow' Glitch
During November–December 2010 there was a glitch in Standard Detail where the leaves on the trees had a square that was white or another object colour other than green. This caused a number of player to think that the trees had become snowy due to the time of year and recent weather. It was however just a glitch, and only occured on lower graphical settings.