sparkengine-run-package-and-release

Launch, smoke-test, package, and publish SparkEngine binaries via CPack and GitHub release workflows.

31|3|Updated Jul 26, 2025
One-click install
npx skills add https://github.com/Krilliac/SparkEngine --skill sparkengine-run-package-and-release-krilliac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sparkengine-run-package-and-release
Source: https://github.com/Krilliac/SparkEngine/tree/main/.claude/skills/sparkengine-run-package-and-release
Command: npx skills add https://github.com/Krilliac/SparkEngine --skill sparkengine-run-package-and-release-krilliac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operators of the SparkEngine C++ game engine need verified, repo-grounded instructions for launching engine binaries, bounding runs for smoke tests, producing distributable packages, and reading the release pipeline's evidence without conflating "built" with "published". ## Core Features & Use Cases - Launch runbook: Documents every runtime flag (-headless, -game, -test-frames, -exec), the module selection order, and copy-paste launch commands for windowed, headless dedicated server, and editor modes. - Smoke testing: Defines bounded-run recipes that pair exit codes with log evidence under the per-user %LOCALAPPDATA%/SparkEngine/Logs directory. - Packaging and release: Covers CMake install + CPack packaging (ZIP/NSIS/WIX/TGZ), the real status of the two in-engine GamePackagers, and the release.yml workflow's triggers, gates, and artifact evidence via gh commands. - Use Case: A CI engineer sees "CI is green but the nightly release failed" and uses the documented evidence commands (gh run view, gh release view nightly) plus the local CPack/PackageSmoke reproduction recipes to pinpoint the release-only gate that broke. ## Quick Start Ask the assistant to launch the SparkEngine headless dedicated server with the SparkGameMMOFPS module bounded to 60 test frames and verify the exit code and log output.

Frequently Asked Questions about sparkengine-run-package-and-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run SparkEngine as a headless dedicated server?

Launch SparkEngine.exe with -headless (or its alias -dedicated), -no-subprocess, and an explicit -game path to a module DLL. Add -threads to bound workers and -exec to run a console script, then verify the server by polling its UDP port rather than trusting the spawn.

How do I package SparkEngine into a zip or installer?

Run cmake --install on the configured build tree, then invoke cpack with the generated CPackConfig.cmake. CPack produces ZIP everywhere plus NSIS/WIX on Windows and TGZ on Linux, named SparkEngine-<version>-<System>-<Processor>.

Why does SparkEngine show a project selector instead of loading my game module?

A bare launch with two or more module DLLs next to the exe arms an ImGui project selector and loads nothing, because ModuleManager refuses bulk-loading. Pass -game <dll> explicitly or place a spark.modules.json manifest next to the executable.

Where does SparkEngine write logs and save files?

Logs and saves go to a per-user data root: %LOCALAPPDATA%/SparkEngine on Windows or $XDG_DATA_HOME/SparkEngine on POSIX, not beside the executable. A legacy working-directory Saves tree is migrated once with a marker file.

Why is CI green but the SparkEngine release failed?

The PackageSmoke test and CPack packaging run only in the release.yml workflow, not in per-PR build.yml, so a green PR does not prove packaging works. Reproduce locally with the install, cpack, and PackageSmoke recipes, then inspect the failed run with gh run view.

When should I not use this runbook for SparkEngine problems?

Route compile or CMake configure errors to the build/CI skill, merge or ship readiness verdicts to the change-control skill, module ABI and hot-reload questions to the modules skill, and .spk asset corruption to the asset-integrity skill.