Cannot Identify Most Recent Error in BugSack Due to Missing Timestamps

[fisken1991]

Describe the problem

I'm using the BugSack addon to track Lua errors in World of Warcraft, but I'm running into a problem where I cannot determine which error just occurred when I experience a freeze or lag spike during a dungeon.

BugSack collects multiple errors over time, but the entries don't have timestamps or ordering information that clearly tells me which one happened most recently. This makes it very difficult to identify the specific error that corresponds to the freeze or performance issue I'm trying to debug.

What steps will reproduce the problem?

1.Play through a dungeon with BugSack active.

2. Let multiple Lua errors accumulate in the BugSack error window.

3. Experience a sudden freeze or lag spike.

4. Open BugSack to review errors — there's no clear way to tell which error just occurred.

Expected Result: I should be able to identify the most recent error (ideally via a timestamp or clear ordering in the BugSack window).

Actual Result: BugSack shows a list of errors, but there's no indication of when they occurred, making it hard to tell which one is relevant to a recent freeze or lag.