Comments about FuBar_QuestsFu

Comment #43

no-reply@curseforge.com (belleboyd) — Tue, 25 Aug 2009 03:11:37 +0000

Just picked up an error:

Date: 2009-08-24 22:17:53 ID: 1 Error occured in: Global Count: 1 Message: ...\AddOns\FuBar_QuestsFu\PlayerNotify\PlayerNotify.lua line 102: bad argument #2 to 'format' (number expected, got string) Debug: (tail call): ? (tail call): ? [C]: format() ...\AddOns\FuBar_QuestsFu\PlayerNotify\PlayerNotify.lua:102: ?() ...er3\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146: ...er3\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146 [string "safecall Dispatcher[8]"]:4: [string "safecall Dispatcher[8]"]:4 [C]: ? [string "safecall Dispatcher[8]"]:13: ?() ...er3\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:91: Fire() ...FuBar_QuestsFu\lib\LibQuixote-2.0\LibQuixote-2.0.lua:360: ?() ...FuBar_QuestsFu\lib\LibQuixote-2.0\LibQuixote-2.0.lua:115: ...FuBar_QuestsFu\lib\LibQuixote-2.0\LibQuixote-2.0.lua:114

Comment #42

no-reply@curseforge.com (wxx011) — Mon, 24 Aug 2009 05:12:02 +0000

sorry,I have a error

"FuBar_QuestsFu-r43802
PartyNotify
PartyNotify.lua:66: attempt to concatenate local 'title' (a boolean value)\nCallbackHandler-1.0-3:146: in function <...oot
Libs
CallbackHandler-1.0
CallbackHandler-1.0.lua:146>\n<string>:\"safecall Dispatcher[4]\":4: in function <[string \"safecall Dispatcher[4]\"]:4>\n<in C code>: ?\n<string>:\"safecall Dispatcher[4]\":13: in function `?'\nCallbackHandler-1.0-3:91: in function `Fire'\nLibQuixote-2.0-90081:515: in function `?'\nLibQuixote-2.0-90081:548: in function `?'

Comment #41

no-reply@curseforge.com (2drunk2funk) — Tue, 11 Aug 2009 11:10:30 +0000

Would be nice to get this fixed, really like the functionality and the Job done sound!

QH quest tracking is not as nice as this.

Comment #40

no-reply@curseforge.com (xevilgrin) — Sat, 08 Aug 2009 13:00:11 +0000

@slipfoot: same here on german client ... thats an issue since 3.2 ...only deactivating can stop that behavior at the moment

please Kemayo bring Questfu on uptodate status .. i miss indeed the "Jobs done" sound

@D-Town & Riega ... thank you for your overlook and ideas... your find/replacement suggestions for workaround are helping indeed

Comment #39

no-reply@curseforge.com (slipfoot) — Sat, 08 Aug 2009 10:18:16 +0000

Since Patch 3.2 I am not able to accept any Quests. Clicking on the button 'Accept' simply has no effect. Just tested wit r413. After deactiviating FuBar_QuestsFu accepting of quests is functioning again. Can anyone confirm this behaviour?

Comment #38

no-reply@curseforge.com (justcallmefred) — Thu, 06 Aug 2009 20:23:11 +0000

Would anyone be willing to upload a working version anywhere? Even if the stated it's only temporary until the author uploads a working version..

Comment #37

no-reply@curseforge.com (Riega) — Thu, 06 Aug 2009 14:02:46 +0000

D-Town, many thanks. I added in details/details.lua Find/Replace - Replace "GetDifficultyColor" with "GetQuestDifficultyColor" to get rid of an other error.

Comment #36

no-reply@curseforge.com (wetllama) — Wed, 05 Aug 2009 21:18:54 +0000

D_Town,

Thank you for digging through the logs and finding those. You're a life saver! :)

Comment #35

no-reply@curseforge.com (D_Town) — Wed, 05 Aug 2009 19:11:01 +0000

I haven't tested this much, but this seems to work so far. I'm not much of a lua developer, but I can certainly look at diff logs and try to make sense of them :)

1. QuestsFu.lua: Find/Replace - Replace "QuestDifficultyColor" with "QuestDifficultyColors"

2. QuestsFu.lua: Find/Replace - Replace "GetDifficultyColor" with "GetQuestDifficultyColor"

3. Blizz\Blizz.lua: Find/Replace - Replace "QUESTS_DISPLAYED" with "#QuestLogScrollFrame.buttons"

Comment #34

no-reply@curseforge.com (Woundheir) — Wed, 05 Aug 2009 16:15:41 +0000

Its been partially broken for a long time :( not thinking its getting fixed.