Better Stacktraces
After looking at too many stacktraces to count, I decided to make this to make developers' lives just a bit easier. It's also useful for users who run into errors. They can report more useful information to developers. Also, you'll know exactly which mod the error is from. No more guessing based of namespaces and method names only.
New!
Introducing XML error detection. When there's XML in an error, this mod will tell you the potential sources for that error. It also can pick up errors that don't have XML in them specifically, but that related to XML in some way, such as cross reference errors.
What's a Stacktrace?
A stacktrace is the long string of information that you see when you look at a message, warning, or error in the log. Developers use this information to debug the source of errors in their mods. That information comes from Unity, but useful information is stripped out when it finally gets to your log.
What Does it Do?
This overrides the default RimWorld stacktrace with my own.
Features include:
[list]
[*] Mod name or source
[*] Assembly name
[*] Method parameter types and names
[*] File names*
[*] Line numbers*
[*] XML errors
[/list]
*File names and line numbers are only available if debugging information is found. e.g. The failing mod in question has .pdb debugging symbols next to the assembly in the mod's folder. Since this data is not available to any of RimWorld's or System assemblies, it will never pick up on that information.
Compatibility
[list]
[*] Visual Exceptions
[/list]
To Do
[list]
[*] Add support for more error types
[/list]
Note: Due to the nature of mod loading, this can't modify stacktraces that came before this mod loaded.
