Skip to content

Releases

1.1.0-rc.3 — Private Editor history and resilient HTTP responses

Choose a tag to compare

@VoVanRusLvSC2 VoVanRusLvSC2 released this 07 Nov 10:38

Fixes for HTTP disconnect handling and hidden Editor history isolation. API contract 1, native protocol 16 and the existing 31 MCP tools are unchanged.

  • Handle connection aborts/resets during JSON headers, response bodies and artifact downloads. Do not send a second response to a closed client or replay native work. Other I/O errors remain visible.
  • Redirect only the owned Editor's Recent Files registry subtree, including remembered open documents, to a private volatile instance key before startup. Remove that private key after the exact owned process exits. Existing normal history is preserved; this is not full user-profile virtualization.
  • Retain startup failure phase, Win32 code, remote result, bootstrap code and bounded log tails in private startup-failure evidence. Include this evidence in document-validation failures even after worker reset.
  • Allow a continuous 15-second dispatch-marker grace interval instead of rejecting a newly created document window immediately.

Validation: 131 Python tests and ten native test executables passed. Two real hidden workers each opened, saved and generated/compiled a private map with zero compiler errors. Native history writes were observed in their private keys; normal history and source bytes remained unchanged. Both owned workers and private keys were removed. Observation recorded zero visible owned windows, foreground samples and input-desktop changes. A deliberately missing startup DLL retained phase load-local-bootstrap / Win32 126 and its suspended owned child exited. Frozen HTTP and MCP checks passed; packaged source/native hashes were verified.

The separate intermittent startup complaint still needs its original machine's logs; these local checks do not identify its cause. Terrain appearance was not changed, and no new Terrain-quality or full Data-audit acceptance is claimed.

Replace the complete toolkit package and restart its owned worker to apply this update. Existing running workers and separately pinned MCP integrations are not automatically upgraded. Stable 1.0.0 remains available.

See docs/COMPLAINT_FIXES.md for details, reproduction commands and limits.

1.1.0-rc.2 — Hidden Editor cursor isolation

Choose a tag to compare

@VoVanRusLvSC2 VoVanRusLvSC2 released this 28 Oct 12:31

Hidden Editor cursor isolation fix for 1.1.0-rc.1. API contract 1, native protocol 16 and the existing 31 MCP tool names are unchanged.

  • Wrapped D3D9 and D3D9Ex devices discard cursor positioning, cursor bitmap and show/hide commands. The invisible render thread no longer forwards them to the driver on the input desktop.
  • The startup DLL refuses initialization outside the selected original Editor on its private desktop before installing patches or creating the rendering thread.
  • No game process is attached to or modified. GUI hooks remain scoped to owned Editor threads, with no physical input injection or desktop switching.

Validation: 122 Python tests, eight native test executables, real-DLL rejection in an unrelated test process, and hidden original-Editor startup plus two nonblack Terrain captures on a private map. The source map remained unchanged; observation recorded zero visible owned windows, foreground samples or input-desktop changes. Read-only inspection found no toolkit DLL in the same running SC2 game before and after the test. Gameplay input itself was not driven or recorded. The test worker closed.

The frozen HTTP and windowed MCP package checks passed (31 tools), and the packaged source/native hashes match the committed build. The rc.1 field/resource and camera acceptance baseline remains documented separately; a full Data audit was not repeated for this cursor fix. This is a prerelease; stable 1.0.0 remains available.

Replace the complete package and restart its owned worker to apply the change. Already running workers keep their existing DLLs. Do not hot-replace loaded DLLs or stop another session's Editor. See docs/INPUT_ISOLATION.md for details.

1.1.0-rc.1: native Terrain camera and Data field values

Choose a tag to compare

@VoVanRusLvSC2 VoVanRusLvSC2 released this 27 Oct 19:23

Terrain camera control and original effective field values

