2 commits

Author	SHA1	Message	Date
Kelsi	08834ff498	feat(editor): add WSPL JSON round-trip authoring workflow ... Closes the WSPL open-format loop with --export-wspl-json / --import-wspl-json, mirroring the JSON pairs added for every other novel binary format. All 14 binary formats added since WOL now have full JSON round-trip authoring. Each spell round-trips all 18 scalar fields. Four enum-typed fields emit dual int + name forms so a hand-author can use either: • school (physical / holy / fire / nature / frost / shadow / arcane) • targetType (self / single / cone / aoe-self / line / ground) • effectKind (damage / heal / buff / debuff / teleport / summon / dispel) • flags (passive / channeled / ranged / aoe / friendly / hostile / ...) The flags bitset emits string-array form so a hand-author can write ["hostile", "aoe"] instead of having to remember that HostileOnly|AreaOfEffect = 0x110. Verified byte-identical round-trip on the mage preset (4 spells covering frost / fire / arcane schools and damage / buff / teleport effects, full flag and effect-value coverage). Adds 2 flags (544 documented total now).	2026-05-09 16:06:29 -07:00
Kelsi	5ea1f7ee2a	feat(pipeline): add WSPL (Wowee Spell Catalog) format ... Novel open replacement for Blizzard's Spell.dbc + SpellEffect.dbc + the AzerothCore-style spell_dbc / spell_proc tables. The 20th open format added to the editor — completes the canonical-data side of the gameplay graph. Each entry holds the metadata side of a spell: name, description, school, range, mana / cast / cooldown times, plus a single primary effect. The simplified effect model (one effectKind + min/max value + misc field) covers the common cases (damage / heal / buff / debuff / teleport / summon / dispel) without needing to reproduce the full multi-effect graph that classic Spell.dbc carries. Cross-references with previously-added formats: WLCK.channel.targetId (kind=Spell) -> WSPL.entry.spellId WQT.objective.targetId (kind=SpellCast) -> WSPL.entry.spellId WCRT.equippedMain (item with on-use) -> WIT -> WSPL Format: • magic "WSPL", version 1, little-endian • per spell: spellId / name / description / iconPath / school / targetType / effectKind / cast & cooldown & GCD ms / manaCost / range min..max / minLevel / maxStacks / durationMs / effectValueMin..Max / effectMisc / flags Enums: • School (7): Physical / Holy / Fire / Nature / Frost / Shadow / Arcane • TargetType (6): Self / Single / Cone / AoeFromSelf / Line / Ground • EffectKind (7): Damage / Heal / Buff / Debuff / Teleport / Summon / Dispel • Flags: Passive / Hidden / Channeled / Ranged / AreaOfEffect / Triggered / UnitTargetOnly / FriendlyOnly / HostileOnly API: WoweeSpellLoader::save / load / exists / findById; presets makeStarter (Strike + Lesser Heal + Power Word: Fortitude + Hearthstone, one per major effect kind), makeMage (Frostbolt 116 + Fireball 133 + Arcane Intellect 1459 + Blink 1953, canonical Classic spellIds), makeWarrior (Heroic Strike 78 + Thunder Clap 6343 + Battle Shout 6673 + Mortal Strike 12294). CLI added (5 flags, 535 documented total now): --gen-spells / --gen-spells-mage / --gen-spells-warrior --info-wspl / --validate-wspl Validator catches: spellId=0 + duplicates, empty name, school out of range, effectKind out of range, NaN range, range/value min>max, FriendlyOnly+HostileOnly conflict (incoherent), friendly-only with damage/debuff effect (incoherent), hostile-only with heal/buff effect, buff/debuff effect with durationMs=0 (instant fade — almost certainly authoring oversight). The validator caught a real preset-emitter authoring error during initial smoke testing — buff spells were setting effectValueMin without effectValueMax (validator's range check immediately flagged it), prompting an in-batch fix to set both fields. This is exactly the catch-the-typo purpose validators serve.	2026-05-09 15:58:09 -07:00