[Anceane]

ok, i will check in to see if the logs contains lua errors and then post them if needed.

though i can tell you than they can really grow more than 1-2 mb, i have 2 files up to 4 mb (i have older versions as i do regularly save of my savedvariables folder in case i encounter a big problem with new addon version).

But this is probably due to the fact that i have 2 accounts and log everyday each characters during the event (22 characters, and sometimes 11 more when i am courageous enough to log husband account so he can complete the event)

Now i have a question concerning :
character name - in case the problem occurs due to switching characters or due to some special characters in the name

i encounter from time to time actually some trouble with the save of addons, and it seems to be tied with the characters included in my account naming and names. The addons sometimes create two versions of my account. one with the correct naming and one with adding some characters, as some example shown in the spoiler below.
i find a way to correct that by leaving the game, editing the .lua by suppressing the wrong naming but if i create a new character the problem arise again.

Is there something i can do ?

Thank you

Warning: Spoiler

[247] =
{
[1] = 1556367908002,
[2] = "2019-04-27 08:25:08.002 -0400",
[3] = "I",
[4] = "LibDebugLogger",
[5] = "Initializing...\n@Esmeraüda\nAüran\n2019-04-25 16:06:36.440 -0400\neso.live.4.3.10.1774781\nNA Megaserver\n\nkeyboard\neso+\nen\nEnglish\naddon count: 136/138\nallow outdated",
[6] = "stack traceback:\nuser:/AddOns/AwesomeGuildStore/lib/LibDebugLogger/LibDebugLogger.lua:117: in function 'DoLog'\n<Locals> level = \"I\", tag = \"LibDebugLogger\", message = \"Initializing... @Esmeraüda...\", count = 1, now = 1556367908002, entry = tbl </Locals>\n[C]: in function 'pcall'\nuser:/AddOns/AwesomeGuildStore/lib/LibDebugLogger/LibDebugLogger.lua:125: in function 'Log'\n<Locals> level = \"I\", tag = \"LibDebugLogger\" </Locals>\nuser:/AddOns/AwesomeGuildStore/lib/LibDebugLogger/LibDebugLogger.lua:238: in function '(main chunk)'\n<Locals> LIB_IDENTIFIER = \"LibDebugLogger\", lib = tbl, LOG_LEVEL_DEBUG = \"D\", LOG_LEVEL_INFO = \"I\", LOG_LEVEL_WARNING = \"W\", LOG_LEVEL_ERROR = \"E\", NUM_MAX_ENTRIES = 10000, MAX_ENTRY_AGE = 86400000, STARTUP_LOG_TRACES = true, STARTUP_LOG_LEVEL = \"D\", LOG_LEVEL_TO_NUMBER = tbl, LOG_LEVEL_TO_STRING = tbl, STR_TO_LOG_LEVEL = tbl, startTime = 1556222796440, log = tbl, temp = tbl, defaultSettings = tbl, settings = tbl, IsFormattingString = user:/AddOns/AwesomeGuildStore/lib/LibDebugLogger/LibDebugLogger.lua:58, FormatTime = user:/AddOns/AwesomeGuildStore/lib/LibDebugLogger/LibDebugLogger.lua:65 </Locals>",

correct naming is : @Esmeraüda - character Aüran

Originally Posted by sirinsidiator That file is like a blackbox in a plane. It contains useful information for authors to figure out why an error is happening. It cleans itself up, so it shouldn't grow much larger than 1-2MB. Right now it logs the following information when you log in on a character: account name - in case you play with multiple accounts and that is somehow causing issues (e.g. with the saved variables) character name - in case the problem occurs due to switching characters or due to some special characters in the name login time - in case a problem occurs a fixed time after logging in on the character client version - hope that doesn't need an explanation megaserver - in case of server specific issues service type - steam or non-steam in case that makes a difference ui type - keyboard or console ui is quite an important detail eso+ - changes how some apis react language - in case it is some localization problem out of date checkbox state - good to know when someone has an issue with some addon not loading addon count - how many are active and how many are installed addon load events - this gives information about the load order of your addons, the loaded addon version and which subdirectory of the addon folder it was loaded from In addition it also logs Lua errors and addons can use the library to log custom messages. It also offers some settings to log even more information. There are 4 "levels" of log messages (debug, info, warning, error) and the default is to log everything except debug messages. Each message can also log a stack trace so an author knows where the log itself is coming from, which is also disabled by default. The goal for this is to make debugging easier for authors by providing a file that contains all the information users usually forget to mention.