This candidate adds explicit native Terrain camera framing and persistent
field-value snapshots to SC2 Editor Toolkit. It uses the original installed
Editor; it does not implement a replacement Data model or renderer.

  • Set target XYZ, pitch/yaw/roll, distance and FOV through the original Camera
    Editor. Commit the view, read it back in a fresh dialog and export a renderer
    PNG. Saved cameras and complete overhead map export remain supported.
  • Record every materialized effective field in all 109 native catalogs, including
    loaded dependencies, nested members and array elements. Keep original type
    serialization, per-value failures and verified numeric/color/vector bits.
  • Query and compare values using the existing audit tools with section:fields,
    optional exact catalog/object/field filters and bounded pagination. These
    operations work after the Editor closes. Older reports without field values
    and incompatible value encodings are rejected explicitly.
  • Centralize package/native version metadata and preserve the existing 31 MCP
    tool names and API contract 1. Native IPC is now 16.

Validation

The final reader traversed Nydus and its loaded dependencies: 50,129 objects,
6,906,851 field values, zero getter/serialization errors
. Exact storage was
recorded for 2,578,832 values. Private native maps confirmed LifeMax 45 → 73
as the only changed Marine field, matching the original Data UI. The frozen MCP
queried the complete native value index and its self-comparison without launching
an Editor. Explicit camera views produced distinct, visually reviewed PNGs;
complete overhead export also passed.

The frozen HTTP package passed original Nydus compilation and exact Galaxy
download, then captured a private terrain map with explicit camera parameters.
122 Python tests, seven native suites and frozen HTTP/MCP contract checks passed.
See 1.1 acceptance for evidence scope and intermediate
attempts that are not counted as passes. Source archives remained unchanged;
counted native observations recorded no owned user-desktop visibility/foreground
events, physical input injection or desktop-switch API use. Owned Editors closed.

Upgrade and limits

Replace the complete ZIP package and restart the API/MCP worker. Full value
audits require at least 12 GiB free on the selected --work volume; storage
is checked before native work and during indexing/copy publication. This is a
prerelease; stable 1.0 remains available. Source code is included in the Git tag.
Installations are discovered/configurable; the verified native adapter currently
supports original Editor 5.0.17.98310 x64.

Fields describe the saved effective default variant. Runtime upgrades/player
state, actor-event semantics, computed links, nested resource binary integrity
and movement/attack/ability/death behavior require separate checks. File-presence
validation retains its separately documented 1.0 evidence; this candidate does
not claim a new successful full file audit from its stopped development repeat.
Region capture remains an experimental crop of full-map pixels. Explicit cameras
use native viewport resolution; arbitrary output resolution is not exposed.

SC2 Editor Toolkit 1.0.0

Choose a tag to compare

@VoVanRusLvSC2 VoVanRusLvSC2 released this 24 Oct 16:39

SC2 Editor Toolkit 1.0.0

Stable MCP/HTTP automation for the original StarCraft II Editor, scoped to the
verified original 5.0.17.98310 x64 binary on an interactive Windows x64 session.
Portable installation discovery and explicit selection are supported. The
toolkit owns hidden private Editor instances; it does not attach to a user's
visible Editor, inject physical mouse/keyboard input or switch desktops.

New for 1.0

  • Separate validated input schemas for all 31 MCP tools and the corresponding
    HTTP operations, result envelopes, tool annotations and structured error codes
    with actionable next steps. Long operations use the existing persisted FIFO
    job queue, progress, cancellation, deadlines and fresh-worker recovery.
  • Immutable indexed audit queries by report ID, with exact object/catalog and
    finding filters, pagination, bounded inline results and full exact artifacts.
  • Incoming original typed Data references: find which recorded objects use a
    target catalog/object and return their native field paths.
  • Audit comparison: added/removed findings and added/removed/modified recorded
    object observations, with project/adapter identities and bounded pages.
  • Project revision manifests: pre/post hashes of recursively declared local
    dependencies plus the installed CASC build manifest, matched to observed
    native Data source names. Unresolved/cache/physical-path guarantees remain
    explicit instead of being silently treated as verified.
  • Original header-only DocumentInfo dependency metadata is recognized as empty;
    unclosed or otherwise malformed XML remains incomplete. This fixes a false
    incomplete project manifest on the tested Nydus dependencies.
  • Read-only installation preflight through sc2_doctor, POST /doctor or the
    windowed API executable's doctor command. Checks original Editor identity,
    embedded native component version/protocol/hashes, renderer package, writable
    storage, desktop and optional FFmpeg/ffprobe. GPU readiness requires a live test.
  • Bounded native resource batches with progress and temporary private-tree
    redraw/scroll settings restored after traversal. Renderer warmup before
    original audio recording retains strict audio/timeline confirmation.
  • English setup/contracts/acceptance documentation and a reproducible allowlisted
    release packager that checks frozen toolkit code against committed source.

