When lua throws a panic after attempting to call a nil value, no message is supplied to CustomPanicHandler in ModManager.cpp. The default message handler gets the error message.
To Reproduce
Steps to reproduce the behavior:
Add a nil function call to a lua file (ex add core.print("message") as this doesn't actually exist as a registered function
Run game and observe generic error
Comment out panic handler registration in ModManager.cpp m_luaState.set_panic( sol::c_call<decltype(&CustomPanicHandler), &CustomPanicHandler>);
Run again and observe default panic handler throws verbose error
Expected behavior
We should be getting the same error as the default panic handler
Describe the bug
When lua throws a panic after attempting to call a nil value, no message is supplied to CustomPanicHandler in ModManager.cpp. The default message handler gets the error message.
To Reproduce
Steps to reproduce the behavior:
core.print("message")
as this doesn't actually exist as a registered functionm_luaState.set_panic( sol::c_call<decltype(&CustomPanicHandler), &CustomPanicHandler>);
Expected behavior
We should be getting the same error as the default panic handler
Additional context
Last occurred in commit a1adf386