Skip to content

Commit

Permalink
Update CHANGELOG.md
Browse files Browse the repository at this point in the history
  • Loading branch information
ben committed Sep 9, 2023
1 parent f0b9b41 commit 63b1824
Showing 1 changed file with 6 additions and 4 deletions.
10 changes: 6 additions & 4 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,13 +2,15 @@

## Next Release

- Make player condition meters and momentum available as bar displays on actor tokens
- Under the hood: all meter fields are now objects with `max` and `value` properties, rather than a single number value
- Under the hood: Migrate all actor and item subclasses to DataModel API. This brings several benefits such as stricter run-time validation which improve the reliability of the data used in `foundry-ironsworn`, and near-instant data migrations. It also makes it _much_ easier to implement data migrations for new features in the future.
- Add a hook that fires when custom oracle registration is ready ([#864](https://github.com/ben/foundry-ironsworn/pull/864))
- Organize compendium packs into folders
- Improve appearance of v11 compendium sidebar and popouts with the "Phosphor" theme
- Under the hood: refactor all `RollTable`s and oracle rolls to use a single standardized pipeline (with `foundry-ironsworn`-style table roll messages) by default; certain kinds of results will fall back to FVTT-style messages instead.
- Include most of Starforged's oracle icons in the `foundry-ironsworn/assets` directory -- use them as symbolic tokens, map pins, etc
- Make player condition meters and momentum available as bar displays on actor tokens
- Under the hood changes:
- All meter fields are now objects with `max` and `value` properties, rather than a single number value
- Migrate all actor and item subclasses to DataModel API. This brings several benefits such as stricter run-time validation which improve the reliability of the data used in `foundry-ironsworn`, and near-instant data migrations. It also makes it _much_ easier to implement data migrations for new features in the future.
- Refactor all `RollTable`s and oracle rolls to use a single standardized pipeline (with `foundry-ironsworn`-style table roll messages) by default; certain kinds of results will fall back to FVTT-style messages instead.

## 1.21.7

Expand Down

0 comments on commit 63b1824

Please sign in to comment.