Existing original Editor operations

Native Triggers XML to Galaxy generation and original compilation, exact Galaxy
export, separate Messages/Console diagnostics, private native save/close/reopen
and component comparison, saved object search, original full-map rendering with
independent unit/doodad filters, saved map cameras, cutscene PNG and H.264/AAC MP4.
Independent servers use separate work directories, tokens and owned Editors.

Acceptance and limits

See docs/V1_ACCEPTANCE.md for the final-package measurements and private Nydus
checks, and docs/MCP_CONTRACT.md for installation and supported guarantees.
No private maps, logs, captures, machine paths or tokens are included in the ZIP.

This release does not claim exhaustive runtime Data correctness. Opaque actor
strings, computed/trigger references, resource binary integrity and transitive
binary dependencies remain outside typed reference/file presence checks. Object
audit comparison is not a complete scalar effective-value diff. Coordinate-region
cropping remains experimental. Game simulation and trigger cinematic playback
are outside the Editor toolkit's stable scope.

Upgrade the complete package and restart its server. Native protocol remains 15;
API/MCP contract is version 1. Unexpected arguments are now rejected, so clients
should use each advertised tool schema. Prior releases remain available.

Original project author and owner: VoVanRusLvSC2. Uses the existing SC2 Native
Toolkit Attribution License 1.0; preserve the required author/repository credit.

SC2 Editor Toolkit v0.14.0-rc.1 - Full native Data audit

Choose a tag to compare

@VoVanRusLvSC2 VoVanRusLvSC2 released this 24 Oct 11:21

SC2 Editor Toolkit v0.14.0-rc.1

Full traversal of the original Editor's effective Data model is now available
through POST /data/audit, queued audit_data jobs and MCP sc2_audit_data.

  • Visit all 109 native catalogs in the map/mod and loaded dependencies, with inherited fields, arrays and nested structures.
  • Check typed catalog targets and file paths through the original merged Archive Browser.
  • Return per-catalog coverage, strict presence findings, original diagnostics, revision hashes and complete downloadable JSONL/JSON reports.
  • Keep opaque types, unresolved tokens and optional references explicit; missing optional targets alone do not assert a broken map.
  • Correct Console capture to read output control 15 and exclude input control 13. Messages retains output control 13.
  • Preserve owned-worker FIFO, progress, cancellation/deadlines and hidden operation without physical input.
  • Support separate absolute packaging/build output directories.

Validated on Nydus and real dependencies: 50,129 objects, 7,367,409 field visits,
103,197 typed references and 26,041 unique file paths; zero getter failures and
zero confirmed new Editor errors. Native visibility/foreground/input-desktop
changes remained zero. A packaged full negative-map cycle found intentional
missing references/files, confirmed inherited/existing targets, read the real
Console output and verified authenticated artifact downloads by SHA-256.
97 Python tests, six native suites, packaged HTTP and 27-tool MCP tests passed.

Presence findings and coverage gaps remain in the reports; this release does
not certify gameplay semantics, binary resource integrity or runtime-computed
references. Dependency file revisions are not independently hashed.

Upgrade the complete native protocol-15 bundle and restart owned workers.
Editor build support remains the verified original 5.0.17.98310 x64. Existing
release assets are unchanged. Installation/API/MCP/build instructions and
validation documentation are in English. Source is included in the tagged
repository; the toolkit requires your own installed StarCraft II Editor.

SC2 Editor Toolkit v0.13.0-rc.1

Pre-release

Choose a tag to compare

@VoVanRusLvSC2 VoVanRusLvSC2 released this 23 Oct 22:40

