The Full Wiki

Glitches: Misc



Up to date as of February 09, 2010

From Grand Theft Wiki

Glitches are unintended affects that can be found in the Grand Theft Auto series.


Grand Theft Auto


The Swimming Glitch

Find some water, Preferably a small pond, but not the ocean and walk towards the water. Continue walking when you hit the water and you'll continue walking/swimming, but only for 5-6 seconds.

Grand Theft Auto III

Walking Above The Subway Tunnel

This glitch can be performed at the subway in Shoreside Vale at the Airport. When the train arrives to the platform, take the very last door of the train. Enter the train and then get out again. You will automatically get teleported above the platform, into the Blue Hell and you will see the tunnel. Word of caution, sometimes the tunnel will get invisible and you risk walking off the edges and get teleported back to the streets.

Rhino Spawn Glitch

If you spawn a Rhino (using the cheat code) anywhere in the city, a second one will spawn in the middle of the street at Liberty Campus around the corner from the Safehouse.

Grand Theft Auto: Vice City

Bike Morphing

Find a motorbike and a clothing icon. Park the bike in the clothing icon, but make it so that when you get off, Tommy won't touch the icon. Get off the bike then get back on. If you did it right, Tommy should have gotten the clothes and gotten on the bike at the same time. This is hard to do at first but practice makes perfect. Use the clothes in Ocean Beach at Rafael's and if you don't get it, ride down to the beach and come back, the clothing will be back.

Cargo Ship Glitch

On the cargo ship in Viceport if you get to the top of the ships cargo you may see a small gap between the two sets of cargo. If you jump into the gap, you will appear outside of the ship between the cargo holds outside the ship and on the other side of the road.

Cherry Popper

The Cherry Popper's save point can corrupt your saved file. To avoid the corruptions of the files, save elsewhere. However somtimes this doesn't happen but it's better not to risk.

Test Track & Trial by Dirt

The initial scores of both Trial By Dirt and Test Track will have the same time results once both scores are listed in stats. Once you play the missions again and beat each time, the scores will be individual as they should be.


Grand Theft Auto: San Andreas

Monster Glitch

Obtain a Monster truck and park ONE wheel onto a random car (sideways or front on, both work). Get out of the Monster, get in the car you park on, and you will find yourself spinning 5000ft in the air, crashing back down to earth.

Taxi Driver Mission Glitch

On the Xbox and PC versions a glitch occurs when the player begins the Taxi Driver mission, but no fares are available. It happens when the player has crossed over the map boundary, which can corrupt save files. It is advised to do this mission very early to avoid this glitch.

Airport Security Guard Glitch

On the PC version, when you shoot the security guard at one of the airports he will vanish and is no where in the booth.


Grand Theft Auto: Vice City Stories

Invisible Biker Glitch

Sometimes if a battle with the Bikers are going on in Grand Theft Auto: Vice City Stories, shoot it with an Assault Rifle while it's driving fast, and it'll show the Angel doing the donuts with no driver.

Grand Theft Auto IV

  • After a missions ends in which an enemy was shot or blown into water (such as the missions Tunnel of Death or Uncle Vlad), the body of that particular enemy will not be shown in the water, even if the cut-scene ended with the player only a few feet away from the sea.
  • If the player falls into a gap (i.e. between two cars or between a car and a dumpster), Niko will suffer minimal damage even when falling from a height that will normally kill him.
  • At the beginning of a date with any Girlfriends while in any vehicle, wait for her to get tired and fire a weapon to end the date. The vehicle the player is currently in will not lose health to any damage done to the vehicle.
  • Bringing up the camera option on the Phone while driving in a car or on a bike will instantly stop the car or bike no matter what the speed the vehicle was going. (Fixed in the PC Version)
  • In the subway tunnels, it is possible to be forced through the wall and into Blue Hell. If the player is riding a motorbike and is trapped between the wall and a moving train, he an be forced through and off the bike. The player could also use a large vehicle (such as the Bus) and get shoved by two subways going in opposite directions to get forced into Blue Hell. All that occurs is falling for a brief few seconds before respawning on the ground above.
  • In the online multiplayer mode "Bomb Da Base II" players have reported a bug/glitch, that occurs at a certain point in the mission. The screen will go black and then start loading, the player will be loaded back to single player.
  • In Francis International Airport in the online multiplayer mode "Free Mode", if the player drives a truck up one of the ramps in the Airport it is possible to make the truck fall on its side and start spinning in circles, this is not only visible to the player, but also other players.
  • If the player gets out of a vehicle parked on the entrance gates leading to Francis International Airport's cargo yard (with stop signs on them,) the gates will go back down and cause the vehicle to disappear.
  • If a vehicle's engine doesn't start, it will start if someone calls the player on the cellphone, more conveniently, if the player calls someone else.
  • Sometimes when driving by the Filling Stations in Northwood, there are two vehicles parked in the parking lot, one of which could be parked with it's engine running, doors locked, and the hazard lights on, which cannot be turned off by the player.
  • When trying to open or get on top of a moving vehicle that is driving down a slope if Niko misses the vehicles door and it drives away Niko will sometimes start walking weird and won't stop until he hits another object. This glitch has been dubbed 'Retarded Niko' by the way he looks and walks when in the glitch.
  • A player can lose a 5 or 6 star wanted level by flying their chopper over Francis International Airport. The wanted level will revert to a 4 star.
  • A certain pedestrian's afro will behave like a hat, falling off after he gets hit.


This article uses material from the "Glitches" article on the GTA wiki at Wikia and is licensed under the Creative Commons Attribution-Share Alike License.


Up to date as of February 08, 2010

From Halopedia, the Halo Wiki

(1 vote)
Crewman Glitch. The crewman seems to be using an invisible MA5B Assault Rifle.

