Tomquest2 still doesn't give out any debug info with all my addons enabled, but with only tomquest2 enabled i get this error:
Message: ...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:19: Cannot find a library instance of "AceGUI-3.0".
Time: 10/09/09 22:22:16
Count: 1
Stack: [string "Interface\FrameXML\BasicControls.xml:<Scrip..."]:18: in function <[string "Interface\FrameXML\BasicControls.xml:<Scrip..."]:4>
[C]: ?
[C]: in function `error'
Interface\AddOns\tomQuest2\libs\LibStub\LibStub.lua:23: in function `LibStub'
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:19: in main chunk
Locals: (*temporary) = "Cannot find a library instance of "AceGUI-3.0"."
I am posting this error here because since i have the addon with embedded libraries i find it a bit strange, but you can correct me if my wrong.
I've just uploaded beta 31 I had to rename the ldb object for quest tooltip and daily quests so you might have to enable those if your ldb display hide them by default.
I had to rename those ldb objects to avoid conflicts with some ldb display. (tomQuest2 sub option panel were attached to tomQuest2 ldb option of the ldb display.
i hope that you are still maintaing this great addon. Did you had the chance to take a look at this problem? It is very sporadic. Sometimes the error also occurs when i accept new quests.
First of all thanks for this great addon, just a quick question, are you getting this ready for 3.3 as i took it on the PTR and it didn't play at all :(
Don't worry at all I'm still maintaining tomQuest2 I just had very little time recently and I used this time on the PTR so I already have a 3.3 ready tomQuest2:)
I also think that I fixed your problem on the PTR X-buZZ so I should just find what I did and backport it to 3.2 :)
Also on middle click on a quest on the tracker it will open the worldmap and show the quest objectives on the map.
I need to find a space on the tracker to add the icon with the POI number.
I'm also working on redesigning the tracker and quest tooltip to remove the need for LibQTip. I'll add some custom frames which should make things easier for me to maintain and enhance :)
tomQuest2-3.2 beta 32\core.lua:1427: attempt to concatenate local 'description' (a nil value)
- it occurs when hearting
- it occurs when teleporting or using portals
- it occurs when entering instances
- it occurs when accepting new quests
It would be really great if you could create a little hotfix or just tell me which lines i need to modify in order to get rid of it before your 3.3 release.
its not just the error. TomQuest totally stops working after this error.
in 3.1 and 3.2 there was a limitation on the number of quests /achievements that can be tracked, this limitation was based on the space available on screen. in 3.3 they replaced this limitation with a global variable that set a maximum number of quests/achievements trackable.
My 3.1 / 3.2 builds had some special code to remove the limitation based on space available, with this release I had to remove this code so you might encounter some problems related to space missing.
Tomquest2 still doesn't give out any debug info with all my addons enabled, but with only tomquest2 enabled i get this error:
I am posting this error here because since i have the addon with embedded libraries i find it a bit strange, but you can correct me if my wrong.
When i Shift right click a quest to link it in chat i no longer get a the quest name linked and the ability to click the questlink.
All i get now is "quest:NUMBER" ie "quest:4300" for the quest [Bone-Bladed Weapons]. This is the quest id right?
Hope you can fix this soon its rather annoying lol
Thanks and keep up the great work.
thanks for the report I'll fix that :)
This also occurs when you get the looting messages for a quest item.
Such as:
"You've looted 4300 which starts a quest"
ok thanks for the info, It'll be fixed in next release
I had to rename those ldb objects to avoid conflicts with some ldb display. (tomQuest2 sub option panel were attached to tomQuest2 ldb option of the ldb display.
since the latest release from curse i get the following error message when turning in quests:
After that, the quest tracker does not update any more until ui reload.
Can you please have a look at this?
Kind regards
X-buZZ
i hope that you are still maintaing this great addon. Did you had the chance to take a look at this problem? It is very sporadic. Sometimes the error also occurs when i accept new quests.
btw: i am on a german client.
Please keep up the great work!
Kind regards
X-buZZ
First of all thanks for this great addon, just a quick question, are you getting this ready for 3.3 as i took it on the PTR and it didn't play at all :(
Thanks again
Don't worry at all I'm still maintaining tomQuest2 I just had very little time recently and I used this time on the PTR so I already have a 3.3 ready tomQuest2:)
I also think that I fixed your problem on the PTR X-buZZ so I should just find what I did and backport it to 3.2 :)
Also on middle click on a quest on the tracker it will open the worldmap and show the quest objectives on the map.
I need to find a space on the tracker to add the icon with the POI number.
I'm also working on redesigning the tracker and quest tooltip to remove the need for LibQTip. I'll add some custom frames which should make things easier for me to maintain and enhance :)
I am looking forward to it.
Regards
i have more info about the following error:
- it occurs when hearting
- it occurs when teleporting or using portals
- it occurs when entering instances
- it occurs when accepting new quests
It would be really great if you could create a little hotfix or just tell me which lines i need to modify in order to get rid of it before your 3.3 release.
its not just the error. TomQuest totally stops working after this error.
Kind regards
X-buZZ
Here in europe 3.3 is released one day later. I assume that the new version will not work with 3.2 right?
Regards
X-buZZ
My 3.1 / 3.2 builds had some special code to remove the limitation based on space available, with this release I had to remove this code so you might encounter some problems related to space missing.
Other than that it should work.
I'm also on a European server :)