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

Provide more granular rules configuration #819

Open
rsek opened this issue Jun 24, 2023 · 0 comments
Open

Provide more granular rules configuration #819

rsek opened this issue Jun 24, 2023 · 0 comments
Labels
🧵 type: discussion thread for extended discussion

Comments

@rsek
Copy link
Collaborator

rsek commented Jun 24, 2023

(copy pasted from discord for posterity)

here's a brain dump of how i could see a more granular, world-wide system configuration shaking out as far as options:

  • assets:
    • user can enable any number of asset sets with checkboxes
    • if multiple game asset sets are enabled, present a tabbed browser
  • oracles
    • user can enable any number of oracle sets with checkboxes
    • if multiple game oracle sets are enabled, present a tabbed browser
  • moves:
    • user can enable any number of move sets with checkboxes
    • if multiple game move sets are enabled, present a tabbed browser
  • impacts and debilities
    • MVP: global setting, simple toggle between "starforged impacts" and "ironsworn debilities"
    • further development: users can configure a custom list of impacts/debilities in the settings menu, and those will populate the statusEffect array
  • legacies and bonds
    • nothing really stopping them from coexisting, i suppose
    • each gets a checkbox. when ticked, its tab is added to character sheet
    • implies a change of layout from 2-col IS sheet. continue to offer old sheet for a time as we develop an alternative?
  • actor creation: presented actor types
    • checkboxes enable each type
  • progress track: what move gets used?
    • MVP: <select> a move in roll dialog
    • further development:
      • subtype is still a string, but it's now used as a label (comparable to asset's track.name)
      • add property: resolvedBy (optional; takes a progress move uuid)
      • UX: we present a dropdown of subtype/resolvedBy pairs as presets, but provide the option of going "off road"
      • consider a "global progress track types" config?
@rsek rsek added the 🧵 type: discussion thread for extended discussion label Jun 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🧵 type: discussion thread for extended discussion
Projects
None yet
Development

No branches or pull requests

1 participant