Docs
Documentation
From installation to advanced usage, everything you need to know about SCNexus.
SCNexus Docs
Install, campaigns, works and settings
Guides
Campaign management
Import your own campaigns into the library, activate them in the game, and restore the official campaigns at any time
Custom content
Install maps and mods straight into the game, then pick a launcher map and start in one click
Weekly mutations
This week's mutation map, mutators and community rating, plus the full mutator reference
Replays
Index replays by StarCraft profile and replay type, with duplicate detection, bulk export and match data
Workshop
Browse community works, open their details and download reviewed releases
Creator center and uploads
Create works, maintain their details, upload new versions and track upload tasks
Downloads
Fetch content from GitHub or the Workshop, then install it once you have checked it
Creation tools
Local helpers such as the encoding converter; input is never uploaded or stored
Smart Assistant
A controlled MCP service connecting local data to AI clients on the same machine
Account and personal center
Signing in, your profile and level progression, and setting up and maintaining two-step verification
Settings
Language, game directories, feature switches and logging privacy, tab by tab
Contributing
Contributing
How to contribute to SCNexus: where the repositories live, how to set up a development environment, what to run before submitting, the code and documentation conventions, the code of conduct, and how to report security issues.
Translating the interface
Where the interface translation files live, how keys are named, how to submit changes, how to verify them locally, and what adding a language touches.
Editor Docs
Galaxy Editor and creation tools
Getting started
Reference
Package formats and install sources
Overview
The packaging and source conventions that importing, installing and distributing content depends on.
SCNexus package standard
Directory layout, package.json manifest fields, map and mod resource declarations, and how launchers and bundled documents are written for SCNexus work packages.
CCM package standard
How CCM describes a campaign in metadata.txt, the key-value format, the directory layout and install targets, and how SCNexus reads these packages.
GitHub source standard
The manifest and structural requirements a public GitHub repository has to meet to serve as an install source, and how addresses and branches are written.
