When Bannerlord Windows server starts it opens a console and seems to be redirecting its standard output there. Consequently, any unhandled exception that would kill the program are also printed in that console, which is a shame since that console then gets close and the extremely valuable stack trace of the exception is lost forever. If the exception comes from managed code it can be found in the Windows event viewer but that's not the case when the issue is in native code.
A workaround I found was to attach a debugger which will pause the process before it exits, so we have time to read the exception.
Please consider getting rid of that console, and printing the logs directly in the standard output like in the Linux version.
A workaround I found was to attach a debugger which will pause the process before it exits, so we have time to read the exception.
Please consider getting rid of that console, and printing the logs directly in the standard output like in the Linux version.
