Got the following error upon entering Terokkar Forest:
[2007/06/11 16:28:45-1275-x1]: Cartographer_QuestObjectives\addon.lua:1391: attempt to index local 'value' (a nil value)
---
the prebuilt databases have some of the table Key's missing so u'll get this error , least for me, alot when it trys to itterate thought the SV file expecting something that's not there.
QuestObjectives ought to clean out the entries so that the error only happens once.
it happens for every iteration of a zone, eventually yes they do go away, after it's had time to look at each note in detail and fill in the missing values.
[2007/08/14 16:35:35-256-x106]: Cartographer_Quests\addon.lua:1279: attempt to index local 'value' (a nil value)
---
[2007/08/14 16:39:02-256-x6]: Cartographer_Quests\addon.lua:1279: attempt to index local 'value' (a nil value)
Cartographer_Notes-2.0\Notes.lua:2554: in function <Interface\AddOns\Cartographer_Notes\Notes.lua:2550>
Dewdrop-2.0-44792 (DewdropLib):1870: in function <...erface\AddOns\DewdropLib\Dewdrop-2.0\Dewdrop-2.0.lua:1819>
Dewdrop-2.0-44792 (DewdropLib):1884: in function `Refresh'
PitBull-r45121\PitBull.lua:3410: in function `_UpdateLayouts'
PitBull-r45121\PitBull.lua:5834: in function `ChangeConfigMode'
PitBull-r45121\PitBull.lua:2692: in function `OnClick'
FuBarPlugin-2.0-44269:937: in function <...\FuBarPlugin-2.0\FuBarPlugin-2.0\FuBarPlugin-2.0.lua:934>
FuBar-33424\FuBar.lua:1120: in function <Interface\AddOns\FuBar\FuBar.lua:1118>
---
[2007/08/14 16:39:33-256-x5]: Cartographer_Quests\addon.lua:1279: attempt to index local 'value' (a nil value)
Cartographer_Notes-2.0\Notes.lua:2554: in function <Interface\AddOns\Cartographer_Notes\Notes.lua:2550>
Dewdrop-2.0-44792 (DewdropLib):1870: in function <...erface\AddOns\DewdropLib\Dewdrop-2.0\Dewdrop-2.0.lua:1819>
Dewdrop-2.0-44792 (DewdropLib):1884: in function `Refresh'
PitBull-r45121\PitBull.lua:3410: in function `_UpdateLayouts'
PitBull-r45121\PitBull.lua:5834: in function `ChangeConfigMode'
PitBull-r45121\PitBull.lua:2694: in function `OnClick'
FuBarPlugin-2.0-44269:937: in function <...\FuBarPlugin-2.0\FuBarPlugin-2.0\FuBarPlugin-2.0.lua:934>
FuBar-33424\FuBar.lua:1120: in function <Interface\AddOns\FuBar\FuBar.lua:1118>
these errors are normal, they should only happen once per NODE in a given region, then never again as it's attempting to read a value from a table that isn't there by design of the CMT.
these errors are normal, they should only happen once per NODE in a given region, then never again as it's attempting to read a value from a table that isn't there by design of the CMT.
:: Stop Stressing about it :: and reload ur UI :P
UI errors should never result from the normal operation of an addon. A nil check should really be placed in the code to prevent it from throwing an error :P
these errors are normal, they should only happen once per NODE in a given region, then never again as it's attempting to read a value from a table that isn't there by design of the CMT.
:: Stop Stressing about it :: and reload ur UI :P
UI errors should never result from the normal operation of an addon. A nil check should really be placed in the code to prevent it from throwing an error :P
true it's annoying
Quote from Barracuda »
I think those errors would not appear if the Addon would be used as intended.
When i got it right it results from merging databases externally.
The solution is easy: only use your own gathered data and you wont get the error ! ;-)
i wouldn't call this a solution, but more a cop-out; as this error doesn't introduce any apparent issues or problems in operation.
UI errors should never result from the normal operation of an addon. A nil check should really be placed in the code to prevent it from throwing an error :P
Couldn't agree more. Normally I'd immediately throw away an addon that spewed out Lua errors like this. I guess I am accepting them because this addon is simply too useful. While it does seem like there are no bad effects of these errors, I really do hope the author or current maintainer will do something about them. If it happened in a program I had developed, I would feel embarrassed.
I patched one of the errors in my own copy by simply checking for nil and then doing nothing. That has worked fine so far it seems.
UI errors should never result from the normal operation of an addon. A nil check should really be placed in the code to prevent it from throwing an error :P
Couldn't agree more. Normally I'd immediately throw away an addon that spewed out Lua errors like this. I guess I am accepting them because this addon is simply too useful. While it does seem like there are no bad effects of these errors, I really do hope the author or current maintainer will do something about them. If it happened in a program I had developed, I would feel embarrassed.
I patched one of the errors in my own copy by simply checking for nil and then doing nothing. That has worked fine so far it seems.
Yeah I should patch my local copy as well, and maybe dump some debug data to see what is actually going on.
[2007/09/01 22:49:29-1058-x1]: Cartographer_QuestObjectives\addon.lua:922: attempt to perform arithmetic on local 'numGot' (a string value)
AceEvent-2.0-44693 (FuBar):728: in function <...face\AddOns\FuBar\libs\AceEvent-2.0\AceEvent-2.0.lua:715>
<in C code>: ?
AceEvent-2.0-44693 (FuBar):363: in function <...face\AddOns\FuBar\libs\AceEvent-2.0\AceEvent-2.0.lua:341>
First, great job on a very Cartographer addon with a great way of managing the number of quest objective points on a map. The expanding point size is brilliant! Thanks for the hard work. :)
I seem to have many quest objectives in my saved data, and for some reason they don't show up, even with all the filters set and options to hide various kinds turned off.
I started playing around with your mod (and cartographer) about a week ago, and recently started having an issue after I turned on guild-sharing and show party objectives. At first it seemed to be working, I got lots of points showing up for my brother's quests and mine (he was also just starting to play with this and was in my party) so the points must have come form my guild sharing.
Anyway I was looking around as the points and decided to delete some from the guild, and just see what I got from him collecting objectives. This is when things seemed to start to break... Nothing showed up from him, if I removed the points I had received from the guild members, or alone.
A good example is for 1 quest specifically. I saw a point for "Don't Kill the Fat One" in Terokkar Forest so I figured I'd delete all the point form a guild member and see how it would show up again from my brother when he finished it. (we where about to start that one for him) the point never showed up, even when I used the manual request from group and it didn't seem to change.
I ended up looking around in the SavedVariables file (can't see how you actually record the points coords), and Don't Kill the Fat One is in the file, with my brothers name associated with it, but it never shows up when I try to set the options to show everything...
This has completely stopped working for me. I get 16 errors of the same type as those listed above that it is said in here is "normal". I can't say they are normal in my case. They started appearing about 3-4 days ago, about the same time quest objectives stopped appearing in the map.
Edit: re-installed with externals and these go away. This is related to Quioxte not being found. I beleve this is an issue in the standard lib as ony "Quioxte" is listed there, but your mod is calling "Quioxte-1.0"
What needs to be done to correct the standard lib in this case? These mods should work without embedding all the shared libs, especially for people like me who have minimal memory configs
If you are referring to my post OrionShock, I think I made it clear that I set the settings so I can see everything in my data (in theory), and I can't see many things... Other stuff shows up, but many that I had seen, are now gone. (but some form of them are in the saved data)
I'm looking over the Kara map, and it seems like the stuff is rotated like 45?, and very small. And some points don't seem to be in the right places? they are are out in the black areas wile most others do seem to be in the right place.. Odd.
for example, I have a grey question mark ? in the black area for Koren, and Prince Malchezaar is out in the black.
[2007/10/06 21:20:01-1307-x1]: Cartographer_QuestObjectives\addon.lua:922: attempt to perform arithmetic on local 'numGot' (a string value)
AceEvent-2.0-49307 (Ace2):735: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:722>
<in C code>: ?
AceEvent-2.0-49307 (Ace2):367: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:345>
Cartographer_QuestObjectives is the only addon I'm running using Quixote (verified doing a full text search of my Addons folder ;)). Also posted this in the libraries section, as the error that comes up only references Quixote.
A single error that reoccurs an average of 200+ times per session when in a party or raid (not solo):
Quixote-1.0-47871 (Quixote):621: table index is nil.
Has been doing this since the day WoW 2.2.3 went live. Last occurrence of this error was Oct 14/07 (again since other post) with Quixote r49795, Cartographer_QuestObjectives r50676 & Cartographer (Rock) r51988. All Ace2 & Rock libraries (& Quixote) are standalone & fully updated here.
Disabled quest objective note sharing in Cartographer soon after the problem started; no change.
Just made the switch from Cartographer_QuestObjectives to Mobmap and must admit its nice to have an addon that doesn't spit errors at you all the time and is kept up to date.
Also like the way MobMap handles its data, its broken up and only accesses what it needs so its far more memory efficient, its not at the top of performancefu like QuestObjectives always was.
I recommend people try it until this one gets a rewrite.
Tat
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
QuestObjectives ought to clean out the entries so that the error only happens once.
[2007/08/14 12:30:22-255-x30]: Cartographer_Quests\addon.lua:1279: attempt to index local 'value' (a nil value)
---
Any idea how to fix this as it can mount up to hundreds over a few hours
[2007/08/14 16:35:35-256-x106]: Cartographer_Quests\addon.lua:1279: attempt to index local 'value' (a nil value)
---
[2007/08/14 16:39:02-256-x6]: Cartographer_Quests\addon.lua:1279: attempt to index local 'value' (a nil value)
Cartographer_Notes-2.0\Notes.lua:2554: in function <Interface\AddOns\Cartographer_Notes\Notes.lua:2550>
Dewdrop-2.0-44792 (DewdropLib):1870: in function <...erface\AddOns\DewdropLib\Dewdrop-2.0\Dewdrop-2.0.lua:1819>
Dewdrop-2.0-44792 (DewdropLib):1884: in function `Refresh'
PitBull-r45121\PitBull.lua:3410: in function `_UpdateLayouts'
PitBull-r45121\PitBull.lua:5834: in function `ChangeConfigMode'
PitBull-r45121\PitBull.lua:2692: in function `OnClick'
FuBarPlugin-2.0-44269:937: in function <...\FuBarPlugin-2.0\FuBarPlugin-2.0\FuBarPlugin-2.0.lua:934>
FuBar-33424\FuBar.lua:1120: in function <Interface\AddOns\FuBar\FuBar.lua:1118>
---
[2007/08/14 16:39:33-256-x5]: Cartographer_Quests\addon.lua:1279: attempt to index local 'value' (a nil value)
Cartographer_Notes-2.0\Notes.lua:2554: in function <Interface\AddOns\Cartographer_Notes\Notes.lua:2550>
Dewdrop-2.0-44792 (DewdropLib):1870: in function <...erface\AddOns\DewdropLib\Dewdrop-2.0\Dewdrop-2.0.lua:1819>
Dewdrop-2.0-44792 (DewdropLib):1884: in function `Refresh'
PitBull-r45121\PitBull.lua:3410: in function `_UpdateLayouts'
PitBull-r45121\PitBull.lua:5834: in function `ChangeConfigMode'
PitBull-r45121\PitBull.lua:2694: in function `OnClick'
FuBarPlugin-2.0-44269:937: in function <...\FuBarPlugin-2.0\FuBarPlugin-2.0\FuBarPlugin-2.0.lua:934>
FuBar-33424\FuBar.lua:1120: in function <Interface\AddOns\FuBar\FuBar.lua:1118>
---
:: Stop Stressing about it :: and reload ur UI :P
UI errors should never result from the normal operation of an addon. A nil check should really be placed in the code to prevent it from throwing an error :P
When i got it right it results from merging databases externally.
The solution is easy: only use your own gathered data and you wont get the error ! ;-)
true it's annoying
i wouldn't call this a solution, but more a cop-out; as this error doesn't introduce any apparent issues or problems in operation.
Couldn't agree more. Normally I'd immediately throw away an addon that spewed out Lua errors like this. I guess I am accepting them because this addon is simply too useful. While it does seem like there are no bad effects of these errors, I really do hope the author or current maintainer will do something about them. If it happened in a program I had developed, I would feel embarrassed.
I patched one of the errors in my own copy by simply checking for nil and then doing nothing. That has worked fine so far it seems.
Yeah I should patch my local copy as well, and maybe dump some debug data to see what is actually going on.
AceEvent-2.0-44693 (FuBar):728: in function <...face\AddOns\FuBar\libs\AceEvent-2.0\AceEvent-2.0.lua:715>
<in C code>: ?
AceEvent-2.0-44693 (FuBar):363: in function <...face\AddOns\FuBar\libs\AceEvent-2.0\AceEvent-2.0.lua:341>
I seem to have many quest objectives in my saved data, and for some reason they don't show up, even with all the filters set and options to hide various kinds turned off.
I started playing around with your mod (and cartographer) about a week ago, and recently started having an issue after I turned on guild-sharing and show party objectives. At first it seemed to be working, I got lots of points showing up for my brother's quests and mine (he was also just starting to play with this and was in my party) so the points must have come form my guild sharing.
Anyway I was looking around as the points and decided to delete some from the guild, and just see what I got from him collecting objectives. This is when things seemed to start to break... Nothing showed up from him, if I removed the points I had received from the guild members, or alone.
A good example is for 1 quest specifically. I saw a point for "Don't Kill the Fat One" in Terokkar Forest so I figured I'd delete all the point form a guild member and see how it would show up again from my brother when he finished it. (we where about to start that one for him) the point never showed up, even when I used the manual request from group and it didn't seem to change.
I ended up looking around in the SavedVariables file (can't see how you actually record the points coords), and Don't Kill the Fat One is in the file, with my brothers name associated with it, but it never shows up when I try to set the options to show everything...
attached is my current data file. Any ideas??
Edit: re-installed with externals and these go away. This is related to Quioxte not being found. I beleve this is an issue in the standard lib as ony "Quioxte" is listed there, but your mod is calling "Quioxte-1.0"
What needs to be done to correct the standard lib in this case? These mods should work without embedding all the shared libs, especially for people like me who have minimal memory configs
for example, I have a grey question mark ? in the black area for Koren, and Prince Malchezaar is out in the black.
AceEvent-2.0-49307 (Ace2):735: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:722>
<in C code>: ?
AceEvent-2.0-49307 (Ace2):367: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:345>
A single error that reoccurs an average of 200+ times per session when in a party or raid (not solo):
Quixote-1.0-47871 (Quixote):621: table index is nil.
Has been doing this since the day WoW 2.2.3 went live. Last occurrence of this error was Oct 14/07 (again since other post) with Quixote r49795, Cartographer_QuestObjectives r50676 & Cartographer (Rock) r51988. All Ace2 & Rock libraries (& Quixote) are standalone & fully updated here.
Disabled quest objective note sharing in Cartographer soon after the problem started; no change.
I hope nothing happened to him and he will come back soon ...
If you ever read me, thank you for this addon,
I' m desperately waiting for the total rewrite you told us about 6 months away ^^
Or someone will drop an eye in it, Questobjectifs must stay alive.
Thank you for it :)
Also like the way MobMap handles its data, its broken up and only accesses what it needs so its far more memory efficient, its not at the top of performancefu like QuestObjectives always was.
I recommend people try it until this one gets a rewrite.
Tat