9 June 2009 game engine update glitch

From the RuneScape Wiki, the wiki for all things RuneScape
Jump to navigation Jump to search

The 9 June 2009 game engine update glitch occurred on 9 June 2009 at around 16:00 UTC after the RuneScape game engine was significantly rewritten. Just minutes after the update, however, players were experiencing a huge variety of bugs, and soon the RuneScape Forums were overloaded with bug reports and confused players. One of the earliest reported glitches was that players could not run and eat at the same time which, according to Jagex, involved accidentally removing a feature that allowed the player to perform two actions at the same time.

Banks[edit | edit source]

Many banks became inaccessible, the most notable one being the Grand Exchange bank. If a player attempted to talk to a banker, they would get the error "I can't reach that". Zanaris bankers would give players the "Nothing interesting happens." message when they tried to use the bank. The one way players could use the Grand Exchange bank was by clicking the Bank - Desk option.

Disabled attack styles/non-retaliation[edit | edit source]

All of the non-player characters were unable to use Magic or Ranged attack styles, and a number did not retaliate to a character in any way. This led to players successfully "solo-ing" the Corporeal Beast, going through the TzHaar Fight Cave extremely fast, and killing the bosses in the God Wars Dungeon, as they had no worry about taking any damage.

World 64 crash[edit | edit source]

The World 64 crash occurred on 9 June 2009 following the "rest" feature update. Any players who logged into World 64 could not log into another world from the account that was logged into World 64. If a player on World 64 was in a Clan Chat (now known as a Friends Chat) when the crash occurred, the player would still be in the Clan Chat until they logged into another world, even though the player was not shown in-game.

Even though Mod Emilee, a Jagex Moderator, had stated that Jagex would not be performing a roll-back, they performed a roll-back on World 64 around ten minutes after the crash, leaving some players in a vulnerable spot. The ten-minute roll-back resulted in a loss of experience and item drops for players affected.

Other glitches[edit | edit source]

Apart from the major game glitches, several other bugs prevented players from accessing features of the game as they normally would be able to:

  • Crystal chimes stopped cleansing warped creatures.
  • Attempting to use a combat spell on players in the Soul Wars waiting room would give the message "Nothing interesting happens".
  • While scaring away the dog in Varrock, players would first pivot sitting down before they scare it away.
  • Players could not remove their armour while running.
  • Evil Trees could no longer be inspected.
  • Players could only train Ranged or Magic standing right next to a foe, and the dragon halberd could not be used to attack from behind an obstacle or a space away.
  • The player-owned house doors disappeared, except for the doors at the entrance.
  • Ava's accumulator didn't work, yet Ava's attractor did.
  • Many players could no longer train Hunter.
  • Players no longer automatically walked west when they lit a log.
  • Players could get free Firemaking skillcapes if they had 99 Firemaking.
  • Summoned familiars became invisible.
  • Players could no longer bless gravestones.
  • The Magic Dart spell would not work.
  • Void Knights became invincible.
  • Penguins could no longer be spotted.
  • Triggering a trap in Pyramid Plunder would get a player stuck and kill them in a matter of seconds.
  • Players could not complete random events or leave the random event area.
  • Players could not set up the dwarf multicannon.
  • Bankers were seen facing sideways.
  • Players could no longer jump on the basalt rocks to get to the Lighthouse nor could they jump on the stepping stones to get to the Tears of Guthix activity.
  • Hopper controls in windmills, including in the Cooking Guild, no longer functioned and instead produced the message "I can't reach that!" when interacted with.
  • Tele-other spells could no longer be cast.
  • When a player tried to regularly bank at a banker, they would occasionally receive the message "This booth isn't in service."
  • The rope swings in the Brimhaven Agility Arena produced the message "I can't reach that!" when interacted with.
  • Rock crabs would appear when players walked over them, but immediately disappear, making it so they could not be killed.
  • Elementals in the Sorceress' Garden would not teleport players.
  • TzHaar monsters became aggressive and killed many players.
  • The graphics on the doors at areas such as Yanille would show both an open and closed door at the same time.
  • Players were unable to pickpocket.
  • Players could not create a canoe at the canoe hotspots along the Lum.
  • Players could not use greegrees.
  • Players could not escape the Teleportation Lost and Found Office.
  • Players could not consume anchovies.
  • Some areas such as the Al Kharid mining site could not be walked through.

Aftermath[edit | edit source]

Even after Jagex attempted to fix the glitches, other bugs continued to appear. After a fourth system update, with a total of six occurring that day, most of the issues seemed to have been resolved. Many players complained about the fact that Jagex had refused to roll back to a previous state before the update. Many others were angry over the fact that the players who had exploited the glitches were not banned, as doing so is a violation of the Rules of RuneScape. Some players went as far as trying to get others to riot in protest. With the new "rest" feature, "sit-ins" around the Grand Exchange and other banks became popular.

In an attempt to hotfix a bug that made it impossible to run and eat at the same time, Jagex inadvertently made it possible to do up to two different actions simultaneously that had previously been impossible. This made power-training skills such as Fishing and Woodcutting faster because players could drop items without having to re-click to gather more resources. At first Jagex considered it alright. But as more forum posts came in, Jagex fixed it because "A lot of the careful balancing of the game was being thrown off". In one extreme case, it was possible to create gem bolt tips and make the bolts at the same time.

The entire game system had been revised to improve the game engine. After six years of updates, the foundations were very messy, so tidying up the code allowed the engine to perform tasks more efficiently. Contrary to popular belief, the increased engine performance is what caused the glitches to occur, not the run update. Throughout the day, Jagex received so many bug reports on the RuneScape Forums in such a short time-span that they had to suspend the creation of new threads for a while so they could read and sort through all of the existing reports.

Gallery[edit | edit source]