Skip to content

Conversation

@LocalIdentity
Copy link
Contributor

We can no longer use the unresolved values for skills with multiple levels as some skills grab the base value from the first set and add it to the second/third and this doesn't work correctly with the previous method
This also removes a bunch of duplicate stats that appeared on some skills
I made it so that skills with only 1 level keep the previous method of only using the statInterpolation formula as otherwise it would break minion skills that work this way

There is still an issue where running the export script multiple times without restarting the exporter will duplicate the constant stat entries but I was running out of time to fix it

The only actual issue with a gem now is the ShieldCharge gem which has too many statInterpolation entries. It doesn't cause any issues in the program but would be nice to fix as it may cause an issue in the future on another gem

Before:
image
image
image

After:
image
image
image

Fixes #412

We can no longer use the unresolved values for skills with multiple levels as some skills grab the base value from the first set and add it to the second/third and this doesn't work correctly with the previous method
This also removes a bunch of duplicate stats that appeared on some skills
I made it so that skills with only 1 level keep the previous method of only using the statInterpolation formula as otherwise it would break minion skills that work this way

There is still an issue where running the export script multiple times without restarting the exporter will duplicate the constant stat entries but I was running out of time to fix it

The only actual issue with a gem now is the ShieldCharge gem which has too many statInterpolation entries. It doesn't cause any issues in the program but would be nice to fix as it may cause an issue in the future on another gem
@LocalIdentity LocalIdentity added the bug: calculation Numerical differences label Jan 30, 2025
* Updated skills.lua to not duplicate stats

* AdditionalStats are being set as resolved values now
@Wires77 Wires77 merged commit 0a584a7 into dev Feb 4, 2025
2 checks passed
@LocalIdentity LocalIdentity deleted the fix_stat-sets branch February 4, 2025 04:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug: calculation Numerical differences

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ember Fusillade secondary effect

3 participants