Pazyryk
Deity
- Joined
- Jun 13, 2008
- Messages
- 3,584
Failure to report Runtime Errors has been observed by several modders in this thread. I believe this started occuring in the vanilla pre-G&K patch back in June, 2012 (that's when I first observed the problem). It is present in current versions of vanilla and G&K. I did a fairly extensive test of the problem here, showing that the failure to print errors is limited to Lua chunks called by many (perhaps all?) GameEvents, but not Lua chunks called by Events or from the Live Tuner itself.
There is a more minor (but still annoying) issue that Runtime Error reports you do get always have a path name that is truncated such that you can't read the file name, only line number. Perhaps this is not really a bug (it might be Lua's debug.traceback default behavior) but I think it is worth mentioning in the context of error reporting.
If anyone is interested, I built a workaround in Lua for both of these problems here. It uses xpcall to contain your Lua errors and print traceback with non-truncated path names.
There is a more minor (but still annoying) issue that Runtime Error reports you do get always have a path name that is truncated such that you can't read the file name, only line number. Perhaps this is not really a bug (it might be Lua's debug.traceback default behavior) but I think it is worth mentioning in the context of error reporting.
If anyone is interested, I built a workaround in Lua for both of these problems here. It uses xpcall to contain your Lua errors and print traceback with non-truncated path names.
