Skip to content

include lineage flag on support gems#60

Open
tskimmett wants to merge 2 commits into
repoe-fork:masterfrom
tskimmett:codex/project-support-gem-lineage
Open

include lineage flag on support gems#60
tskimmett wants to merge 2 commits into
repoe-fork:masterfrom
tskimmett:codex/project-support-gem-lineage

Conversation

@tskimmett
Copy link
Copy Markdown

@tskimmett tskimmett commented May 17, 2026

What changed

  • Projected SupportGems.dat64.IsLineage into support gem JSON as is_lineage.

  • Refactored support gem parsing so convert_gem receives the matched SupportGems row directly, which now provides both icon and lineage metadata.

Why

Lineage support gems were not being explicitly represented in parsed skill gem data, which forced downstream consumers to infer lineage status from tags (apparently they aren't all tagged appropriately). This change preserves the source-of-truth lineage flag from the DAT layer.

I did notice what appears to be an issue in the source data where several supports for persistent buffs are incorrectly marked as lineage 🤷

@tskimmett tskimmett changed the title [codex] Project support gem lineage metadata Project support gem lineage metadata May 17, 2026
@tskimmett tskimmett changed the title Project support gem lineage metadata include support gem lineage flag May 23, 2026
@tskimmett tskimmett changed the title include support gem lineage flag include lineage flag on support gems May 23, 2026
@tskimmett tskimmett marked this pull request as ready for review May 23, 2026 03:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant