This is a work-in-progress cross-platform custom campaign mod manager for StarCraft II based on the awesome work of the GiantGrantGames community. GiantGrantGames and his community have come up with a custom campaign mod manager that allows modders to use the standard campaign UI for custom campaigns. They have developed and freely released their mod manager, however their mod manager only works on Windows.

This mod manager aims to work on both Mac and Windows as both platforms are officially supported by Blizzard for StarCraft II.

Currently only Mac on Intel processors and Windows 10 and 11 have been tested and verified.

Tested on Mac and Windows. Published for Mac, haven't figured out publishing for Windows. WinForm is used for the published Windows version.

For Windows, the simplest setup is to install Visual Studio 2022 and add Android, iOS, C#, and MAUI to your Visual Studio. Howeer, if you don't want to install Visual Studio, then you can install just the .NET CLI and go from there. For Mac users, you'll want to install install the .NET CLI (Visual Studio 2022 for Mac is still in pre-release).

This project requires .NET 6 to be installed as well as the MAUI workload. To get everything setup, do the following:

• Go to https://dotnet.microsoft.com/en-us/download and install .NET 6
• Run the following command:
  • Windows: dotnet workload install maui (may need to run your powershell/cmd as an Administrator)
  • Mac: sudo dotnet workload install maui
• Once that finishes, run dotnet run --project "SC2 Custom Campaign Manager" to launch the program

To build, run dotnet run --project "SC2 Custom Campaign Manager" -f:net6.0-maccatalyst -c:Debug

To create a pkg file, run dotnet build "SC2 Custom Campaign Manager" -f:net6.0-maccatalyst -c:Debug /p:CreatePackage=true

• Run dotnet publish "SC2 Custom Campaign Manager" -f:net6.0-maccatalyst -c:Debug -o out

To build, run dotnet build "SC2 Custom Campaign Manager" -f:net6.0-windows -c:Release

The WinForm UI has only been tested with Windows. The easiest way to build it is to load the solution in Visual Studio and then run the WinForm project. This is what's published for Windows

I use Visual Studio's publishing feature for this project. Publishing is currently for the "folder publish" type and "folder publish" location. My settings are as follows:

• 64-bit Settings
  • Configuration: Release | Any CPU
  • Target framework: net6.0-windows
  • Deployment mode: Self-contained
  • Target runtime: win-x64
  • Target loxation: bin\Release\net6.0-windows\publish\win-x64\
  • File publish options
    • Produce single file: Checked
    • Enable ReadyToRun compilation: Checked
• 32-bit Settings
  • Configuration: Release | Any CPU
  • Target framework: net6.0-windows
  • Deployment mode: Self-contained
  • Target runtime: win-x86
  • Target loxation: bin\Release\net6.0-windows\publish\win-x86\
  • File publish options
    • Produce single file: Checked
    • Enable ReadyToRun compilation: Checked

All of the core logic, logging, etc is in the Commons library. This means that the UI can easily be changed out as needed per platform. Originally, there were two UIs, but I decided to just move to one UI for now. However, in the future if someone wanted to create another UI on-top, it would be very simple.

The other advantage of this modularity is the UI code is both small and easy to read, so learning how to adapt new UIs should be fairly straightforward.

UI code is responsible for the following:

• Overriding where logging goes and doing any log rotation (if needed)
  • This allows for UIs to choose an "internet connected" log reporting, local logging, no logging, etc
• Defining a "ShowMessage" method which takes a string and (hopefully) shows the user a message in some sort of UI logging
• Initializing an instance of SC2CCM
• Presenting the current UI state to the user (state is read from SC2CCM)
• Setting up UI handlers to forward events to SC2CCM

That's pretty much it. All of the unzipping, detecting installed campaigns, loading configuration, log messages, etc. is handled by the commons module. Manually written UI code should be around 300 lines of code, including class/method boilerplate and comments

• Import and load different campaigns
• Remembers last loaded campaign between sessions
• Allows toggling cutom campaigns
• Displays campaign descriptions

• Drag and drop for imports