|
Diametra wrote:SCAMP help!!
I downloaded the latest beta version to try out fresh on the pve realm. Had this error message stuck right in the middle of my screen that cannot be cleared with out removing the add-on questie.
Questie Quest lua 507 attempt to call local value type function (a nil value) I fixed it on the pve realm by replacing questie with a version completed on or around may 8th.
Unfortunately i tried it on the pvp realm too. replaced it with the older version. Now, the addon screen refers to the newer version no mater which i have installed. The checkbox is for BETA version 2x regardless of what is actually in the addons folder. It has the error messge perma stuck no matter which version I put in Addons.
http://imgur.com/gallery/UJwDyTV/new
dang....how irritating is imgur? I've had this image up there for like two minutes and it has 63 views and a -8 rating and someone from the peanut gallery commenting, with authority of how unimportant it is. WTF.
|
|
Paradox77 wrote:Hello guys,
first of all sorry for my bad english
i have read the whole thread but still have 3 questions.
- when i update questie or delte the saved variables Folder, do questie still knows which quests i have allready done? (or should i always copy the saved variables for questie ?)
- questie Shows so many Icons on the minimap for all quests (not only tracked ones) is this normal? (i dont talk from the ? and ! thats just fine)
- the questtracker shows the quests as not tracked but it is tracked in questie, only gos away when i reload questie and uncheck the quests in the log.
thanks in advanced
Diametra wrote:Ya...I'm telling you I had the latest one in there..it caused this frozen error screen...I removed it completely and put in an older version. Which works fine on the pve server.
I replaced it on pvp server with old one too. The start-up menu is still referring to the beta one 2.x whch is no longer present. the error is still on the screen. Where is this thing located: !QuestieCompatibility folders.
Update: I'll just tell you what I did. I downloaded every version from newest to oldest until one of them both worked and made the error dissapear. It was version 2.08 that did the trick.