could not drop libdebugfile into Sid's

Anceane · 05/15/23, 09:32 PM

I crashed, and when i wanted to check the eventual addon error, i got this error :

The file is 1.121 kb

And if i want to read the file, it opens on one infinite line

Any idea what i can do ?

Thank you

sirinsidiator · 05/16/23, 04:53 AM

The saved data files have two forms. During regular gameplay it will store the data without white space to reduce the time it takes to write to disk. Only on logout or UI reload it will create a "proper" file.

My log viewer currently does not have the capability to read the compacted form of the save data files.
Since your game crashed, it never had an opportunity to store the data in this latter form which the viewer can read.

Given that the game only writes the save data once every 15 minutes, it's unlikely that the file contains any information about what happened right before the crash. So in the end it probably would not really help you anyway.

Anceane · 05/17/23, 10:34 AM

Thank you

undersand the how to now, and the reason

I just removed the file yesterday, and i guess i can delete it now

Since no crash, probably some corruption after several crash on Cyro

**Baertram** · 05/17/23, 10:36 AM

Best practice if LDL (LibDebugLogger) is active and you get a lua error popup:
If you get an error message (lua error popup) and LibDebugLogger was active:
At best note down time and date of the error.
Note how to reproduce (if you are able to).
Then do a /reloadui to properly save the current LibDebugLogger infos to the SavedVariabes file.
Afterwards upload the live/SavedVariables/LibDebugLogger.lua file here (https://sir.insidi.at/or/logviewer/ -> "Choose it from disk" button or drag&drop the LibDebugLogger.lua file there). At best copy it from your live/SavedVariables folder and create a backup so you got it for later usage some day too, as else it would be overwritten from ingame data one day soon.

Then inform the addon dev with linkt o the file, date + time the error happend and description how to reproduce the error.

sirinsidiator · 05/17/23, 12:25 PM

I've added a descriptive error message to the log viewer: