Mod auto-sync sender (BETA): push scanned mod list to the bot - #39
Open
Guardian023 wants to merge 1 commit into
Open
Mod auto-sync sender (BETA): push scanned mod list to the bot#39Guardian023 wants to merge 1 commit into
Guardian023 wants to merge 1 commit into
Conversation
Scans the host's installed UMM mods, classifies each via DVMP's ModCompatibilityManager by reflection (no compile-time dependency on dv-multiplayer, matching GRDNConnectBehaviour), and POSTs the list to the bot's /mod-sync endpoint. - Category mapping: All/Undefined/no-info -> required, Client -> optional, Host -> host, Incompatible -> skipped. - URL is the mod's UMM HomePage, passed through only for github/nexus; the bot keeps its curated link otherwise. - Host-only, triggered explicitly from a 'Sync mods to bot (beta)' button in the UMM settings, never automatic. The bot ignores it unless MOD_SYNC_BETA is on, so this is inert until the beta is enabled bot-side. Pairs with grdn-bot #45 (the /mod-sync endpoint) and issue #12.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Connect half of the mod auto-sync (issue #12). Pairs with grdn-bot#45 (the
/mod-syncendpoint).What it does
On demand, the host scans its installed UMM mods, classifies each via DVMP's
ModCompatibilityManager, and POSTs the list to the bot's/mod-sync.GRDNConnectBehaviour's pattern (scan AppDomain for theMultiplayer*assembly, resolveModCompatibilityManager+TryGetCompatibility), so there's still zero compile-time dependency on dv-multiplayer.All/Undefined/no-info → required,Client→ optional,Host→ host,Incompatible→ skipped.HomePage, passed through only forgithub.com/nexusmods.com; the bot keeps its curated link for anything else.UnityWebRequest+x-secret+ActiveBotUrl/ActiveBotSecretpath asStatsTracker/DefectMonitor.Trigger
A "Sync mods to bot (beta)" button in the mod's UMM settings. Host-only, explicit, never automatic. Nothing fires on its own.
Safety / rollback
MOD_SYNC_BETAis on (grdn-bot#45), so this is inert until the beta is deliberately enabled bot-side.This is reflection against DVMP that I can't compile-check outside the game. The reflection targets are taken from DVMP's own
ModCompatibilityManager.csandModInfo.cs, but it may need a compile/runtime pass on the VPS. Feed me any build or log errors and I'll iterate.Test flow
MOD_SYNC_BETAon the bot, deploy, restart.Auto Syncpreset with/viewmods preset:Auto Syncand the game log for[ModSync]lines.