Runtime error row numbers are incorrect, unable to jump to line with error

Context

I am working on a TTS mod that has a Global.-1.ttslua file and multiple object scripts. In each of these scripts there is only a single #include line, which imports code in that I keep under source control -- similar to the setup in this post.

Issue

When I click on an object in-game that runs some code with a runtime error, the row number in the error message is relative to the concatenated file that has all of the included code in it.

For example, I could have files a.ttslua, b.ttslua, and c.ttslua all with 100 lines each, which are then included in the global script. If the error happened on line 55 of b, the error message would show row 155. If I click on <- Jump to Error, I am brought to the original parent file that includes the subsequent files.

This makes debugging very tedious and time-consuming.

Specific Example

Here is an error message I get clicking on a button in-game. The actual error is trying to call a function on a nil value, just used as an example. Note that no file has over 100 lines.

Jumping to the error, I am brought in Atom to a file containing only this:

#include <4PlayerHeroRealms/scripts/ui/Discard Hand p1>

That file contains only this:

#include ../sizes
#include ../messages

function onLoad()
  -- some other code here, but importantly the click function calls ...
  params = {1} -- player
  Global.call("discardActive", params)
end

After some manual investigation, the error is actually in the discardActive function within a file called 4PlayerHeroRealms.ttslua that is included by the global script file. I found this out by copy-pasting the concatenated global script file from the in-game editor to another text editor and looked up the line number 197, which was zone.doSomething() where zone was accidentally nil.

Berserk-Games / atom-tabletopsimulator-lua