Skip to content

Fix swapped Cold/Lightning columns in DamageCalculationTypes and name the unnamed ones - #246

Merged
SnosMe merged 1 commit into
poe-tool-dev:mainfrom
juddisjudd:main
Sep 9, 2026
Merged

SnosMe merged 1 commit into
poe-tool-dev:mainfrom
juddisjudd:main

Conversation

@juddisjudd

Copy link
Copy Markdown
Contributor

ColdDamageStats and LightningDamageStats have each other's stats. On every row, the column named Cold points at *_lightning_damage and the column named Lightning at *_cold_damage. For MainHandAttack, Cold holds Stats rows 262 and 263, which are main_hand_minimum/maximum_lightning_damage. This swaps the two names. Column order and types are unchanged.

The unnamed columns after IsAttack point at the same kind of stat on all 13 rows, so this names 26 of them: the per-element stun, freeze and pin multipliers, the accuracy stats, base and double crit chance, eventual crit, and the reference to the row's *FakeHitForAilments twin with its bool.

Columns 12 and 40 stay unnamed. Both are bools that are true on real hits and false on the fake-hit and self-damage rows, and nothing in the data says which is which.

Checked at 4.5.5.1.6 by resolving every key against Stats on all 13 rows.

…tning stats

The columns named ColdDamageStats and LightningDamageStats hold each other's
stats: the Cold column resolves to *_minimum/maximum_lightning_damage and the
Lightning column to the cold pair, on every row.

The 28 columns after IsAttack resolve to a consistent stat across all 13 rows:
the per-element stun, freeze and pin multipliers, the accuracy stats, base and
double crit chance, eventual crit, and a self-reference to the row's
FakeHitForAilments twin with the matching bool. Two bools stay unnamed; they
are true on every real hit and false on the fake-hit and self-damage rows.
@SnosMe
SnosMe merged commit 634a704 into poe-tool-dev:main Sep 9, 2026
1 check passed
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.

2 participants