PDA

View Full Version : Problem with Kamal on Court of Coin


Farr
12-02-2007, 09:52 PM
<p>This is for the quest Court of Coin: Building the Business (or something similar).</p><p>Got to the last part where I have to "fire" prefector kamal who spawns at the court of champions. As soon as I kill him, he and his wierd little cohort de-spawn. It says You have killed Kamal. This encounter will no longer give rewards. And no quest update. I'm lvl 74 zerk and I can kill him quite quickly, so I dont think its a matter of the time he takes. Please help... I'm out of solutions. Thanks!</p>

Fyorwin
12-06-2007, 02:05 PM
<p>I'm having trouble with this one as well. I did it with a 63 Illusionist and a 70 Guard and got the same failure message. the Guardian mentored to 63 and we tried again - quest is green, Kamal pops grey at 52 - no luck. Last attempt, we both mentored to a 60 Assassin. Mob and quest both green. Nada. </p><p> I petitioned but the GM said the quest was working according to design. In his response he mentioned to pay close attention to mentoring levels. We may try it again mentored to a 52 Mystic.</p>

Fyorwin
12-10-2007, 08:31 PM
<p>Well, mentoring to the 52 Mystic didn't work. I've tried hailing the mob to initiate quest dialogue and he ignores me. Do I have to /say "You're fired" while targetting him? If I bother trying this again I'll try that text and see.</p><p> Any other brilliant suggestions out there?</p>

Jindrack
12-14-2007, 05:41 PM
I have a fix for this one going in.  Something changed with how his pathing task worked on the backend.

Dracor
12-14-2007, 05:51 PM
Thanks for the dev response! It makes a huge difference to the community.

Terron
01-16-2008, 06:50 PM
<cite>Jindrack wrote:</cite><blockquote>I have a fix for this one going in.  Something changed with how his pathing task worked on the backend.</blockquote>Has the fix gone in?I just killed him again without getting an update.

Jindrack
01-17-2008, 02:39 PM
The fix looks like it will go in with the next GU.

Terron
01-17-2008, 09:02 PM
<cite>Jindrack wrote:</cite><blockquote>The fix looks like it will go in with the next GU.</blockquote>Thank you