SC2 Editor Toolkit v0.13.0-rc.1 adds background jobs, revision-bound original-Editor reports and native Data access. The existing map/cutscene/trigger routes and unit/doodad filter arguments remain available.

Added

  • Bounded per-server FIFO jobs with status/progress, cancellation, execution deadlines, persisted history and fresh-worker recovery. Interrupted jobs are never automatically replayed. Separate servers retain independent owned Editors.
  • A downloadable map/mod report combining original loading/Data diagnostics, optional native save → close → disk reopen/component comparison, original Galaxy generation, native compilation and exact Galaxy export. Reports carry source SHA-256/map revision; unreadable logs stay unknown.
  • Effective Data fields from the original Editor's complete Copy As Text serialization, captured in a process-private clipboard. Exact raw catalog/ID and original XML corroborate selection; clipped UI cells are not reported as complete fields.
  • Native Object Explorer associations with catalog-qualified related IDs and pagination. Edge direction, transitivity and exhaustive usage coverage are not inferred.
  • Main Model file availability through the original merged Archive Browser. Confirmed absence is a separate resource error; a nonblack placeholder frame is never used as proof of file presence.
  • Eight additional MCP tools (26 total) and English guides for jobs/reports and Data/resources.

Reliability

  • Owned requests use queued GUI-thread dispatch without a cross-process synchronous send context. IPC mapping and atom stay alive until completion or exact owned-process exit.
  • Work-directory locking prevents concurrent servers from replacing one another's state/token. Packaged startup failures produce private JSON diagnostics without a desktop error dialog.
  • Queue admission/finish persistence failures are handled explicitly, including disk-full conditions.
  • Private Win32/OLE clipboard isolation includes immutable text snapshots and complete format/empty-clipboard handling; it does not forward operations to the user's clipboard.

Validation

  • 88 Python tests and five native C++ regression suites passed.
  • Both packaged HTTP and windowed MCP stdio executables passed; 26 tools discovered.
  • The frozen executable passed FIFO/cancellation, native report/save/reopen/compiler/export, inherited and overridden Marine fields, native Explorer links, Ability/Effect/Sound catalogs, malformed Data, missing dependency, localized save/reopen and deadline/fresh-worker recovery.
  • A private Nydus mod copy passed native generation, load/Data diagnostics and compilation with zero compiler errors, preserving the supplied source.
  • Positive Marine and intentionally absent main Model file checks passed through the original Archive Browser.
  • Native whole-map regression passed all four unit/doodad filter combinations and restoration, six geometry comparisons against an independent placement-free reference, exact native TGA/PNG pixels and downloads, search filters, Galaxy export and readable Editor diagnostics. The 512×384 output and region crop were visually reviewed.
  • Independent hidden workers ran concurrently; no physical input or desktop-switch calls were used. Sources/installed Editor were preserved and owned test workers closed.
  • A separate two-worker XML test passed five original conversions/compilations with zero errors, isolated tokens/artifacts and survivor compilation after closing the other worker. Its explicit --allow-screensaver observer run stayed on the system screensaver (418 samples, zero owned foreground/visible windows); both pre-existing Editors remained alive.
  • Both EXEs contain the exact tested five native binaries and pinned DXVK renderer. User maps, mods, logs, tokens and captures are excluded from the release.

Scope and upgrade

This is a prerelease for the verified original Editor 5.0.17.98310 x64 and tested English Data UI. Replace the complete bundle and restart owned workers: native protocol 14 requires matching components. Do not attach it to a normal Editor.

Resource validation currently checks the selected Model's main file presence with readable operation diagnostics. It does not certify binary integrity, nested textures/animations/sounds, other resource catalogs or gameplay. Water rendering, arbitrary terrain-camera overrides, Galaxy-trigger cinematic playback and every Editor/GPU/dependency combination are not certified. Earlier parallel-instance, portable-selection and media evidence is separately dated in docs/VALIDATION.md.

The ZIP includes source-commit/build metadata, SHA-256 checksums, English documentation and third-party notices. Source code is published in this repository under the attribution license; the previous stable release remains unchanged.

v0.12.0-rc.1 - Native whole-map export and object filters

Choose a tag to compare

