2020-03-06 09:53:52: ERROR[Main]: ServerError: AsyncErr: ServerThread::run Lua: Runtime error from mod 'tsm_pyramids' in callback LuaABM::trigger(): ...n/../games/ENLIVEN/mods/codercore/tsm_pyramids/mummy.lua:398: attempt to index a nil value
2020-03-06 09:53:52: ERROR[Main]: stack traceback:
2020-03-06 09:53:52: ERROR[Main]:       ...n/../games/ENLIVEN/mods/codercore/tsm_pyramids/mummy.lua:398: in function <...n/../games/ENLIVEN/mods/codercore/tsm_pyramids/mummy.lua:391>

These paths are theoretically fixable. Possible solutions:

• Collect valid paths from other parts of the log (not shown above).
• [-] Use some hard-coded locations (This would not be good, since could be a different copy of the program).
• Use the location of the output file itself.
  • This would be negated by piping (only if Accept standard input #2 is implemented), unless there is some way to get the location of the executable or script from which piping is occurring, or:
    • Allow a param for the directory containing source files to which error output refers.

The fix can occur during the analysis phase (before double-clicking the lines, outputinspector stores the path and other parameters as user data in the actual list item object).