Mod Packager - Optional deploy to workshop/dedicated server mods directory for fast multiplayer testing.

[wildeelli]

Long story short, integrate Digi's Fast Solo DS Testing script in to the MDK2 Mod Packager as an optional... option.

How I see it functioning as a user:

• two parameters in the local.ini:
  • the workshop ModId
  • a solution configuration name
• when the specified solution configuration is built, the project (mod) would additionally be deployed to the steam workshop mods folder and dedicated server mods folder, overwriting the workshop downloaded version of the mod with the in-development version.

Build events in VS22 at least are not necessarily viable for this since the multiplayer testing deployment isn't something always needed to be done during development.

[THDigi]

The whole premise of replacing local mod files is a hack, so it needs very careful consideration about side effects of automating it.

Right now one having to run a .bat script manually is plenty reminder of what you are doing, and giving it full paths is making you aware of what's being done, as well as seeing the remove directory command and all that...
But if it becomes a hidden part of the build which you then forget, and worse, if you set it up to override the live version, then it's gonna cause so many confusing problems 😅

I'm all for easier MP testing but it should be safe, maybe a reminder every time you do it that it copied to DS, as well as a recomandation in the ini to use a dedicated hidden mod for this... also should probably input paths instead of only the workshop id, as torch I believe downloads mods in its own folder.
And I have a feeling I'm forgetting another important pitfall 👀