Effect Tagging #11

Closed
opened 2023-08-26 21:08:01 +02:00 by legendsmiths · 3 comments
Collaborator

Hero has 5 main effect outputs:

  1. Normal (body & stun, seems to be working)
  2. Killing (body plus stun multiplier)
  3. Stun only (only stun damage)
  4. Body only (only count the body damage normally)
  5. Effect (add up the dice like stun)

Within a Power, the ability to define which type of effect roll will be necessary for future automation.

A drop down with these options (as labeled above) would be perfect.

Then, when outputting the effect roll to chat do the following:
A. Include the label in output to clarify
B. In the case of #2, roll 1d3 and multiply the damage by the 1d3 roll to determine the amount of STUN.
C. In the case of #1-2, report BODY and STUN separately (and accessible for automated damge application)
D. In the case of #4, output the value only as STUN (no BODY)
E. In the case of #4, output the value only as BODY (no STUN)
F. In the case of #5, output the value as a die result (no BODY or STUN)

Other than B, this is only about output tagging with no automation. B would be a very helpful minor automation (hopefully) for inclusion in the current Basic version.

Hero has 5 main effect outputs: 1. Normal (body & stun, seems to be working) 2. Killing (body plus stun multiplier) 3. Stun only (only stun damage) 4. Body only (only count the body damage normally) 5. Effect (add up the dice like stun) Within a Power, the ability to define which type of effect roll will be necessary for future automation. A drop down with these options (as labeled above) would be perfect. Then, when outputting the effect roll to chat do the following: A. Include the label in output to clarify B. In the case of #2, roll 1d3 and multiply the damage by the 1d3 roll to determine the amount of STUN. C. In the case of #1-2, report BODY and STUN separately (and accessible for automated damge application) D. In the case of #4, output the value only as STUN (no BODY) E. In the case of #4, output the value only as BODY (no STUN) F. In the case of #5, output the value as a die result (no BODY or STUN) Other than B, this is only about output tagging with no automation. B would be a very helpful minor automation (hopefully) for inclusion in the current Basic version.
Owner

How is computed STUN ?

How is computed STUN ?
uberwald added the
enhancement
label 2023-08-26 21:42:37 +02:00
Owner

Should be OK in next release

Should be OK in next release
Owner

All fixed in next release, automation accepted in the current development scope.

All fixed in next release, automation accepted in the current development scope.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: public/fvtt-hero-system-6#11
No description provided.