WoW 3.3.5a/The Kessel Run

[Guest]

I am very lost. I have found a bugged quest and am trying to go through the sql database to try and figure out why the quest is not working properly.

The Kessel Run (Quest ID 9663) is dysfunctional. I got it from the right person, the right text is displayed, the right timer and ever the right induction spell, getting Kessel's Mount. My problem is that I am suppose to warn the High Chief Stillpine at Stillpine Hold, Exarch Menelaous at Azure Watch and Admiral Odesyus at Odesyus' Landing. The problem that I am encountering is this: I can warn everyone on the list, but the quest does not accept my right-clicking on the CHief, Exarch or Admiral. They say thank you for the reward and the quest does not accept it. It still says 0/1 for each of the people I am to warn.

What am I missing? Is there something I need to check out in the dbc files or something? I would hate to think that I have to find some way to track this clear back into the client itself or something. Or even going through all the sourcecode to the core of Mangos. Ewe.

Any help would be greatly appreciated.

[wolverine]

Alright. Is there any way to simply disable a quest or do I have to go through the database and simply remove the quest from there? I've been through the core code and didn't find anything which pertained to my problem, but I did find a function that I cannot figure out how to invoke which revolves around disabling quests.

[ecstasyversus]

Alright. Is there any way to simply disable a quest or do I have to go through the database and simply remove the quest from there? I've been through the core code and didn't find anything which pertained to my problem, but I did find a function that I cannot figure out how to invoke which revolves around disabling quests.

Well when i find a bug quest like that i run this two comands:

1. Syntax: .lookup quest $namepart (to find the quest ID, so i can shift click on it and insert in the chatbox.)

then...

2. Syntax: .quest complete #questid (just remove the #questid and replace with the [shift + click] on the quest ID you found with the above command.)

and the quest giver should now complete your quest.

I don't know if your server is public removing the quest would not be a good idea. just saying.

[wolverine]

Well, I did remove it. But I also backed up the entire row in the database devoted to the quest. I've been through the quest a dozen times and through the core code, as I said, and couldn't find anything in regards to the quest itself or anything wrong witht he quest. I even compared it to the same quest in two other databases, and got nowhere.

And having to sit there and manually complete it for everyone would be a pain. And no, at this time we are not public. I've considered it but have had second thoughts about that idea as I am not sure I want to deal with 100 people all at once telling me about all the broken quests.

In the database, I just modified the whole quest chain so the chain starts with the quest after 9663 and removed 9663 from the quest template database. For now.