[Guide] Fixing the "Dun Morogh" Graveyard Issue

[Finalee]

Alright, let me start off by saying that all the credit for this find comes from one of my fine GM's at Phoenix WoW, Xanar, and even though we don't quite know how it works, it works and we are glad for it.

NOTE: Before we even get started, make sure you go into your Navicat, or whatever DB Accessing tool you use, and make a copy of your graveyards table.

Alright, we all know about the bug that teleports you to Dun Morogh if you are an alliance character. It was supposedly fixed in the update for MGT-Pack (1.1) but I am running my server on it and it still was not fixed. Now, my great GM Xanar thought of an idea that might work, so I let him have a go at it.

First off, we will open our graveyards table using Navicat (or your DB accessing program). Easy right? 

Next, we will find the column named zoneid. 

After you have found that, starting at the first row, change all the ID's to 1. Make sure all your zoneid's are set to one. 

Save your table and restart your server......Yea, it's that easy, we were amazed too.

Here is a simple SQL Query to make this fix easier:

UPDATE graveyards SET ZoneId = 1

Now, I'm guessing all of you are asking, O.K. but how the hell does this work???

I will answer to the best of my knowledge. 8-)

When you die and your spirit is released, and the game looks for the closest graveyard within the Zone ID. Now, by changing the zone ID to 1, this sets every graveyard in the game (and this is where we start to guess) to the whole world (or zone ID 1) (end of guessing). So in turn, that means that if you die anywhere in the world, you will be teleported to the nearest graveyard, no matter where you die. And that, is how it solves the problem.

Let me again say that this credit goes to Xanar, with me explaining everything. Also if you find anything that is wrong in what I said please correct me. Thanks...

-Fin

P.S. This was O.K.ed by Darvaleo (a MGT-Pack Developer) and he posted back at MGT, here is his post:

When you die, the server does some lookups for the the current area id and zone id for your current position on the map; if it can't find any area match it just does nothing in the transport and this "problem" is a bad AreaTable.dbc file.

If it finds the area, but has 0 in the Zone, it guesses and just assumes it will use the area for the comparison only and ignore the zone information.

Your solution bypasses the zone checking information and works fine so long as there is a graveyard on the same map you are located when you die.

Personally I haven't been able to cause the graveyard problem since MGTpack 1.1, so I wonder if people that are having the problem really just have problems with their AreaTable.dbc and this is just a way to get around that problem.

All in all, as long as it works, I have no problems with this fix.

Thanks Finalee for sharing it.

[*TraPStaR*]

or you could just have maps folder like all the rest of people

[Le Froid]

or you could just have maps folder like all the rest of people

[project anthrax]

wow.... thanks! I just posted about this being a problem for me and the solutions were a bit more intensive...

Just tried it out and viola! problem solved... Thanks again!

[07wilsonaf]

blah blah blah

[Tobeo]

Nice, This helped me solve another problem aswell ;D

[Shroomie]

Great! Nice simple solution to a rather annoying issue.