Fixed some map quests

[topaz-next-bot]

Issue by Lynnea1320
Friday May 01, 2020 at 01:36:01
Originally opened as: project-topaz/topaz - Issue 558

---

I affirm:

• that I agree to Project Topaz's Limited Contributor License Agreement, as written on this date
• that I've tested my code since the last commit in the PR, and will test after any later commits

Some weren't giving proper rewards or key item notifications. Will push more as we find them.

[topaz-next-bot]

Comment by Lynnea1320
Monday May 04, 2020 at 02:08:07

---

No, that was what it was before and I'm getting reports for No Message from
players.

On Sun, May 3, 2020 at 5:09 PM TeoTwawki notifications@github.com wrote:

@TeoTwawki commented on this pull request.

In scripts/zones/Northern_San_dOria/npcs/Aurege.lua
project-topaz/topaz#558 (comment):

@@ -41,6 +41,7 @@ function onEventFinish(player, csid, option)
if csid == 521 and player:getQuestStatus(SANDORIA, tpz.quest.id.sandoria.EXIT_THE_GAMBLER) == QUEST_AVAILABLE then
player:addQuest(SANDORIA, tpz.quest.id.sandoria.EXIT_THE_GAMBLER)
elseif csid == 516 then

•    npcUtil.completeQuest(player, SANDORIA, tpz.quest.id.sandoria.EXIT_THE_GAMBLER, {ki = tpz.ki.MAP_OF_KING_RANPERRES_TOMB, title = tpz.title.DAYBREAK_GAMBLER, xp = 2000})
  

•    npcUtil.completeQuest(player, SANDORIA, tpz.quest.id.sandoria.EXIT_THE_GAMBLER, {ki = tpz.ki.MAP_OF_KING_RANPERRES_TOMB, title = tpz.title.DAYBREAK_GAMBLER, xp = 2000 * EXP_RATE})
  

•    player:messageSpecial(ID.text.KEYITEM_OBTAINED, tpz.ki.MAP_OF_KING_RANPERRES_TOMB) -- Map of King Ranperre's Tomb
  

npcUtil.completeQuest(player, SANDORIA,
tpz.quest.id.sandoria.EXIT_THE_GAMBLER, {keyItem =
tpz.ki.MAP_OF_KING_RANPERRES_TOMB, title = tpz.title.DAYBREAK_GAMBLER, xp =
2000 * EXP_RATE}) didn't work?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
project-topaz/topaz#558 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJIPZIGHUR5J77FAD3XEHDTRPXMPTANCNFSM4MWY77AA
.

[topaz-next-bot]

Comment by ibm2431
Monday May 04, 2020 at 03:32:17

---

It's always been broken