FG Spreadshirt Swag
  1. #1

    Struggling to Understand Weapon Effect Automation

    I thought I had this figured out but apparently not.

    Are weapon automation effects applied as if they were an effect on the character using the weapon? My assumption was that they were applied to the target of the attack. I was trying to add "PERS: 1d4 fire" as a weapon effect, but it didn't work.

  2. #2
    Trenloe's Avatar
    Join Date
    May 2011
    Location
    Colorado, USA
    Posts
    29,848
    Weapon effects modify either an attack or a damage action, they don’t apply an effect to the target - so any effect that specifically modify an attack or damage action will apply. Such as ATK, target AC, DMG, etc.. PERS effects don’t specifically modify a base damage action, persistent damage is completely separate and is actually an effect that is applied to the target, not an effect that applies directly to the damage action.

    You can, however, add a new damage instance to the weapon - use 1d4 for the damage and persistent, fire for the damage types. This will apply an effect to the target of PERS: 1d4 fire when damage is rolled with that weapon.
    Private Messages: My inbox is forever filling up with PMs. Please don't send me PMs unless they are actually private/personal messages. General FG questions should be asked in the forums - don't be afraid, the FG community don't bite and you're giving everyone the chance to respond and learn!

  3. #3
    Oh! I had no idea that was possible. Thank you, that both clears up my confusion and solves my problem.

  4. #4
    It seems that if you add a persistent effect to the damage that way and you you hit the creature again it will apply the persistent damage a second time or however many times it is hit with the same attack. I know that effects like clumsy, drained, etc do not stack, does persistent damage after multiple hits stack?

  5. #5
    Persistent damage will currently be applied multiple times and therefore roll the damage and the flat check as often as it is applied.
    This is a known issue and will be fixed in a later version. It is currently listed as entry RS2.118 in the issue tracking spreadsheet:
    https://docs.google.com/spreadsheets...it?usp=sharing

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
PF2E Playlist

Log in

Log in