galaxy-debug-data-catalog

Debug Galaxy scripts with DataTable storage, catalog field access, and asset preloading.

3|2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/ShadowDragonSC2/Base.SC2Data --skill galaxy-debug-data-catalog-shadowdragonsc2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: galaxy-debug-data-catalog
Source: https://github.com/ShadowDragonSC2/Base.SC2Data/tree/main/.koda/skills/galaxy-debug-data-catalog
Command: npx skills add https://github.com/ShadowDragonSC2/Base.SC2Data --skill galaxy-debug-data-catalog-shadowdragonsc2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers building StarCraft II maps in Galaxy scripting often struggle to inspect and mutate runtime data, catalog fields, and asset loading state across triggers; this skill consolidates debugging output, a global key-value DataTable, catalog access, UserData, and preloading into a single, repeatable workflow.

Core Features & Use Cases

  • Debug Output: print messages to the in-game console for troubleshooting and quick insight into trigger flow.
  • DataTable Storage: provide a global and local key-value store to persist cross-trigger state and parameters.
  • Catalog Access: read and modify runtime data fields (e.g., unit stats, weapon data) directly from triggers.
  • User Data: access and utilize embedded user data for dynamic content configuration.
  • Asset Preloading: preload models, textures, and sounds to reduce hitching during gameplay.
  • Use Case: diagnose a triggering sequence by logging field values, cache results across triggers, and preload assets for smooth demos.

Quick Start

Enable the Trigger Debugger and begin using DataTable and Catalog calls in your Galaxy scripts to inspect and persist runtime state.

Frequently Asked Questions about galaxy-debug-data-catalog

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

FAQPage Schema
How do I debug Galaxy scripts and inspect runtime catalog fields in StarCraft II?

To debug Galaxy scripts, you can use native APIs like DataTable and CatalogFieldValue to read and write runtime catalog fields, while printing debug output directly to the in-game Trigger Debugger console for immediate troubleshooting.

What is the best way to persist cross-trigger state in Galaxy scripting without bank saves?

Persisting cross-trigger state in Galaxy scripting is best handled using a DataTable-backed key-value store, which supports both global and local scopes to cache parameters across triggers, avoiding bank-save use entirely.

How do I preload assets in Galaxy scripts to reduce gameplay hitching?

You preload assets in Galaxy scripts by utilizing the native PreloadAsset and PreloadModel APIs to load models, textures, and sounds before they are used, reducing gameplay hitching during trigger execution.

Can I access and modify unit stats directly from triggers using Galaxy native APIs?

Yes, you can access and modify unit stats and weapon data directly from triggers by using the CatalogFieldValue APIs to read and mutate runtime catalog fields during trigger events.

Does this debugging workflow support accessing embedded user data for dynamic content configuration?

Yes, the debugging workflow supports accessing embedded UserData through Galaxy native APIs, enabling dynamic content configuration by reading and utilizing embedded parameters across trigger sequences.