Bug: Misc


DC Comics

Up to date as of February 01, 2010
(Redirected to Bernard Bonner (New Earth) article)

From DC Database

Character Template Character Template

Real Name
Bernard Bonner
Current Alias



Partner of Byte

Blythe Bonner (sister)


Base Of Operations


5' 10"

159 lbs (72 kg)


First appearance



History of character is unknown.

See Also

Links and References

  • None.


"You get right back here and finish this article, young man!"

History Section Needed!

The history section for this article is either absent or contains very little information. You can improve this article by adding as much relevant historical information as possible. Articles should be written from an "in-universe" perspective as if they were written by a historian living in the DC Universe.
(This template will categorize articles that include it into the "History Section Needed" category.)

This article uses material from the "Bernard Bonner (New Earth)" article on the DC Comics wiki at Wikia and is licensed under the Creative Commons Attribution-Share Alike License.


Up to date as of February 02, 2010

From Muppet Wiki

Design Team:
Ed Christie • (designer)
Tim Miller • (builder)

Bug is a bright yellow insect who appeared in The Adventures of Elmo in Grouchland. Bug is the meek henchman to Huxley, carrying out his orders with a shrug. Bug's personality is such that he accepts and even enjoys the mistreatment, until Elmo finally shows him what true kindness and friendship are.

Tyco released a small talking plush version of Bug.

The Bug puppet was subsequently reused as the Jitterbug in Episode 4117 of Sesame Street, and as Bill the Bug on Panwapa.

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


Up to date as of February 01, 2010

From The Vault

This disambiguation page lists articles that might otherwise share the same title.
If an article link led you here, please change the link to point directly to the intended page.

Bug can refer to the following ingame terms:

It can also refer to a software malfunction. Please see the following per-game overview pages:

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

Final Fantasy

Up to date as of February 01, 2010

From Final Fantasy Wiki

Bug may refer to:

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

Guild Wars

Up to date as of February 01, 2010

From GuildWiki

A bug is an error, flaw, mistake, failure, problem or fault in a game that prevents it from working as intended. This may include things such as graphical flaws, spells not working correctly or features not working properly.

Bugs are often fixed in game updates. If you find a bug you can visit the support section of the official Guild Wars homepage to report it.

For a current list of known bugs, see Category:Bugs.

Skills that contain anomalies are listed at List of skill anomalies.

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


Up to date as of February 09, 2010

From Grand Theft Wiki

A Bug in GTA 1.

The Bug is a small beetle-like car that appears in nearly all early GTA games up to Grand Theft Auto III, including:





Based largely on the real life Volkswagen Beetle in both name and design, the Bug is depicted in all its appearances as a largely undesirable car, being unattractive in design and performing poorly as a road going vehicle.


In GTA 1 and GTA 2, the Bug possesses average cornering helped largely by its below average acceleration and speed, making it a poor vehicle of choice for timed missions and chases. For GTA London 1969, however, the Bug features better performance, with average top speed and acceleration; GTA 2 also improves over the performance of previous Bugs by making the game's Bug more nimble and more responsive in cornering, although its speed is still considerable underwhelming.

When exported in good condition GTA 1, the Bug awards the player a base payment of $200 in Liberty City and Vice City, but only $100 in San Andreas. Similarly, the Bug in GTA London may be exported for a base amount of £200 if delivered in mint condition. When crushed in GTA 2, the Bug gives the player a Machine Gun.


The Bug is present in nearly all classical GTA games, appearing in all three cities in GTA 1 (Liberty City, San Andreas and Vice City), and in the GTA London 1969 mission pack. For GTA 2, the Bug only appears in the Downtown and Residential districts of Anywhere City.

See also

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

Marvel Database

Up to date as of February 09, 2010

From Marvel Database

This is the Bug disambiguation page.

A = Appearances · I = Images · G = Gallery · F = Fan Art · Q = Quotes

Disambig Template Help

This article uses material from the "Bug" article on the Marvel Database 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.


Up to date as of February 04, 2010

From Wookieepedia, the Star Wars wiki.

Bug can refer to more than one thing:

This is a disambiguation page—a navigational aid which lists other pages that might otherwise share the same title. If an article link referred you here, you might want to go back and fix it to point directly to the intended page.

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


Up to date as of February 05, 2010

From TibiaWiki

This creature is in the Arthropods class.

29 Hit points
18 Experience points per kill

Summon/Convince: 250/250 (Illusionable)
Abilities: Melee (0-23).
Push Objects:
Est. Max. Damage: 23 hp per turn
Immune To: None.
Strong To:
Neutral To: Physical, Holy, Death, Energy, Ice, Earth, Drown, Life Drain
Weak To: Fire (+10%)
Sounds: None.
Behavior: They fight to the death.
Field Notes: They are good to gain experience from because of their low defence. Be very cautious of these in Rookgaard as they can easily gang up and break your shielding spots.
Location: In many parts around Tibia, including Rookgaard.
Strategy: They are very slow and weak in Mainland; just attack them.
Loot: 0-6 gp, 0-3 Cherries (semi-rare). (Loot Statistics)
See also: Creatures.
Add historical information about this creature.
Creature Types of Tibia
Creature Types
of Tibia

Frogs Quara
Arachnids Insects
Demon Lords
Demon Lords The Ruthless Seven
The Ruthless Seven
Demons Triangle of Terror
Triangle of Terror
Bio- Geo-
Cryo- Hydro-
Electro- Pyro-
Elemental Lords
Elemental Lords Blobs
Amazons Outlaws
Barbarians Pirates
Monks Sorcerers
Necromancers Voodoo Cultists
Voodoo Cultists
Dwarves Goblins
Elves Orcs
Giants Trolls
Chakoyas Minotaurs
Dworcs Misc
Magical Creatures
Beholders Shapeshifters
Apes Felines
Artiodactyls Glires
Bears Misc
Canines Mutated Mammals
Mutated Mammals
Annelids Bosses
Arena Bosses
Arena Bosses Event Creatures
Event Creatures
Birds Traps
Dragons Misc
Lizards Serpents
The Undead
Ghosts Skeletons
Pharaohs Undead Humanoids
Undead Humanoids

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

City of Heroes

Up to date as of January 31, 2010

From City of Heroes Wiki



  1. A bug is an error, mistake, or flaw in the game that prevents it from behaving as designed. Most bugs arise from mistakes and errors made by developers in either the programming or design.

See Also

This article uses material from the "Bug" article on the City of Heroes 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