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] Adding additional damage with AE does not include damage types #483

Open
maxobremer opened this issue Aug 20, 2024 · 2 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@maxobremer
Copy link

Description
When you use an active effect to add extra damage, for example for the divine favor spell, the extra damage is added, but loses its damage type.
For divine favor i made an active effect with system.bonuses.mwak.damage ADD +1d4[radiant]
image
Without any modules it rolled the damage of the attack with the radiant damage separate.
image
With RSR active the roll used the [radiant] as flavour in the roll but just piled it on the slashing damage.
image

Steps to Reproduce

  1. Have only RSR as your active modules
  2. give an actor an affect that grants them additional damage set up like: system.bonuses.mwak.damage ADD +1d4[radiant]
  3. have quick roll for items enabled in the RSR settings for items*
  4. Roll for damage with a melee weapon or whatever you have given extra damage
  5. See that the radiant damage is added as flavour but not as actual radiant damage

*I tested this with only quick roll enabled and with every setting enabled separately. Issue persists as long as you have quick roll enabled even when you use alt to override it. No quickroll enabled=no issue

Versions

  • Module: [3.2.0]
  • dnd5e: [3.3.1]
  • Foundry: [12.331]

Other Modules
No other modules

@maxobremer maxobremer added the bug Something isn't working label Aug 20, 2024
@maxobremer maxobremer changed the title [BUG] Adding additional damage does not include damage types [BUG] Adding additional damage with AE does not include damage types Aug 20, 2024
@MathewBissonnette
Copy link

It appears the problem is in hooks.js. On line 60, changing CONFIG.DND5E.aggregateDamageDisplay = false; to instead =true fixes the problem.

@MangoFVTT
Copy link
Owner

This is an issue that needs to be fixed by a change in the system. The CONFIG.DND5E.aggregateDamageDisplay being false is correct, as this will stop damage fields of the same type from being combined into one field automatically (a big point of contention that people wanted). Unfortunately, it also means certain parsing of contextual damage (the [ ] stuff) is skipped as well. I'll need to make a PR for the system at some point that fixes it so the parsing is always done regardless of whether or not the damage is being aggregated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants