Quest Reward Crashing Client

[Scatman]

This specific quest reward is crashing the client. The crash occurs right when you are supposed to receive the quest. You never see the quest accept/decline dialog pop up however. I'm using this item:

Code: Select all

AddQuestRewardItem(Quest, 2393, 1)

When this line is commented out in the quest script the quest is given and no errors occur. The item is "a small lab flask". I think it's a house item if that means anything.
Here is a screen shot of the error:

[LethalEncounter]

Cool, never seen that error before. I'll check it out.

[Scatman]

The quest is called "glowmyst juice" in oakmyst forest in case you want to see it crash for yourself. Just un-comment that line.

[LethalEncounter]

Could you verify this is still a bug using the latest client and world exe whenever John updates? I couldn't reproduce it.

[John Adams]

Tess Updated.

[Scatman]

I am still getting it in rev 142. I am using client 5082T. You know what though? There is something wrong with this quest because even when I do comment out that reward, I still cannot obtain the quest. The quest dialog shows but nothing happens when I accept it. Let me try to figure out what is up with this quest/spawnscript and then I'll try again.

[LethalEncounter]

If it displays the quest but doesnt do anything when you accept it, it is more than likely a bug with the item. I have gotten a few of those this morning and was able to fix them all (or so I thought). Let me know which item id you are using and I'll try to reproduce it.

[John Adams]

IMO, Tess' items table is probably not something we should be using. Once I have time to evaluate the parsed items from all our logs, we might have a more realistic Items selection.
I thought we were going to use "Pounce" until we got items done?

[Scatman]

Ha yeah but if the item already exists in the db I figured I'd throw it in there. I have even tried giving it no quest reward and I still can't get the quest. Should I set them all to pounce if item ids are going to be changing in the future?

[John Adams]

I would. We know Pounce works as an item, at least.
I liked how you did it previously, putting some comment in about needing the proper item_id. If you make some common text comment like "ITEM_ID NEEDED", we can search for those scripts later and update them easier.
But this is your domain, so whatever you want to do really. Once I get passed Convos and Quest scripts, I will finish the items editor so you can tweak later.

[LethalEncounter]

That might be a good idea, because then when your items are done I can easily debug an entire type of item at once.

[Scatman]

Ok, I'll change them back to Pounce II with a comment above each QuestReward on the name of the item that is supposed to go there. This actually reminds me of something I forgot to request. We'll eventually need to have more than 1 quest reward (which we can do), but then only allow the player to select only 1 of the x rewards after finishing.

[Scatman]

Alright so it was the other item (there were 2 rewards) that was preventing me from getting the quest. So one item crashed the client, the other just wasn't allowing the quest to be accepted.

[LethalEncounter]

It was probably the item that prevented you from getting the quest which caused both issues. What was that item id?

[Scatman]

Yeah it was.
The item that crashed the client was "a small lab flask" with id 2393.
The item that didn't allow me to get the quest was "small hip bag" with id 2232.