sc2data-effects-weapons

Create and validate SC2 effects, weapons, and upgrades XML against catalogsData.xsd.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SC2 Data Editor – Effects, Weapons, Upgrades, and the damage chain in XML. Use when creating or modifying CEffect* (damage, search, apply behavior, launch missile, set), CWeapon, or the full chain from weapon through to damage application. Also covers TargetFind, TargetSort, and Footprints. Always consult the catalogsData.xsd schema for exact fields and structure; do not assume unsupported fields exist. Do not use for actors/visuals (sc2data-actors-visuals) or unit/ability containers (sc2data-units-abilities).

Core Features & Use Cases

  • Define per-unit data files for weapons, upgrades, and their effect chains in XML.
  • Validate data against the catalogsData.xsd schema and align with the recommended per-file placement in GameData.
  • Use as a reference guide when implementing CEffect*, CWeapon, CUpgrade, and the full damage pipeline from weapon to impact.

Quick Start

Open Base.SC2Data/GameData for your unit and start editing its XML using the Data Editor workflow described in this Skill.

Frequently Asked Questions about sc2data-effects-weapons

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

FAQPage Schema
How do I create and validate SC2 weapon effect chains in XML?

SC2 data modeling automates creating and validating XML for SC2 effects and weapons. It builds the full damage chain from weapon to impact, enforcing schema-aligned fields and per-file placement in GameData to prevent errors.

What is the correct XML structure for SC2 effects and upgrades?

The correct XML structure for SC2 effects and upgrades follows the catalogsData.xsd schema. This ensures compatibility by enforcing schema-aligned fields and proper per-file placement within the GameData directory structure.

How do I validate SC2 Data Editor XML against the catalogsData.xsd schema?

You validate SC2 Data Editor XML by applying the catalogsData.xsd schema using recommended XML validation tooling. This process enforces schema-aligned fields and per-file structure to prevent data errors during design workflows.

Does this SC2 data modeling cover actors, visuals, and unit containers?

This SC2 data modeling does not cover actors, visuals, or unit containers. It is specifically scoped to CEffect*, CWeapon, CUpgrade, and the damage pipeline, excluding sc2data-actors-visuals and sc2data-units-abilities.

When should I use separate XML files for SC2 weapons and effects?

You should use separate XML files for SC2 weapons and effects to align with recommended per-file placement in GameData. This structure enforces schema-aligned fields and prevents compatibility errors when modifying Data Editor entries.

Can I define TargetFind and Footprints using SC2 XML data?

Yes, you can define TargetFind and Footprints using SC2 XML data. The Skill covers these elements alongside CEffect*, CWeapon, and CUpgrade when building or modifying Data Editor entries for your unit.