galaxy-debug-data-catalog

Expose DataTable, Catalog fields, and UserData during SC2 Galaxy triggers for debugging and modification.

7|1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/KimPlaybit/Starcraft-2-Editor-Skills --skill galaxy-debug-data-catalog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: galaxy-debug-data-catalog
Source: https://github.com/KimPlaybit/Starcraft-2-Editor-Skills/tree/main/.agents/skills/galaxy-debug-data-catalog
Command: npx skills add https://github.com/KimPlaybit/Starcraft-2-Editor-Skills --skill galaxy-debug-data-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging Galaxy scripts can be hard due to hidden data contexts. This skill exposes DataTables, Catalog fields, and UserData at runtime to simplify inspection and modification during map testing.

Core Features & Use Cases

  • Read and write global and per-player DataTable values during triggers.
  • Access and modify catalog fields (unit, weapon, upgrade) with per-player context.
  • Preload assets and generate debug output to streamline troubleshooting.

Quick Start

Open the Trigger Debugger and run a test map that uses DataTable and Catalog operations to inspect values.

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 data tables and catalogs during SC2 map testing?

You can debug Galaxy data tables and catalogs by exposing DataTable values, catalog fields, and UserData at runtime during triggers. This allows you to inspect and modify game data while running a test map in the Trigger Debugger.

Can I read and write per-player DataTable values in Galaxy triggers?

Yes, you can read and write both global and per-player DataTable values during triggers. This feature supports per-player scoping to help track individual player state during map development.

How do I access and modify SC2 catalog fields for units and weapons at runtime?

You can access and modify catalog fields for units, weapons, and upgrades with per-player context at runtime. This requires Galaxy script access to native Catalog APIs to inspect and tune values during triggers.

What is the best way to inspect hidden data contexts in Galaxy scripts?

The best way to inspect hidden data contexts in Galaxy scripts is by exposing DataTables, catalogs, and UserData at runtime. This simplifies troubleshooting by generating debug output and allowing live inspection during map testing.

Does this approach to debugging Galaxy scripts support asset preloading across triggers?

Yes, this debugging approach supports asset preloading across triggers. You can preload assets and generate debug output to streamline troubleshooting and ensure required game resources are available during runtime inspection.