Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cap Doom Blast expiration mode and use charge based calcs for skills that ignore tick rate #6720

Merged
merged 4 commits into from
Dec 31, 2023

Conversation

Paliak
Copy link
Contributor

@Paliak Paliak commented Sep 20, 2023

Fixes #6492 (comment) implements #7143

Description of the problem being solved:

At 100% reduced curse duration Doom Blast expiration mode should behave like curse replacement mode since the curse will instantly expire.

Doom blast modes expiration and replacement modes did not allow for curse overlaps. This pr changes the config logic to show the config option when applicable.

Doom Blast expiration and replacement modes used simulation based calculations instead of charge based ones causing unexpected tick rounding during simulation. This pr makes all skills that are the only skill in the current trigger group and ignore server tick rate to use charge based calcs to avoid tick rounding.

This pr also implements hexvlast replacement mode for doom blast which uses the inverse of the sum of fastest hexblast and triggering curse cast time.

@Paliak Paliak changed the title Cap Doom Blast expiration mode by curse cast rate. Cap Doom Blast expiration mode and use charge based calcs for skills that ignore tick rate Sep 20, 2023
@Paliak Paliak added the bug: calculation Numerical differences label Sep 21, 2023
@LocalIdentity LocalIdentity merged commit 73482fe into PathOfBuildingCommunity:dev Dec 31, 2023
@Paliak Paliak deleted the capExpirationMode branch January 23, 2024 19:08
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.

Cast on Critical Strike Trigger Rate being calculated incorrectly
2 participants