[{"data":1,"prerenderedAt":596},["ShallowReactive",2],{"blog-list-en":3},[4,285,391],{"id":5,"title":6,"author":7,"body":8,"category":271,"date":272,"description":273,"draft":274,"extension":275,"meta":276,"navigation":277,"path":278,"seo":279,"stem":280,"tags":281,"__hash__":284},"blog_en\u002Fblog\u002Frelease-0-1-0.md","SCNexus 0.1.0 released","MengLuoRJ",{"type":9,"value":10,"toc":254},"minimark",[11,15,18,23,26,35,39,42,45,49,52,55,58,61,65,68,71,99,120,123,126,129,133,136,139,143,146,150,153,156,159,163,166,169,172,176,179,183,211,222,226,229,233],[12,13,14],"p",{},"The previous stable release was 0.0.21, published in December 2024. The 0.1 line has since been developed through a series of snapshots, during which the interface, campaign management and custom content management were rewritten. 0.1.0 is the first stable release of that line, and the most substantial change in almost two years.",[12,16,17],{},"Three areas account for most of it: a new interface, a new underlying architecture, and rebuilt campaign and custom content management. Each is described below, followed by the Workshop, weekly mutations, replays and the Assistant.",[19,20,22],"h2",{"id":21},"what-a-stable-release-means","What a stable release means",[12,24,25],{},"During the snapshot period, the layout, the configuration format and the install records were all subject to change, and every upgrade required reading the release notes first. 0.1.0 settles these: subsequent 0.1.x releases will contain fixes and small additions only, without further wholesale rework.",[12,27,28,29,34],{},"For users still on 0.0.21, this upgrade spans roughly two years and changes how the application is operated. Reading the ",[30,31,33],"a",{"href":32},"\u002Fen\u002Fdocs","documentation"," after upgrading is recommended.",[19,36,38],{"id":37},"a-new-interface","A new interface",[12,40,41],{},"A sidebar replaces the previous column layout. Navigation, buttons, dialogs and notices now share a single set of components and colours, and the light or dark theme can follow the system setting.",[12,43,44],{},"Settings, previously spread across several locations, are consolidated into one page: game directory, feature switches, logging and privacy are configured in the same place.",[19,46,48],{"id":47},"a-new-underlying-architecture","A new underlying architecture",[12,50,51],{},"The application structure and the data handling beneath the interface have been rewritten as well.",[12,53,54],{},"The main process is divided into modules by domain — campaigns, custom content, content packages, replays, the Workshop, settings, updates, the Assistant. The renderer communicates with it only through the explicit interfaces exposed by the preload layer: interfaces are declared one by one, per domain, and arbitrary channel invocation is not available. Arguments and call origins are validated at runtime in the main process; type declarations are not treated as validation.",[12,56,57],{},"Content package handling is a single pipeline: scan, classify, parse, plan install targets, detect conflicts, write. Writing is performed as a transaction, so a failure part-way through returns the files already written to their previous state rather than leaving a partially installed directory.",[12,59,60],{},"Configuration and install records use a persistent structure with defaults, validation and version migration, so data from earlier versions is migrated on upgrade.",[19,62,64],{"id":63},"campaign-and-custom-content-management","Campaign and custom content management",[12,66,67],{},"The rework of campaign and custom content management centres on recognition.",[12,69,70],{},"A source no longer has to contain a descriptor. Once an archive or directory is added, the application locates the resources from its Maps \u002F Mods structure and determines the install targets itself: no manifest has to be written in advance, and the result does not depend on how any particular directory level is named. Nested directories are handled in the same way.",[12,72,73,74,78,79,82,83,86,87,90,91,94,95,98],{},"The campaign type is derived from the map paths: maps directly under ",[75,76,77],"code",{},"Maps\u002FCampaign"," correspond to Wings of Liberty, ",[75,80,81],{},"swarm"," (including ",[75,84,85],{},"evolution",") to Heart of the Swarm, ",[75,88,89],{},"void"," and ",[75,92,93],{},"voidprologue"," to Legacy of the Void, and ",[75,96,97],{},"nova"," to Nova Covert Ops. Differences in the casing of resource paths are normalised by the application, so the packager's conventions no longer matter.",[12,100,101,102,105,106,110,111,114,115,119],{},"Where a descriptor is present, it takes precedence: a source containing ",[75,103,104],{},"package.json"," is handled under the ",[30,107,109],{"href":108},"\u002Fen\u002Fdocs\u002Fscnexus-package","SCNexus package standard",", one containing ",[75,112,113],{},"metadata.txt"," under the ",[30,116,118],{"href":117},"\u002Fen\u002Fdocs\u002Fccm-package","CCM package standard",", and a source containing neither goes through automatic recognition.",[12,121,122],{},"Where recognition cannot decide, the application states the reason — several candidate package roots, an ambiguous campaign type, resources outside the standard Maps \u002F Mods hierarchy — instead of reporting a bare failure.",[12,124,125],{},"Results are updated when files change. After a project is renamed or files are added or removed, the directory is rescanned and whatever is already installed is left in place; in earlier versions the same changes marked the install record as invalid.",[12,127,128],{},"The campaign library lists category, install method, content size and disk usage at the same level, without opening a detail page. The source can be chosen before installing, and conflicts are resolved item by item. Before the active content is switched, the application verifies that the current selection is still usable.",[19,130,132],{"id":131},"workshop","Workshop",[12,134,135],{},"The website provides each work's description, version history, and the formats and dependencies it requires, so the decision can be made before installing. Uploading is handled by the creator centre, which maintains several versions, saves drafts and shows review status.",[12,137,138],{},"Each creator has five works by default, with a limit of 300 MB per work. That covers most campaigns but is not a hard ceiling: creators who need more may apply to an administrator, who allocates the quota case by case.",[19,140,142],{"id":141},"weekly-mutations","Weekly mutations",[12,144,145],{},"The CN, US, EU and Asia regions each show this week's mutators and map. Entries can be searched by mutator name or description, and community ratings are shown. Data follows server-side verification, and the client indicates whether an entry has been confirmed; where it has not, a rotation estimate is shown instead.",[19,147,149],{"id":148},"replays","Replays",[12,151,152],{},"Replays are organised by StarCraft profile and by type (melee, campaign, challenge). Imported replays are copied into the corresponding directory rather than merely indexed. The list can be searched by file name, map, player or path, and selected replays can be exported as an archive.",[12,154,155],{},"Match data falls into four states: fully parsed, partially parsed, unsupported by the current version, and corrupt. The first two show players, races and duration, and some builds also provide economy charts. The feature is not intended as a full review tool; it establishes the basic facts of a match without launching the game.",[12,157,158],{},"Note that the replay directory is not watched: after files are added or removed outside the game, use Refresh or Scan directory.",[19,160,162],{"id":161},"assistant","Assistant",[12,164,165],{},"The Assistant provides a controlled local connection for AI clients on the same machine. It can query application state, campaigns, projects and download tasks, and can carry out operations that modify files, such as switching, restoring and uninstalling.",[12,167,168],{},"It is disabled by default. Once enabled, a connection requires an access token, which can be regenerated at any time and invalidates the previous one immediately. Operations that modify files require confirmation each time by default, and automatic approval can be granted per operation. The 500 most recent operations are retained, without recording request contents.",[12,170,171],{},"A token is equivalent to permission to read local data and modify campaign files. Grant it only to clients you trust.",[19,173,175],{"id":174},"macos","macOS",[12,177,178],{},"The macOS build enters the first stage of support: the game installation is detected, and resource directories are recognised even where Maps and Mods differ in case. The package is currently neither signed nor notarised, so the first launch must be allowed in System Settings → Privacy & Security. Some features remain limited, and we do not yet consider it the equal of the Windows build.",[19,180,182],{"id":181},"before-upgrading","Before upgrading",[184,185,186,194,205],"ol",{},[187,188,189,193],"li",{},[190,191,192],"strong",{},"Back up."," Install records and settings are migrated to the new format; the migration normally requires no manual step, but copy the campaign and custom content directories first.",[187,195,196,199,200,204],{},[190,197,198],{},"Download."," The installer is available from ",[30,201,203],{"href":202},"\u002Fen#download","the home page"," and is 64-bit only. Users coming from 0.0.21 should keep the old version installed until the new one has been confirmed to read existing campaigns, then remove it.",[187,206,207,210],{},[190,208,209],{},"Rolling back."," Returning to 0.0.21 requires the backed-up directories: the older version cannot read the new install records.",[12,212,213,214,218,219,221],{},"The complete list of changes is in the ",[30,215,217],{"href":216},"\u002Fen\u002Fchangelog","changelog",", which also records each snapshot. Usage questions are covered in the ",[30,220,33],{"href":32},", including installation, campaigns, custom content, replays and the Assistant.",[19,223,225],{"id":224},"what-comes-next","What comes next",[12,227,228],{},"Three priorities follow 0.1.0: continue the macOS work until it matches Windows; extend replay parsing to further protocol versions so that fewer matches remain partially parsed; and refine the Workshop and creation flow, from upload through review to updates.",[19,230,232],{"id":231},"feedback","Feedback",[12,234,235,236,242,243,248,249,253],{},"The documentation, the legal pages and the common flows were reviewed before this release, but omissions remain possible. Problems can be filed in ",[30,237,241],{"href":238,"rel":239},"https:\u002F\u002Fgithub.com\u002FMengLuoRJ\u002Fscnexus\u002Fissues",[240],"nofollow","GitHub issues",", or reported through the QQ group and ",[30,244,247],{"href":245,"rel":246},"https:\u002F\u002Fdiscord.gg\u002FU6EbQKdkH2",[240],"Discord",". Security issues should not be reported publicly; the process is described on the ",[30,250,252],{"href":251},"\u002Fen\u002Fdocs\u002Fcontributing","Contributing"," page.",{"title":255,"searchDepth":256,"depth":256,"links":257},"",3,[258,260,261,262,263,264,265,266,267,268,269,270],{"id":21,"depth":259,"text":22},2,{"id":37,"depth":259,"text":38},{"id":47,"depth":259,"text":48},{"id":63,"depth":259,"text":64},{"id":131,"depth":259,"text":132},{"id":141,"depth":259,"text":142},{"id":148,"depth":259,"text":149},{"id":161,"depth":259,"text":162},{"id":174,"depth":259,"text":175},{"id":181,"depth":259,"text":182},{"id":224,"depth":259,"text":225},{"id":231,"depth":259,"text":232},"release","2026-11-01","The first stable release. The interface and the underlying architecture are new, campaign and custom content management has been rebuilt around automatic recognition, and the Workshop, weekly mutations, replays and the Assistant ship alongside.",false,"md",{},true,"\u002Fblog\u002Frelease-0-1-0",{"title":6,"description":273},"blog\u002Frelease-0-1-0",[282,283],"Release","Stable","46sXtkxTQNV78xasFI-aa7LqB6eCFJmr6R2D5MwUqDU",{"id":286,"title":287,"author":288,"body":289,"category":380,"date":381,"description":382,"draft":274,"extension":275,"meta":383,"navigation":277,"path":384,"seo":385,"stem":386,"tags":387,"__hash__":390},"blog_en\u002Fblog\u002Fcreator-invitation.md","Workshop Creator Recruitment Begins","SCNexus Team",{"type":9,"value":290,"toc":375},[291,294,297,301,307,322,325,329,332,340,343,347,368],[12,292,293],{},"Thank you for using SCNexus.",[12,295,296],{},"We are about to open project uploads for testing. Until now, Workshop entries consisted mainly of descriptions and version information, and project files had no common home; once the upload channel is in place, the project itself will live in the Workshop as well — when a creator pushes a new version, readers will see it on refresh.",[19,298,300],{"id":299},"what-you-can-do-now","What you can do now",[12,302,303,306],{},[190,304,305],{},"Apply to become a creator."," A first-time creator is initially granted:",[308,309,310,316],"ul",{},[187,311,312,315],{},[190,313,314],{},"5 project slots",";",[187,317,318,321],{},[190,319,320],{},"300 MB"," of publishing space per project.",[12,323,324],{},"These are provisional quotas for the testing period and will be adjusted based on actual usage.",[19,326,328],{"id":327},"how-to-apply","How to apply",[12,330,331],{},"Please fill in the SCNexus Workshop creator invitation questionnaire:",[12,333,334,335],{},"👉 ",[30,336,339],{"href":337,"rel":338},"https:\u002F\u002Fdocs.qq.com\u002Fform\u002Fpage\u002FDRE14RXFRb2R4YmJl",[240],"Creator invitation questionnaire",[12,341,342],{},"We will contact you as soon as possible; once your eligibility is confirmed, you can publish through the Workshop.",[19,344,346],{"id":345},"about-the-testing-period","About the testing period",[308,348,349,352,355],{},[187,350,351],{},"Uploads are still in testing, so quotas, limits and workflows may change; please refer to the notices shown on the page;",[187,353,354],{},"If an upload is interrupted, stalls, or fails validation, tell us the project name and the approximate time so we can investigate;",[187,356,357,358,362,363,367],{},"If you already have a creator invitation code, redeem it in the ",[30,359,361],{"href":360},"\u002Fen\u002Fcreator","creator console",". If you do not have an account yet, ",[30,364,366],{"href":365},"\u002Fen\u002Flogin","sign in or register"," first.",[12,369,370,371,374],{},"To see what is in the Workshop right now, start from the ",[30,372,132],{"href":373},"\u002Fen\u002Fworkshop",".",{"title":255,"searchDepth":256,"depth":256,"links":376},[377,378,379],{"id":299,"depth":259,"text":300},{"id":327,"depth":259,"text":328},{"id":345,"depth":259,"text":346},"announcement","2026-10-31","Project uploads are entering testing. You can now apply to become a creator — five project slots to start, and 300 MB of publishing space per project.",{},"\u002Fblog\u002Fcreator-invitation",{"title":287,"description":382},"blog\u002Fcreator-invitation",[132,388,389],"Creators","Recruitment","j0fQOW4AXBWlfbeZ-wcQfKeAGovuT7NUt4Ra_Kt5_Tc",{"id":392,"title":393,"author":7,"body":394,"category":380,"date":381,"description":588,"draft":274,"extension":275,"meta":589,"navigation":277,"path":590,"seo":591,"stem":592,"tags":593,"__hash__":595},"blog_en\u002Fblog\u002Fnew-website.md","A Renewed SCNexus Website",{"type":9,"value":395,"toc":579},[396,403,406,409,413,416,453,456,460,463,483,486,490,500,503,507,510,513,517,541,543,546,560,562,574],[12,397,398,399,402],{},"If you have visited this domain before, what you saw was a documentation site: a column of entries on the left, installation steps and format references in the middle, a sponsorship link in the footer. That was ",[75,400,401],{},"scnexus-docs",", built on VitePress in 2023, and its job was to host documentation.",[12,404,405],{},"Over three years it took on more and more content, yet its structure remained that of a documentation site: the changelog was stacked into a single page in sequential order, and identifying what changed in a given version depended on your browser's find function; the download button pointed at GitHub Releases, with only a single link on the site itself; and what the application actually is never had a page that answered the question directly.",[12,407,408],{},"So this is a rebuild, not a change of appearance.",[19,410,412],{"id":411},"what-the-new-site-contains","What the new site contains",[12,414,415],{},"The site is divided into the following sections, all reachable from the top navigation:",[308,417,418,424,430,436,442,447],{},[187,419,420,423],{},[190,421,422],{},"Home"," — product overview, core capabilities, a preview of the client interface, community links, and a download button pointing at the latest version.",[187,425,426,429],{},[190,427,428],{},"Changelog"," — one record per version.",[187,431,432,435],{},[190,433,434],{},"Blog"," — announcements, releases, technical notes, community and guides, filterable by category. This post is an announcement.",[187,437,438,441],{},[190,439,440],{},"Documentation"," — the primary entry point for installation and usage.",[187,443,444,446],{},[190,445,132],{}," — browse projects on the web.",[187,448,449,452],{},[190,450,451],{},"Account"," — account-related settings.",[12,454,455],{},"Sponsorship, the privacy policy and the terms of service are all still here, and easier to find than before. The status page remains a separate site; the navigation keeps a link to it.",[19,457,459],{"id":458},"the-changelog-can-now-be-browsed-by-version","The changelog can now be browsed by version",[12,461,462],{},"Previously every version was collected in one long article, and the further back you went, the harder it was to search. Now each version has its own record, with the body divided into three fixed groups:",[308,464,465,471,477],{},[187,466,467,470],{},[190,468,469],{},"Updates",": what was added or changed;",[187,472,473,476],{},[190,474,475],{},"Fixes",": what was repaired;",[187,478,479,482],{},[190,480,481],{},"Notes",": known issues and things to check before upgrading.",[12,484,485],{},"The top of the page lets you switch between stable and snapshot releases. To confirm what changed in the first 0.1.0 snapshot, open that version — no scrolling required.",[19,487,489],{"id":488},"the-documentation-has-not-moved-only-the-way-it-reads","The documentation has not moved, only the way it reads",[12,491,492,493,499],{},"One point worth stating: the documentation content ",[190,494,495,496,498],{},"is still maintained in the ",[75,497,401],{}," repository",". Nothing was copied into the new site. Content is synchronized when the site is published, so a single edit keeps both sides consistent.",[12,501,502],{},"What changed is the layout: the left column groups pages under \"Getting Started \u002F Guides \u002F Reference\", the right column shows the table of contents for the current page, and the footer links to the previous and next pages. Finding the definition of a field used to require guessing which page it belonged to; browsing by group now gets you close enough to locate it.",[19,504,506],{"id":505},"the-workshop-is-now-accessible-on-the-web","The Workshop is now accessible on the web",[12,508,509],{},"Previously the only way to see what the Workshop contained was to open the client. You can now browse project descriptions, version history, supported formats and dependencies on the web, and decide whether to install.",[12,511,512],{},"This section requires signing in on the web. The client is unaffected.",[19,514,516],{"id":515},"other-changes","Other changes",[308,518,519,529,535],{},[187,520,521,524,525,528],{},[190,522,523],{},"Chinese and English",": Chinese is the default language; English lives under ",[75,526,527],{},"\u002Fen",". Translations are still being filled in, and pages without one are marked explicitly rather than presenting Chinese text as English.",[187,530,531,534],{},[190,532,533],{},"Light and dark",": follows the system setting, and can also be switched manually.",[187,536,537,540],{},[190,538,539],{},"Mobile layout",": the old documentation site required constant zooming on a phone; navigation, body text and tables are now reflowed for small screens.",[19,542,225],{"id":224},[12,544,545],{},"The site itself is only the front door; the content behind it still needs work:",[184,547,548,554,557],{},[187,549,550,551,553],{},"Fill in English content for documentation and the blog, so that ",[75,552,527],{}," is no longer predominantly Chinese;",[187,555,556],{},"Connect project uploads for the Workshop, so project files can live on the site rather than only descriptions and version records;",[187,558,559],{},"Support subscriptions to the changelog and blog, so there is no need to revisit the site to check.",[19,561,232],{"id":231},[12,563,564,565,570,571,374],{},"The site has just been rebuilt and will inevitably have gaps. If you find a broken link, a layout problem or outdated content, please open an issue on ",[30,566,569],{"href":567,"rel":568},"https:\u002F\u002Fgithub.com\u002FMengLuoRJ\u002Fscnexus",[240],"GitHub",", or let us know in the QQ group or on ",[30,572,247],{"href":245,"rel":573},[240],[12,575,576,577,374],{},"The old site is no longer updated; documentation is now reached through ",[30,578,440],{"href":32},{"title":255,"searchDepth":256,"depth":256,"links":580},[581,582,583,584,585,586,587],{"id":411,"depth":259,"text":412},{"id":458,"depth":259,"text":459},{"id":488,"depth":259,"text":489},{"id":505,"depth":259,"text":506},{"id":515,"depth":259,"text":516},{"id":224,"depth":259,"text":225},{"id":231,"depth":259,"text":232},"The documentation site that served us for three years has been retired. The new site brings the product overview, documentation, changelog, blog and Workshop together in one place.",{},"\u002Fblog\u002Fnew-website",{"title":393,"description":588},"blog\u002Fnew-website",[594,33],"website","8fYBliND1_xM_KrDBOjOdtpkKBC1VWlG3YSQw0GZWq8",1793550744122]