In the world of WoW Classic Hardcore, losing your character due to a disconnect is the worst possible outcome. Unfortunately, even the game’s anti-disconnection systems can sometimes work against players. One WoW player recently shared their harrowing experience on the WoW Classic subreddit, where they were disconnected while on a boat ride and found themselves in enemy territory upon logging back in.
The player, a level 40 paladin, was on their way from Ratchet to Booty Bay when the disconnect occurred. Upon logging back in, they were shocked to find themselves in a completely different location. Instead of being on the boat, they were standing on solid ground, surrounded by graves, and the text of the zone revealed that they were in Razor Hill, a Horde-only town.
This situation was particularly alarming for the player because they were an Alliance character, and being in Horde territory was a dangerous predicament. It seemed that the game’s failsafe measures, designed to protect disconnected players, had actually placed them in harm’s way.
The reason behind this unexpected turn of events likely lies in the game’s coding. WoW Classic has a failsafe mechanism that teleports disconnected players to a relevant graveyard. However, in this case, the player disconnected while transitioning between continents, causing the game to place them at the default graveyard in Razor Hill. This bug occurred because the loading screen between Kalimdor and the Eastern Kingdoms disrupted the game’s understanding of the player’s location.
Thankfully, the player survived this encounter with the loading screen and lived to share their tale. It serves as a reminder of the unpredictable nature of disconnects in WoW Classic and the potential dangers they can pose to hardcore players.
About the author
Source: DOTESPORTS
