devtrackers.gg
over 1 year
ago -
RuneScape
-
Direct link
Transcript (by Youtube)
| 0s | what caused the falador massacre bug the |
|---|---|
| 4s | iconic event from 6th of june 2006 has |
| 7s | been one of the most discussed days in |
| 9s | runescape's two decades being named one |
| 12s | of the best books in mmo history by pc |
| 15s | gamer it's also the only in-game |
| 17s | happening to have its own section on |
| 19s | wikipedia first used 99 construction |
| 22s | party that took place 9 minutes past |
| 24s | midnight on the 6th of june uk time was |
| 27s | the centerpiece in what led to the |
| 29s | infamous bug but despite popular belief |
| 33s | what caused a small group of players to |
| 35s | have pvp enabled outside of the house |
| 38s | remains a mystery to this day in fact |
| 41s | all the jagex moderators working to |
| 43s | prevent the bug from happening again |
| 44s | couldn't identify the cause of it they |
| 46s | did know that bug abusers carried a pvp |
| 49s | variable from the house's pvp challenge |
| 51s | mode but exactly how this was enabled |
| 54s | outside of the house remained unknown to |
| 57s | fix it content developer mod ash |
| 59s | disabled pvp in the entire game until |
| 62s | andrew gower could take a look at it the |
| 64s | morning after but even andrew was unable |
| 67s | to discover how the bug was used and |
| 69s | instead built a new system entirely for |
| 71s | the game to constantly check where the |
| 73s | player is located in the game in this |
| 75s | way if the game notices a player has pvp |
| 78s | in what's meant to be a safe zone the |
| 80s | pvp variable is automatically removed |
| 83s | players have since accepted the theory |
| 85s | that the combat ring was the cause and |
| 87s | being expelled whilst inside it would |
| 89s | let you keep pvp enabled some have also |
| 91s | theorized that this crying pool is |
| 93s | responsible assuming you're just crying |
| 95s | when you were expelled however both the |
| 98s | most known bug abuser durian321 and a |
| 101s | second abuser via zodiac wood in the |
| 103s | hours after the event claimed they were |
| 105s | both in the greater magic cage in the |
| 107s | throne room when being expelled not the |
| 110s | combat ring or this crying pool at all |
| 112s | now the code around construction and the |
| 114s | pvp variable has been heavily changed |
| 117s | since june 2006 meaning there's no way |
| 120s | to say for sure what exactly caused the |
| 123s | falador massacre but after reviewing the |
| 125s | construction code from august 2007 being |
| 128s | the one old-school runescape is built on |
| 130s | we can make a guess that there is a fair |
| 133s | chance the bug was caused by very |
| 135s | specific circumstances when two actions |
| 137s | were activated in the same game tick |
| 140s | cursed you expelling and a separate |
| 142s | player sending the accounts trapped |
| 144s | inside the cage into the dungeons cursed |
| 146s | you was online for a long time and thus |
| 149s | his action would be prioritized meaning |
| 151s | after they got expelled the game would |
| 153s | still attempt to send the players down |
| 155s | into the dungeon but instead seeing |
| 158s | there was no longer a dungeon to enter |
| 160s | it completed the other half of the |
| 162s | action and applied the pvp variable they |
| 165s | would have gotten if the dungeon was |
| 167s | there allowing players like yeti 90 |
| 169s | runescape go 1 john official 0 would be |
| 172s | a zodiac and durian321 to attack whoever |
| 176s | they wanted during the chaos unfolding |
| 178s | in remington it didn't take long before |
| 180s | the community managers on nightshift |
| 182s | responded to the player moderator's |
| 184s | reports but in 2006 it wasn't as simple |
| 187s | as just ban the pkers as the players |
| 190s | attacking were still in combat they |
| 192s | couldn't be logged out even if it was |
| 194s | due to an account ban as such the jmods |
| 197s | were unable to do anything but encourage |
| 199s | players to run away until the pkers left |
| 202s | combat for more than 10 seconds before |
| 204s | attacking a new target interestingly |
| 206s | enough durial's infamous massacre was a |
| 209s | result of sheer luck had he teleported |
| 212s | to edgeville or tried to hop to take |
| 214s | down the busy trading hotspots in world |
| 216s | 2 or even climbed a ladder he'd likely |
| 218s | have lost the pvp variable given how it |
| 221s | was coded but durial simply ran wherever |
| 224s | he wanted to go and thus kept the pvp |
| 226s | variables stuck to him throughout his |
| 228s | evil plan of slaying unsuspecting |
| 230s | players in edgeville |
| 232s | forum threads videos and screenshots |
| 234s | were the hot topic in the following days |
| 236s | people were either angry about losing |
| 238s | their items or tried to claim items they |
| 240s | never even lost as a result and due to |
| 243s | the technical limitation at the time |
| 245s | paul gower made a post in the afternoon |
| 247s | of june 6th announcing there would be no |
| 249s | rollback or item refunds apologizing |
| 251s | profusely for what had happened |
| 253s | durial 321 remained banned with a |
| 256s | personal note made on the account by |
| 258s | andrew gower to ensure it would never be |
| 260s | let back into the game this didn't stop |
| 262s | the account owner from continuing his |
| 264s | runescape adventures however playing on |
| 266s | a secondary account called |
| 268s | azenboyc763 for the next three years |
| 270s | before leaving the game sometime in 2009 |
| 273s | wherever he is today i do wonder if he |
| 275s | is aware of the legacy connected to his |
| 277s | old gamer tank and whatever caused the |
| 280s | massacre bug the cause is likely still |
| 282s | buried in the game's code protected by a |
| 285s | fortress of checks to ensure pvp remains |
| 288s | away from the game's safe zones |