Commit graph

14 commits

Author SHA1 Message Date
de7c3f5fff
refactor: prevent creating items in actors that cannot own them
All checks were successful
ci/woodpecker/pr/checks Pipeline was successful
ci/woodpecker/push/checks Pipeline was successful
ci/woodpecker/manual/checks Pipeline was successful
ci/woodpecker/manual/release Pipeline was successful
2023-07-27 01:07:52 +02:00
7670d7f808
chore: reformat with 2 spaces
All checks were successful
ci/woodpecker/pr/checks Pipeline was successful
ci/woodpecker/push/checks Pipeline was successful
2023-07-10 22:33:01 +02:00
62065a8d31
feat: use new ActiveEffect transferral system
Closes #68
2023-07-09 23:17:38 +02:00
4b97bde6d9
feat: organize checks in columns 2023-07-09 23:16:55 +02:00
692d311558
fix: make ActiveEffects work properly 2023-07-09 23:16:54 +02:00
f25b46a226 feat: update for v10 2022-11-28 02:39:04 +01:00
6277e27056 refactor: convert to ECMAScript where necessary
Also drop @league-of-foundry-developers/foundry-vtt-types.
2022-11-28 02:38:17 +01:00
1e7492073e fix: simplify talent rank display in character sheet 2022-11-10 03:32:52 +01:00
c5d4ec1abd refactor: improve structure of src 2022-11-04 21:47:18 +01:00
9d7c570553 feat: replace spell category by spell groups
This also allows to assign a spell to multiple spell groups, which is the case for many spells in
the SRD.

Additionally, this makes many small improvements and fixes to the provided spell compendium.
2022-11-04 21:14:32 +01:00
ab31450dd8 fix: address a few problems with active effect application 2022-11-04 21:09:06 +01:00
b1ed05a796 feat: add functionality to apply Active Affects to owned Items
In the Active Effect Config, there are now additional inputs to configure the effect
to be applied to items owned by the actor instead of the actor itself. It is possible
to select the items to which to apply the effect via matching by name, or via a condition
expression, that provides similar capabilities as the evaluation of mathematical
expressions in rolls. Data from the Actor, Item, and Active Effect can be accessed
similar to how properties are accessed in roll formulas (using the prefixes `@actor`,
`@item`, and `@effect`). For example, in order to apply an effect to all ranged
weapons, the conditions would be
```js
'@item.type' === 'weapon' && '@item.data.attackType' === 'ranged'
```
2022-11-03 22:14:36 +01:00
12bc76ba54 refactor: use noImplicitOverride option 2022-05-29 17:48:49 +02:00
82217dd971 feat: add selectable check modifiers 2022-05-13 17:31:14 +00:00