@VoVanRusLvSC2 VoVanRusLvSC2 released this 23 Oct 19:16

Native whole-map export and independent object filters

Unit and doodad exclusion now updates the original Editor's flag model and verifies native readback before publishing a PNG. The adapter resolves stable native IDs through the exact tree item, rather than checkbox state, row order or Win32 item metadata. The image retains the original CMapImageGenerator pixels.

Validated with the packaged program on original Editor 5.0.17.98310 x64 and the tested RTX 2070 / DXVK 3.1.1 setup:

  • All four unit/doodad combinations and restoration in one persistent map; independent filters in two simultaneous owned Editors.
  • Native exports from 512x384 through 4096x3072, including full-resolution placed models; exact TGA/PNG pixels and artifact downloads.
  • Six geometry regions compared against a separately rendered private copy with placements removed. Known broken old exclusion output correctly fails the same acceptance check.
  • Saved object query/kind/owner/bounds/pagination, output preservation and invalid-argument checks.
  • Original generation/compilation: 0 compiler errors; exact Galaxy export; actual Editor log readable, complete and clear.
  • 66 Python tests, 4 native C++ suites, packaged HTTP/MCP checks; 18 existing MCP tools, no new tools added.
  • 22,715 recorded per-worker observations: no owned foreground samples, visible windows, input injection or desktop switching. Both owned test Editors closed; source and installed-EXE hashes unchanged.

Editor paths remain automatically discovered or explicitly selectable; there is no machine-specific installation path. Native protocol 13 requires the complete matching package and restarting owned workers. First native map/module loads can take minutes; reuse the loaded map for subsequent requests.

English map export instructions, presentation guide and dated validation describe the tested scope. A dedicated water case, broad map/dependency/device coverage and general coordinate-region calibration are not certified. Earlier cutscene/audio and portable-selection evidence retains its own version/date scope.

Source code is published on main and in this tag. The ZIP includes build/source commit metadata, file hashes and licenses; it contains no user maps, captures, tokens or raw logs. Attribution remains required under the project's existing license.

v0.11.0-rc.1 — Portable Editor selection and concurrent-worker validation

Choose a tag to compare

@VoVanRusLvSC2 VoVanRusLvSC2 released this 23 Oct 17:23

Editor installations no longer need a fixed drive or machine-specific path. This prerelease adds portable discovery/selection and a fresh, reproducible simultaneous-worker acceptance test for presentation.

Changes

  • Select the original Editor through startup editor_path, server CLI --editor, SC2_EDITOR_PATH, or Windows registry/Program Files environment/PATH discovery. Accept an EXE or installation/Support64 directory, including spaces and Unicode. Multiple installations require an explicit choice; invalid explicit selections never fall back silently.
  • Verify the supported original executable's SHA-256 before launch. Host/controllers/capture validate the selected file instead of comparing with a compiled-in installation path. The early owned GUI callback binds by file identity after prelaunch verification and records private startup diagnostics.
  • Native protocol 12 rejects old dispatch markers. Upgrade the complete matching package and restart owned services. No new MCP tools: 18 existing tools gain the shared startup selection argument.
  • Add English presentation/readiness guidance, concurrent-worker tests, missing/unsupported-install tests, native file-identity tests and CI coverage.

Live acceptance

  • Two packaged hidden original Editors run concurrently, selecting an installation through CLI for A and an API request for B. Six original XML → Galaxy → Compile All/export operations passed with zero native compiler errors and exact script downloads.
  • Different markers, PIDs and instance GUIDs stay isolated. Cross-server tokens return 403, foreign artifacts return 404. Closing A leaves B able to generate, compile and export again.
  • Saved-camera Terrain rendering while B compiles, an actual Nydus-derived cutscene frame, and a short H.264/AAC MP4 with a required audible native cue passed. Video/audio fully decoded and downloads matched. Captures are original backbuffer pixels, not desktop screenshots.
  • 2,002 external observations, including 1,912 with both owned Editors alive: zero visible hidden windows, hidden foreground samples or input-desktop changes. No mouse/keyboard injection or desktop-switch API used. All test-owned Editors closed; two pre-existing Editors were left running and uncontrolled. Source archives and installed Editor hashes stayed unchanged.
  • Direct native host/GUI-thread attachment/controller also passed an installation alias with spaces and Unicode. This tests path handling; it is not a physical asset-relocation or separate Battle.net-profile test.
  • 65 Python tests, 4 native C++ suites, packaged HTTP/MCP tests and exact embedded native/renderer hash checks passed.

