ModVersionChecker

ModVersionChecker

Forgot the version of installed mod?

Not knowing mod got updated?

An in-game mod version checker might just right for you.

The mod display all installed BepInEx plugins' version and tries to fetch newer version.

Default hotkey for toggling mod's window is LeftCtrl + F5

Installation

• Put ModVersionChecker.dll into the BepInEx plugins folder,

e.g. C:\Program Files x86 \Steam\steamapps\common\Dyson Sphere Program\BepInEx\plugins\ModVersionChecker.dll

ModDataList

ModDataList holds references mapping from mods' full name to actual GUID in BepInEx. Checker would

not understand which package is related to installed plugin if it's not listed thus not able to check

newer version for it.

ModDataList used in checker can be found here: Github.../ModDataList.xml Checker will try to fetch this list at game launch

Add mod info to ModDataList

Recommended:

• Create Pull Request on

file ModDataList.xml

to repository

• Or file an issue request for adding new mod info
• Once merged, checker will fetch it on the next launch

Locally:

• Add mod info into local XML file located at DSPGameRoot\BepInEx\data\ModVersionChecker\PreservedModData.xml
• Entries in this file will overwrite entries fetched online

FAQ

• Latest version showing Unsupported
• Checker is fetching mod data list, or the mod is not found in mod data list, all mods listed in here are

supported: Github.../ModDataList.xml

• The current version is not correct, I've made sure the installed mod is the latest
• Mod developer did not change the version fed into BepInEx in code upon releasing
• Temporarily solution is to click the Set As Lastest button to set a custom version for that mod same as the

latest version. Checker will assume custom version as installed version later on. Custom versions are saved

at DSPGameRoot\BepInEx\data\ModVersionChecker\CustomModCurrentVersionList.xml

• Mods like QTool_Model_plus showing wrong latest

version

• Mod developer did not change the GUID of his modified mod, checker use GUID to identify mods. In this case, it

points to the original mod

• Once Set As Latest was used, updated plugin not getting correct current version
• Resolved in v1.2
• Mod was supported, but now showing Unsupported after update
• Mod developer changed mod's GUID, please file an issue

Configuration

Method A

• Download and install BepInEx.ConfigurationManager
• Hit Configuration Manager's default hotkey F1 to open management window
• Find ModVersionChecker Mod and change preferred fields.

Method B

• Locate com.github.yyuueexxiinngg.plugin.modversionchecker.cfg
• Open with a text editor
• Find and change preferred fields.

Change log

V1.2

• Fix once Set As Latest was used, checker will always use that version as current version even if the plugin

actually got updated and developer set the correct version.

• Now checker window will be closed automatically when game play starts

V1.1

• Add support for setting mod current version as latest in case mod developer forgot to change the version fed into

BepInEx in code upon releasing a new version

Any feedback? Post in GitHub repo

Mod version detector

What version of the Mod did you forget to install?

Don’t know if the Mod has been updated?

This Mod will display all installed plug-in Mod versions and try to get the new version number on

Default left Ctrl + F5 switches the Mod window

Installation method

• Put ModVersionChecker.dll into the plugins folder of BepInEx,

For example: C:\Program Files x86 \Steam\steamapps\common\Dyson Sphere Program\BepInEx\plugins\ModVersionChecker.dll

ModDataList

The Mod list saves the mapping relationship between the GUID of the plug-in in BepInEx and its Full name. If the Mod is not in the list, the detector will not know which version number corresponds to the installed plug-in, so it cannot detect its version update.

The ModDataList used by the detector is in: Github.../ModDataList.xml. The detector will try to get the latest list from here every time the game …