You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey guys I found this in your Paladin.txt not sure if its a little bug when you extract the data but thought id put it in here because your spell data files are really helpful - report from haiku below
Two stray Demon Hunter records in Paladin raw data dump
While processing data/spelldata/raw/paladin.txt for PvP talent extraction, I found two consecutive records that don't belong to the Paladin class at all:
Name : Dash of Chaos (id=427794) [Spell Family (107), Passive, Hidden]
Talent Entry : Havoc [tree=spec, row=3, col=1, max_rank=1, req_points=0]
Class : Demon Hunter
School : Physical
Labels : 16: Class Spells
: 26: Paladin Spells
: 292
Description : For ... sec after using Fel Rush, activating it again will dash back towards your initial location.
Name : Deflecting Dance (id=427901) [Spell Family (107)]
Class : Demon Hunter
School : Physical
Labels : 16: Class Spells
: 26: Paladin Spells
: 292
Tooltip : Absorbing $w1 damage.
Both are clearly Demon Hunter Havoc spells (Fel Rush follow-up and a defensive absorb), not Paladin. "Havoc" isn't a Paladin spec, and both records explicitly say Class: Demon Hunter.
A likely lead: both stray records carry Labels: 26: Paladin Spells despite their Class field correctly saying Demon Hunter. Whatever query generated paladin.txt looks like it filtered by that Label ID (26, "Paladin Spells") rather than by Class, and these two Demon Hunter spells happen to also carry that label. Might be worth checking whatever's on the other end of that label ID.
Scope: contained — these are the only 2 Class: Demon Hunter records in the whole file, they're consecutive, and the very next record after them is back to a normal Class: Paladin entry. Not a wider contamination as far as I can tell.
Why this matters beyond just being messy data: only one of the two (Dash of Chaos) is even detectable by a downstream parser — it has a Talent Entry: Havoc [tree=spec, ...] line, so any script checking talent-tree spec names against Paladin's real specs (Holy/Protection/Retribution) will flag it as unrecognized. Deflecting Dance has no Talent Entry line at all, so it silently lands wherever "no talent tree" records go (baseline/core spell list, in most downstream splits) with zero warning — indistinguishable from a real Paladin spell to anything that isn't specifically checking the Class field record-by-record.
Details:
Build/version: SimC 1205-01, WoW 12.0.7.68453
File: data/spelldata/raw/paladin.txt
Spell IDs: 427794 (Dash of Chaos), 427901 (Deflecting Dance)
Happy to provide more surrounding context from the raw dump if useful for tracking down where the extraction picked these up.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hey guys I found this in your Paladin.txt not sure if its a little bug when you extract the data but thought id put it in here because your spell data files are really helpful - report from haiku below
Two stray Demon Hunter records in Paladin raw data dump
While processing data/spelldata/raw/paladin.txt for PvP talent extraction, I found two consecutive records that don't belong to the Paladin class at all:
Name : Dash of Chaos (id=427794) [Spell Family (107), Passive, Hidden]
Talent Entry : Havoc [tree=spec, row=3, col=1, max_rank=1, req_points=0]
Class : Demon Hunter
School : Physical
Labels : 16: Class Spells
: 26: Paladin Spells
: 292
Description : For ... sec after using Fel Rush, activating it again will dash back towards your initial location.
Name : Deflecting Dance (id=427901) [Spell Family (107)]
Class : Demon Hunter
School : Physical
Labels : 16: Class Spells
: 26: Paladin Spells
: 292
Tooltip : Absorbing $w1 damage.
Both are clearly Demon Hunter Havoc spells (Fel Rush follow-up and a defensive absorb), not Paladin. "Havoc" isn't a Paladin spec, and both records explicitly say Class: Demon Hunter.
A likely lead: both stray records carry Labels: 26: Paladin Spells despite their Class field correctly saying Demon Hunter. Whatever query generated paladin.txt looks like it filtered by that Label ID (26, "Paladin Spells") rather than by Class, and these two Demon Hunter spells happen to also carry that label. Might be worth checking whatever's on the other end of that label ID.
Scope: contained — these are the only 2 Class: Demon Hunter records in the whole file, they're consecutive, and the very next record after them is back to a normal Class: Paladin entry. Not a wider contamination as far as I can tell.
Why this matters beyond just being messy data: only one of the two (Dash of Chaos) is even detectable by a downstream parser — it has a Talent Entry: Havoc [tree=spec, ...] line, so any script checking talent-tree spec names against Paladin's real specs (Holy/Protection/Retribution) will flag it as unrecognized. Deflecting Dance has no Talent Entry line at all, so it silently lands wherever "no talent tree" records go (baseline/core spell list, in most downstream splits) with zero warning — indistinguishable from a real Paladin spell to anything that isn't specifically checking the Class field record-by-record.
Details:
Build/version: SimC 1205-01, WoW 12.0.7.68453
File: data/spelldata/raw/paladin.txt
Spell IDs: 427794 (Dash of Chaos), 427901 (Deflecting Dance)
Happy to provide more surrounding context from the raw dump if useful for tracking down where the extraction picked these up.
All reactions