The exact published v0.10.0-rc.1 baseline was separately rechecked the same day: Nydus v54 generated/compiled/exported 342,851-byte Galaxy with zero errors; four scene frames and original/native-cue video, PCM/AAC timing, range/camera changes, repeat export and audio cancellation passed. These are separately dated baseline results in the validation history.

Presentation scope

The core is ready to demonstrate as a developer prerelease, with the supported original 5.0.17.98310 x64 binary. Path portability does not automatically support every Editor build or locale. Vulkan drivers, installed map dependencies and an interactive Windows session remain required; FFmpeg/ffprobe/audio endpoint are additional media prerequisites.

One API/MCP server owns one Editor. Use distinct work directories and ports for parallel servers. General Editor preferences may still share the Windows profile. Do not concurrently overwrite one source archive. First native resource loading can take minutes; offline export can take longer than clip duration. Whole-map category exclusion, water/region calibration, trigger-driven cinematic playback and general queued/cancellable native jobs remain outside accepted scope.

See presentation readiness, parallel setup and validation. The ZIP includes matching English documents, BUILD.json, licenses and SHA256SUMS. Existing releases are unchanged.

Source commit: 4455d708bacbfd0803362c0d3d01c0c99000a97f.

ZIP SHA-256: 73d480de3ba5a6c0ecebd26c8a50303ec1fbb99a27f41d9f39c4032b3dcd2e10.

v0.10.0-rc.1 — Parallel normal and hidden Editor with Vulkan

Choose a tag to compare

@VoVanRusLvSC2 VoVanRusLvSC2 released this 21 Oct 13:51

An existing normal StarCraft II Editor can stay open while the toolkit runs a separate original Editor in the background. The owned hidden process uses pinned DXVK 3.1.1/Vulkan offscreen rendering, adapted from SC2GameToolkit, to avoid the system-D3D9 startup failure observed with parallel SC2 instances.

Changes

  • render_backend: "auto" | "legacy" | "vulkan" on worker startup. This renderer-enabled package defaults to Vulkan through auto; backend changes require restarting the owned worker.
  • Private instance GUID suffixes for the existing singleton allowlist, plus separate renderer configuration, caches and logs.
  • Original native XML → Galaxy generation, compilation, diagnostics, rendering and owned GUI-thread dispatch remain in use. No new MCP tools.
  • Reproducible parallel-instance documentation, opt-in coexistence/restart test, pinned dependency fetcher, CI build support, SHA-256 checks and complete DXVK license notice.

Live validation — Editor 5.0.17.98310, RTX 2070 / NVIDIA 595.79.0

  • Opened normal Editor first, then exercised two consecutive packaged hidden-worker lifetimes with different process/instance identities. The normal process/document/window remained responsive and unchanged, without a toolkit bridge DLL; it was left open.
  • Four original XML → Galaxy → Compile All conversions: zero native compiler errors, exact Galaxy artifact/download hashes.
  • Read native Messages/Console in both hidden lifetimes; verified private native save → close → disk reopen and component comparison.
  • Visually reviewed real Terrain PNG with relief, Command Center, Marines and doodad, and NydusIntroBlue PNG at Front Formation Camera / 1980 ms with blue Marines and platform. No desktop screenshot or replacement renderer scene was used.
  • Across 1,659 external coexistence observations: zero visible hidden windows, hidden foreground samples or input-desktop changes. No mouse/keyboard injection or desktop-switch API used. Both owned hidden Editors closed; source assets and installed Editor hashes unchanged.
  • New server rejected the previous token (403) and artifact (404), then compiled successfully again.
  • 57 Python tests, 3 native C++ suites, packaged HTTP/MCP checks (18 tools), embedded binary/dependency hash checks and source native negative/recovery checks passed.

