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版本檢測器

忘記安裝的Mod是什麼版本的?

不知道Mod有更新了?

本Mod會顯示所有安裝的插件Mod版本並嘗試在上獲取新版本號

默認左 Ctrl + F5開關Mod窗口

安裝方法

• 將 ModVersionChecker.dll 放入BepInEx的 plugins文件夾,

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

ModDataList

Mod列表保存BepInEx中插件的GUID與其在上Full name的映射關係, 如果Mod不在列表中檢測器就不知道哪個版本號與安裝的插件對應導致無法檢測其版本更新

檢測器用到的ModDataList在: Github.../ModDataList.xml 每次啓動遊戲時檢測器時都會嘗試從這裏獲取最新的列表

如何向列表中添加Mod項目

推薦做法:

• 在本插件的GitHub項目

中對ModDataList.xml

新建PR

• 或者在GitHub中新建Issue請求添加
• 如果PR被合併, 將會在檢測器下一次啓動獲取新列表時生效

本地添加:

• 將Mod信息添加至本地存儲的XML文件, 路徑爲遊戲根目錄\BepInEx\data\ModVersionChecker\PreservedModData.xml
• 這裏保存的列表項目會覆蓋從網上獲取的項目

常見問題

• 最新版本中顯示 未支持
• 檢測器正在獲取Mod列表中, 或此Mod並未在列表中列出,

所有支持檢測更新的Mod在這裏列出: Github.../ModDataList.xml

-