foundry-ironsworn
foundry-ironsworn copied to clipboard
ben
Ironsworn and Starforged, for Foundry VTT
* implements a low-effort workflow for adding additional icons (as a total replacement for the custom icon font); icons from game-icons.net can now be used *nearly* as-is. detailed instructions are...
see the callout boxes of the "Derelict" oracles section of the book for more information on typical use. my impression is that they're of secondary status, useful for optional detail....
Discovered as part of the fix to #411. Manual rolls should have a visual indicator when the DF Manual Rolls "Flag manual rolls" feature is checked, but as of now...
faction oracles are structured enough that they might benefit from this. some stuff to think about: * in dataforged, the faction name oracle includes string templating data for composing names....
it doesn't allow for unlimited depth - the maximum appears to be 3 deep. for Ironsworn classic, that's plenty, but for starforged it may present some challenges. i'm still considering...
related to, but probably simpler than, #387 . some sample structures: ### Actors * 📁 [Game] [Foes/Encounters] * 📁 [Foe/Encounter Type] * 💼 [Foe/Encounter] ### Items * 📁 [Game] Moves...
the idea is that "Next release" can be updated as changes are made and cease to be "in progress", and then renamed to the next release number when a release...
there's a few "canonical" mechanical items that modify maximum health/spirit, like Ironsworn's Battle-Scarred and Honourbound assets:   there's a logic to being able to set the Supply maximum as...
since many of these touch the same files, here's an overview of tasks to improve code readability, semantics, or otherwise improve dev QoL without user-facing changes to appearance or basic...
This is a rough proof-of-concept for the idea outlined in https://github.com/ben/foundry-ironsworn/issues/386#issuecomment-1152949360. The idea is that all the data that's currently stored in progress item data is now stored in flags...