Store Who-First on a Per-Combat Basis #41
Labels
No labels
Compat/Breaking
Kind
Bug
Kind
DevOps
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Security
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Foundry/ripcrypt#41
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, which team gets to go first is dictated by a world setting, which means that it could affect combats that it shouldn't when the user changes it.
The intent of this is ticket is to prompt the GM creating the combat (before it's created), asking which team should go first, this will also need to be stored in a property on the Combat document itself, which should be a system property.
Combats should also allow changing the Who-First after it is initially set in the case of adventure modules needing to have something set, and the GM wanting something different.