Usage and limits

Keep your normal Editor open. Start the new SC2NativeAPI.exe or SC2NativeMCP.exe; no DLL installation into the SC2 directory is needed. Upgrade the whole matching package and restart the owned service. Vulkan-compatible hardware/drivers are required; legacy explicitly selects system D3D9.

One API/MCP server owns one hidden worker. This is hardware-specific acceptance, not a universal multi-instance guarantee. General Editor preferences may still share the Windows profile; never arrange concurrent overwrites of one source archive. First Terrain resource loading took about 169 seconds. Saved map cameras are static framing, not Galaxy-trigger playback. Terrain category exclusion/water and MP4/audio were not newly accepted in this renderer change.

See docs/PARALLEL_INSTANCES.md, docs/VALIDATION.md and BUILD.json in the ZIP. Source code and English instructions are published in the repository. Existing release assets remain unchanged.

Source commit: 34b4343376d1598cbe0b51124833562bfb1826c2.

ZIP SHA-256: f85f524ce4b98c3c1bc804c19ee42ac3f3f7478ea9587eaa91950d31d1f136b6.

v0.9.2-rc.1 — Native connection fix and live recovery validation

Choose a tag to compare

@VoVanRusLvSC2 VoVanRusLvSC2 released this 21 Oct 10:27

Fixes the Win32 126 native connection failure that blocked original Editor generation, compilation and rendering in v0.9.1-rc.1.

The existing owned startup bootstrap now loads the bridge and initializes callbacks on the Editor's own GUI thread. Requests no longer register a DLL-backed hook across processes. Native commands, exact document/PID/thread checks, private-desktop isolation and source preservation remain in force. The failing Windows registration path was reproduced independently of SC2; a specific underlying kernel resource limit or security product is not claimed as proven.

Live validation of the shipped executables

  • Six alternating XML submissions: original generation, Compile All with zero errors, Galaxy export and exact HTTP download hashes.
  • Wrong context, malformed XML and discarded orphan GUI: rejection, stale-export refusal and recovery.
  • Actual Glicko GUI: zero native compiler errors; a private array-declaration negative produces the expected five errors, followed by successful recovery.
  • Nydus v54 with installed dependencies: zero native compiler errors; 342,851-byte Galaxy, SHA-256 ad36611c87c754f9944b978f921e67ee7767f75a277f0a293d98830f2aaff078.
  • Original Nydus Save As → Close → disk reopen, MPQ component comparison, malformed Data diagnostics, old/new message separation and healthy reload.
  • Three saved map-camera captures with native readback; four Nydus cutscene camera/time captures. Images were inspected for visible terrain, units/decor and scene models.
  • Mixed native versions fail closed and clean up their owned worker.
  • All live observations recorded zero visible Editor windows, foreground samples and input-desktop changes. No mouse/keyboard injection or desktop switch. All owned test Editors were closed; user sources and installed Editor stayed unchanged.

50 Python tests, three C++ suites, packaged HTTP and packaged MCP stdio checks passed. The MCP tool count remains 18. Both EXEs embed exactly the five native binaries used in the live tests.

Upgrade

Replace the complete release and restart the owned API/MCP worker. Native protocol 11 is incompatible with old host/bootstrap/bridge/controller combinations. Do not copy only one DLL into an older release. The installed StarCraft II Editor does not need patching or reinstalling.

This is a prerelease, not a general map/rendering certificate. Saved cameras do not execute Galaxy trigger cinematics. Terrain category exclusions, water acceptance and broader map/build coverage remain open. General safe request cancellation/deadlines are not implemented; initial native Terrain loads can take minutes. MP4/audio historical evidence is unchanged and was not rerun for this correction. The separate converter's GUI capability refusals are unchanged.

Source and English documentation are included in the repository; the ZIP includes English documentation, build metadata and SHA-256 checksums. License and attribution remain unchanged.

Source commit: 2ad6406977fee5e771f226e21a23c53702b58bb5.

ZIP SHA-256: fd36e145430c137354caaa5a8b77644fc7f70a493b17a0ad0d820b6ba68dde0f.