Glitches are errors or bugs in any program that can cause undesired or interesting results. Glitches in video games can often be exploited to gain practical advantages. In the Halo games, glitches are often used in such a manner, and for that reason they are documented quite extensively on some websites. An incomplete list of glitches in the Halo games can be found here.

In Halo: Combat Evolved

Glitches in Halo: Combat Evolved typically required the bypassing of invisible walls or the forcing of objects into areas they were not meant to be brought into. Some animation glitches also occurred.

There are more glitches in Halo: Combat Evolved than in any other game in the series.[citation needed] The amount of glitches in the game is estimated to be between seven and nine thousand.[citation needed] Blood Gulch has over 400 known glitches.[citation needed]

  • There is a Marine that copies himself when dead.
  • There is a glitch at the end of the level Halo in which the final structure has Marines and two technicians. If you kill the Marines, the techs will squat down in fear as normal. If you stick one with a Plasma Grenade while in this position, they will stand up, spread their arms, drop their weapon and start spinning, before being killed by the grenade - because they lack the animations necessary.
  • On the level The Silent Cartographer, it is possible to drive a Warthog through the door that leads to the Cartographer, skipping the need to fight two stealth Elites, four Hunters, and many other Covenant enemies. Doing so can allow you to kill the Zealot elite that stands in the doorway, but it doesn't matter because he will reappear at the end of the level anyways.
  • On the multiplayer map named Death Island, you can drive out on the sea surrounding the island with any vehicle.
  • If you shoot an unarmed Flood Combat Form in the arm with the tentacles, the Flood will be rendered harmless, and will follow you around.

Glitches in Halo 2

Main article: List of Halo 2 Glitches

In Halo 2, players could do things such as Super Jumping or Super Bouncing, get past Invisible Walls to get out of maps, etc. "Button Combos" also existed, such as one that would allow you to kill a player instantly.

In the level, Delta Halo, there is an excessive amount of glitches. For example, there are many cracks and errors in the invisible barriers surrounding the playable areas of the level that enable the player to skip an amount of the level, explore the distant hills, and even get under the lake, on foot, in a Ghost, or in a Warthog.

Glitches in Halo 3

Main article: List of Halo 3 Glitches

Halo 3 has been combed over for glitches by a considerable amount of players, but Bungie has put a lot of effort into making sure that there are few, if any, in Halo 3. There are a few that do exist in active gameplay though, such as the Mine Glitches, driving an AA Wraith, going under the playable area of Construct, Fusion Coil glitches, the Elephant speed boost. Another glitch in Halo 3, one that effects machinima more than gameplay, is commonly referred to as The Bump.

The introduction of the Theater made it easier to find glitches in animation and rendering; its hidden Pan Cam mode introduced some others. The new Forge mode allowed for a large amount of physics, environment, and other gameplay glitches. The use of a new game engine introduced many kinds of glitches that were not present in the game's predecessors.

On the other hand, Bungie cracked down on glitches during Halo 3. Numerous steps were taken to prevent them, including what appears to be an algorithm that detects if items have bypassed the level boundaries. This algorithm is used to delete "lost" Forge items, kill players that exit the map, and return the Theater camera to the nearest living player if it exits the map.

This article uses material from the "Glitches" article on the Halo wiki at Wikia and is licensed under the Creative Commons Attribution-Share Alike License.


Up to date as of February 07, 2010
(Redirected to Glitch article)

From the RuneScape Wiki, the wiki for all things RuneScape

It has been suggested
that this article or section
be moved to Bug. (Discuss).

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

A werewolf experiencing the stretchy skin glitch.
A graphical glitch with the Dorgeshuun crossbow special attack. The player seems to pull the skin on her leg.

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.


Famous Bugs/Glitches

World 111 Glitch

Main article: World 111 Glitch
The World 111 glitch allowing players to attack each other.

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

Main article: February 2009 Crash

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.

A player in a normally inaccessible area via the Noclip Glitch.

Noclip Glitch

Main article: 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.

Player and NPC glitches

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.

A familiar being caught on a pier at Pest Control.

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

Main article: Invisible player
Player (Level 1)

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, the Rock Crabs in Relleka, and Dust Devils in the Smoke Dungeon.

Item Related Glitches

Main article: Item glitches
A graphics glitch while casting high level alchemy.
Party hats made using the party hat duplication glitch.

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 effecting the RuneScape economy, specifically the rares market where the price of [[|Purple partyhat|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 to any player who could tell them how the glitch worked. A few players came forward and with this knowledge Jagex stopped the glitch from working.

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.

Environment Glitches

Main article: Environment glitches

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.

Miscellaneous Bugs

Filtered usernames

An example of the chat filter name interference.

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****" 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. 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.

An example of the Display Name Glitch

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, This hasn't been fixed, but only If you type your previous display name.

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

Options disappeared when the map "loaded".

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

The null 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, before selecting "Use". You can also perform this glitch by dragging an item in between two item areas in the inventory and then quickly clicking use. You can also click drop item, and quickly before it disappear from your inventory right click on it. Simply click "use". Then right click on any item and you will see [ Null ->Item ]

Disappearing Text glitch

The chat box

The text glitch is a glitch that causes almost all of the text in RuneScape to disappear. It is unknown exactly how it happens.

  • Confirmation: It occurred a few times in a POH after speaking to butler, after that it didn't occur again.

(Last time was sometime in January 2010)



Wikipedia has an article about:
  • RuneScape Game Guide
    • Reporting Bugs
    • Rule 4 - Cheating/Bug Abuse

This article uses material from the "Glitch" article on the Runescape wiki at Wikia and is licensed under the Creative Commons Attribution-Share Alike License.


Got something to say? Make a comment.
Your name
Your email address