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

Bug: Goblin's Burn It! feat applies persistent damage to impulses #16669

Open
Jakub-L opened this issue Sep 24, 2024 · 1 comment · May be fixed by #16678
Open

Bug: Goblin's Burn It! feat applies persistent damage to impulses #16669

Jakub-L opened this issue Sep 24, 2024 · 1 comment · May be fixed by #16678
Labels
bug Functionality that is not working as intended

Comments

@Jakub-L
Copy link

Jakub-L commented Sep 24, 2024

Summary

The Goblins' ancestry Burn It! feat adds a "+1 status bonus to any persistent fire damage you deal". However, this bonus persistent damage is added to a fire gate kineticist's fire blast, where it shouldn't. Since the blast doesn't deal persistent damage, it shouldn't get a bonus.

Replication

  1. Create a new actor, give it the Goblin ancestry
  2. Select the Kineticist class and choose single fire gate (feat selection doesn't matter)
  3. Add the Goblin ancestry Burn It! feat
  4. The damage for the Elemental Blast is now 1d6 fire + 1 persistent fire, where it should be 1d6 fire.

Notes

I have checked whether this bonus also applies to:

  • A fighter's longsword attack (it doesn't)
  • A water-gate kineticist's blast (it doesn't)
  • A fire/metal dual-gate kineticist's metal blast (it does)

I expect this is some weird interaction with the fire gate?

@pedrogrullada
Copy link
Collaborator

From my testing, it looks like this is a more general issue where typed bonuses to persistent damage are being added to disabled instances of persistent damage (such as the Fire Gate's Critical Blast)

@pedrogrullada pedrogrullada added the bug Functionality that is not working as intended label Sep 24, 2024
@CarlosFdez CarlosFdez linked a pull request Sep 25, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Functionality that is not working as intended
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants