Hi all! Relatively new (or new to PF2e) GM here. Last night one of my players who is playing a Summoner raised the question of whether he can attempt Treat Wounds twice every hour instead of once since his Eidolon is a separate target (ie. Someone treats the Summoner’s wounds and then immediately treats the Eidolon’s wounds). I ruled in the moment that I didn’t think that sounded right, my reasoning being that they share a health pool and the PC shouldn’t be able to double its benefits solely because of which class it is. Can anyone tell me what the RAW is here, ideally with an AON reference I can point him to?

Edit: I found this thread which seems to suggest that I made the wrong call. I’d love to have a more official answer, but I think the idea that healing is supposed to be trivialized by certain combos makes sense.

  • Hi there,

    I don’t think that perspective is supported by RAW. From the Summoner rules:

    Lastly, the connection between you and your eidolon means you both share a single pool of Hit Points. Damage taken by either you or the eidolon reduces your Hit Points, while healing either of you recovers your Hit Points. [https://2e.aonprd.com/Classes.aspx?ID=18]

    Both can take damage and healing. The only distinction is that they share a hit point pool.

    • Seems to be the general consensus from what I’ve seen any time it’s been brought up even on the PF2e Discord. You just can’t do it off of a single effect, i.e. Ward Medic, but they can be healed individually with Treat Wounds.

      And yes, the Eidolon can indeed be healed as per the Eidolon feature of the Summoner class.

      Damage taken by either you or the eidolon reduces your Hit Points, while healing either of you recovers your Hit Points.

      So it seems pretty clear Treat Wounds works on them. If they couldn’t be injured, then they would be immune to damage which they aren’t. Inferring otherwise is imposing the flavor of ‘damage to the connection’ or something over rules, which I’m not a fan of in a system as tight as PF2e. (That’s just me, though.)