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

Splitting delve and starforged content in to their own packages #835

Open
rsek opened this issue Jun 28, 2023 · 1 comment
Open

Splitting delve and starforged content in to their own packages #835

rsek opened this issue Jun 28, 2023 · 1 comment
Labels
epic complex issues with multiple parts

Comments

@rsek
Copy link
Collaborator

rsek commented Jun 28, 2023

Place to collect discussion, notes, outlines etc on how this will be organized

@rsek rsek added the epic complex issues with multiple parts label Jun 28, 2023
@rsek
Copy link
Collaborator Author

rsek commented Jun 28, 2023

Here's a draft roadmap for how packs and item types could be distributed across the packages. This is intended as a target, not an MVP.

Note that type renames are really easy now. plus, checking the type property is a very direct and legible way to check if something needs a migration in migrateData.

foundry-ironsworn system

Document Types

Actors

  • pc (currently character)
    • a more precise label (npcs are characters too), and also much shorter
  • party (currently shared or starship). i'm working on a PR for this.
  • npc (currently foe)
    • rationale: foe means, well, a foe. but if the point of this is to provide a token, i don't think it's too much of a stretch to imagine that folks might want them for companion assets, friendly NPCs, incidental vehicles, and so on
    • polymorphic functions could be managed with sheets
    • could accomodate some kind of document linking with ForeignDocumentField. e.g. link it to a PC's asset to make the sheet + token able to update the asset

Items

JEP

  • progress-track (currently progress). rationale: to distinguish it from progress items, and to reflect its nature (the JEP is literally just a bare track; the item is a container for a progress track, a clock, and some notes).

Classic Ironsworn compendium packs

I go back and forth on whether these should be included in foundry-ironsworn by default (downside: could be unwanted clutter for SF or custom IS hacks; extra data use), or as part of their own package (downside: system looks a bit sparse out of the box -- compensate with a dialog hint?).

A variation of the latter (which I haven't yet investigated) would be providing them as a preconfigured world. Since it's essentially the content for "the Ironlands" as a setting.

Consider ironsworn-classic here as a placeholder for whatever this ends up being.

  • 📂 Ironsworn Rulebook
    • ironsworn-classic.oracles (currently foundry-ironsworn.ironsworn-oracles, excluding those from Delve)
    • ironsworn-classic.assets (currently foundry-ironsworn.assets)
    • ironsworn-classic.npcs (currently foundry-ironsworn.foe-actors-is, excluding those from Delve)
      • note i'm working on dropping the foe progress items as a pack; special drag and drop functionality for foe/npc actors will replace them (so that users can still drag a foe on to their sheet and instantly add it as a new progress item)
    • ironsworn-classic.scenes (currently foundry-ironsworn.scenes)

ironsworn-delve module

Settings

  • enable/disable rules for delving
  • enable/disable rules for threats
  • enable/disable rules for failure track
  • enable/disable rules for rarities

Document Types

Actors

  • ironsworn-delve.site (currently site)

Items

  • ironsworn-delve.theme (currently delve-theme)
  • ironsworn-delve.domain (currently delve-domain)
  • ironsworn-delve.rarity: a new item type to represent delve rarities.

Compendium packs

  • 📂 Ironsworn: Delve
    • ironsworn-delve.oracles (currently part of foundry-ironsworn.ironsworn-oracles)
      • would it make sense to split out the oracles for threats and delve sites, which are associated with their own "submodules" of rules?
    • ironsworn-delve.moves (currently part of foundry-ironsworn.moves)
      • would it make sense to provide each group of optional moves as its own compendium pack? rationale: compendium packs are a clean "unit" for enabling/disabling a modular group of content within a package.
    • ironsworn-delve.npcs (currently part of foundry-ironsworn.foeactorsis)
    • ironsworn-delve.themes (currently foundry-ironsworn.delve-themes)
    • ironsworn-delve.domains (currently foundry-ironsworn.delve-domains)
    • ironsworn-delve.rarities: new pack. the premade rarities from the book.
      • we could put the "Wield a Rarity" move in here too, as it's an Item. then all rarity rules would be in one tidy pack.
    • ironsworn-delve.sites: new pack. the premade delve sites from the book.

ironsworn-starforged module

Document Types

Actors

  • ironsworn-starforged.location (currently location)
    • alternatively: make it core to foundry-ironsworn and develop some sheets/configuration to make it usable for classic ironsworn locations

Compendium Packs

  • 📂 Ironsworn: Starforged Rulebook
    • ironsworn-starforged.oracles
    • ironsworn-starforged.moves
    • ironsworn-starforged.assets
    • ironsworn-starforged.npcs

ironsworn-sundered-isles module

Settings

  • the curse die
  • multiple supply tracks

Compendium Packs

  • 📂 Sundered Isles
    • ironsworn-sundered-isles.oracles
    • ironsworn-sundered-isles.moves
    • ironsworn-sundered-isles.assets
    • ironsworn-sundered-isles.npcs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic complex issues with multiple parts
Projects
None yet
Development

No branches or pull requests

1 participant