Log in

View Full Version : [Request] Target Self for Spell Actions Other Than Effects



Surge
April 28th, 2020, 12:55
Hello,

Would it possible to add a 'target self' option to the Cast, Damage, and Heal actions of spells under the action tab?

Is this something that is doable in an extension? Even so, I think it would have a wide enough use case that it would be beneficial to be added to the Ruleset as a standard. Of course, I have no idea if it is even possible.

Trenloe
April 28th, 2020, 13:03
Cast, Damage and Heal all use the standard FG targeting system. So, to apply the results of the action to the actor carrying out said action, target yourself before clicking the relevant button.

I'll consider adding a "targets" option similar to effects, but it won't be for a while yet (when I work on PF2 actions in more detail).

Surge
April 28th, 2020, 13:14
Thanks for the consideration Trenloe.

Yes I understand that they use the FG targeting system. It's just a bit of a pain to have to swap targets or drag the action to your own token each time.

Thanks again.

Trenloe
April 28th, 2020, 13:24
This will more than likely come in when I fully code affliction handling.

Trenloe
May 16th, 2020, 14:55
Something seen in the PFRPG2 development caverns...

https://www.fantasygrounds.com/forums/attachment.php?attachmentid=35542

Surge
May 16th, 2020, 15:42
That's awesome! Thank's ever so much. Looking forward to it!

Willot
May 17th, 2020, 02:55
Actually I wonder if this shouldn't be added to CORE. Other rulesets may benefit from this too

Trenloe
May 17th, 2020, 08:25
Actually I wonder if this shouldn't be added to CORE. Other rulesets may benefit from this too
It is in CoreRPG - you can use self targeting for the application of effects.

CoreRPG does not have specific code for cast, damage, heal, attack or save actions. The 3.5e ruleset, which PFRPG2 is based on, only uses the target selection system for effect targeting (because this was built into the underlying CoreRPG and inherited). I had to add the ability to select self only for each action not part of CoreRPG, and for this to be applied to the action when rolled.

Willot
May 17th, 2020, 08:36
Ah, yes of course, It didnt occur to me it was based on 3.5 but when you look at it you can see it peeking through

Drogo210
June 12th, 2021, 21:34
It is in CoreRPG - you can use self targeting for the application of effects.

CoreRPG does not have specific code for cast, damage, heal, attack or save actions. The 3.5e ruleset, which PFRPG2 is based on, only uses the target selection system for effect targeting (because this was built into the underlying CoreRPG and inherited). I had to add the ability to select self only for each action not part of CoreRPG, and for this to be applied to the action when rolled.

That would be very nice to add it to 5e as well so we can code Blood Hunter!

Milke
June 14th, 2021, 22:03
Can't you already just make an effect of Heal with the [SELF] added to it?
And I always see that IFT: CUSTOM effect. I always just put what I'm assigning to the target without putting CUSTOM. So, IFT: Hunted; ... but I always see people put IFT: CUSTOM (hunted).
Is there a benefit to doing it that way?

Trenloe
June 14th, 2021, 22:41
Can't you already just make an effect of Heal with the [SELF] added to it?
Effects have had Target -> Self for a long time. But other actions (damage, heal, etc.) haven't. See post #8. Also see post #5 for a screenshot of what was implemented in the PF2 ruleset last year.



And I always see that IFT: CUSTOM effect. I always just put what I'm assigning to the target without putting CUSTOM. So, IFT: Hunted; ... but I always see people put IFT: CUSTOM (hunted).
Is there a benefit to doing it that way?
IFT: XXXXX works fine if XXXXX is a recognized condition. Otherwise you must use IFT: CUSTOM(XXXXX) for it to correctly match a custom label. IFT: XXXXX will always return true if XXXXX is not a specific PF2 condition.

myyra
June 16th, 2021, 21:48
IFT: XXXXX will always return true if XXXXX is not a specific PF2 condition.

This seems like a very weird default behavior.