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

Consider a workflow for resolving multiple Rolls simultaneously or in a "chain" within one resolver UI #20

Open
zeel01 opened this issue Jul 4, 2023 · 1 comment
Labels
wontfix This will not be worked on

Comments

@zeel01
Copy link

zeel01 commented Jul 4, 2023

In many games, a single action may require more than one roll. For instance, an attack in 5e will generally require both an attack roll and a damage roll. When doing this virtually, there isn't a big problem - click one button, then the other. But for manual and Bluetooth rolls, the user experience is somewhat clunky and involves interacting with a lot of different parts of the UI.

Consider adding functionality such that a module or system can request multiple rolls at the same time, and only one roll prompt UI will appear, listing all of the needed rolls allowing them to all be resolved as part of a single workflow. Additionally/alternatively, rolls could potentially chain - such as rolling on a table that references another table - with the result of one roll potentially triggering another roll, which should ideally just be added to the roll dialog, rather than popping up an additional one.

These rolls could have optional data attached, such as specifying that one roll is dependent on another (if the attack roll fails, the resolver can resolve early without waiting for the damage roll).

Ideally, in some of these situations multiple dice could be rolled all at once, resolving multiple rolls in one physical action. A damage roll rolled along with the attack could simply be discarded on a miss, but rolling all at once is faster. Or a handful of d20s could be rolled at the start of combat to generate the initiative order.

Potential use cases include:

  • Attack roll and damage roll (a d20 roll, and some damage roll that depends on the d20's outcome)
  • Rolling multiple types of damage separately for certain kinds of attacks
  • Contested ability checks between two creatures controlled by the same user [GM] (two d20 rolls, either or both could be advantage or disadvantage, but they are independent).
  • "Nested" rollable tables
  • Multiple separate attack rolls from one action (Eldritch Blast)
  • Multiple creatures rolling saves against an area of effect (For n creatures, you could roll up to n d20s at the same time, and they would be evaluated in the order they register. So for instance if you have 2 dice and need to roll 4 saves, you can roll 2d20 twice and Foundry would assign one individual d20 roll to each creature.)
  • Multiple creatures rolling for initiative (As above, roll as many dice as you have repeatedly until you satisfy all the rolls)
@aaclayton
Copy link
Contributor

Out of scope until unfulfilled rolls is absorbed into core in V12.

@aaclayton aaclayton added the wontfix This will not be worked on label Jul 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants