ErrorAnalyzer

Error Analyzer

A diagnostic tool for Dyson Sphere Program that enhances error reporting and helps identify possible problematic mods.

Features

• Close button: The top-left X button can close the error window and continue playing. (Note: the autosave is still disabled).
• Copy button: The middle button can copy the error message to the clipboard in style format.
• Inspect button: Left click to navigate to the erroring machine, right click to toggle the DEBUG tracking mode.
• Enhance Message: Show the possible candidates of the mods that may cause the error, and related patches on the stack trace.

Usage

Understanding Error Messages

When an error occurs, you'll see an enhanced error message with:

• Game version and loaded mod plugins count
• Possible mod candidates that might be causing the issue
• Error details with a cleaned-up stack trace
• Details of any related Harmony patches

Troubleshooting Mods

The error dialog will show "possible candidates" for problematic mods. This isn't always conclusive, but provides a good starting point for troubleshooting. Try:

• Disabling the suggested mods (if it is not save-dependent)
• Updating mods to their latest versions
• Checking for known conflicts between the identified mods

Navigating to Problem Entities

If an entity (factory machines, belt, etc.) is identified as part of the running error:

• Click on the [Inspect button] to enter DEBUG mode (the button will turn green)
• When the error occur again, it will capture the location and move mecha to that entity in the game world
• If the entity is not on the same planet, a navigation line will guide to the planet
• Some types of entity can only be tracked in single-threaded mode

Sharing Error Information

To report errors to mod developers:

• When an error occurs, click the [Copy button] in the dialog
• Hold Shift while clicking to include the full mod list if need
• Paste the copied text in Discord, GitHub issues, or mod forums

Example

Below is an example of the error message that can be copied to your clipboard:

Error report: Game version 0.10.32.25783 with 10 mods used.
possible candidates: [ErrorAnalyzer1.3.0][ErrorTester1.0.0]
IndexOutOfRangeException: Index was outside the bounds of the array.
StationComponent.DetermineDispatch (float shipSailSpeed, float shipWarpSpeed, int shipCarries, int priorityIndex, StationComponent[] gStationPool, FactoryProductionStat[] factoryStatPool, PlanetFactory[] factories, GalaxyData galaxy, TrafficStatistics tstat); (IL_0DB2)
GalacticTransport.GameTick (long time); (IL_00FD)
GameData.GameTick (long time); (IL_01DC)
GameMain.FixedUpdate (); (IL_017B)
[== Mods on stack trace ==]: [ErrorAnalyzer]
void ErrorAnalyzer.Testing.Plugin::DetermineDispatch_Postfix(); DetermineDispatch(Postfix)

Explanation:

• The first line shows the current game version and how many mod plugins loaded.
• The second line shows the mod plugins that may be involved ([ErrorAnalyzer1.3.0][ErrorTester1.0.0]).
• The error was caused by a IndexOutOfRangeException in StationComponent.DetermineDispatch function.
• "Mods on stack trace" shows the assembly name that appear on the stack trace.
• Under it shows the harmony patches on the stack trace. In this case, ErrorAnalyzer.Testing.Plugin::DetermineDispatch_Postfix() is harmony postfix to StationComponent.DetermineDispatch, which is likely the cause of the error.

Notes:

• The namespace of the function typically corresponds to the mod name and the assembly name.
• The functions listed in the patch section may not directly relate to the error’s root cause. Generally, functions higher in the stack are more likely to be the cause, but other patches not listed in the stack trace may also be involved.
• Removing the erroring machine may or may not solve the issues, so backup the save before dismantling. Sometimes you'll need more powerful purge tools e.g. Re-intialize planet in UXAssist. If they still not work then you'll have to roll back to the previous normal save.
• When the following conditions are matched, the mods will be determinated as possible candidates:

1. Mods that appear directly in the stack trace (judge by namespace)
2. The first patched method on the stack trace, which is not the common patched functions (VFPreload, GameMain, ThreadManager.ProcessFrame)
3. Mods that modify the same type as the first function in the stack trace, if the first function is not mod or patched function

Config

The config file is BepInEx\config\aaa.dsp.plugin.ErrorAnalyzer.cfg, which can be found in mod manager's Config editor.

## Settings file was created by plugin ErrorAnalyzer
## Plugin GUID: aaa.dsp.plugin.ErrorAnalyzer

[DEBUG Mode]

## Enable DEBUG mode to track the entity when starting up the game
# Setting type: Boolean
# Default value: false
Enable = false

[Message]

## Show all mod patches on the stacktrace (By default it will not list GameData.Gametick() and below methods)
# Setting type: Boolean
# Default value: false
Show All Patches = false

## Dump Harmony patches of all mods when the game load in BepInEx\LogOutput.log
# Setting type: Boolean
# Default value: false
Dump All Patches = false

When the DEBUG tracking mode is on, the navigate button will change color. In this mode, it will track the entity that throws errors and move the player to the location when it is on the same planet. Errors in the following methods will be handled too in this mode to let the player dismantle the corrupted building: CargoTraffic.SetBeltState, CargoContainer.RemoveCargo, CargoTraffic.PickupBeltItems

错误分析

错误分析器mod一款适用于戴森球计划的诊断工具，可增强错误报告并帮助识别可能有问题的模组。

功能

• **关闭按钮(Cl