Joseph

This is going to be cleanly handled by the new Activities system in 4.0

This old issue seems related: https://github.com/foundryvtt/foundryvtt/issues/3315

Did you do a clean install? Sounds like you should hit up the _troubleshooting channel on the discord first.

One thing Foundry *could* consider using is accompanying .d.ts files - I've found some success in [Draw Steel](https://github.com/MetaMorphic-Digital/draw-steel/blob/main/src/module/data/actor/_types.d.ts) with importing Foundry's native types and then using the interfaces in these...

Concrete example of where this causes problems is `TextureData`, which gets all of its properties through the SchemaField constructor

Want to express support for resolving this issue. Example use case from a module I'm working on that's implementing the Level Up ruleset by EN Publishing: Characters can gain an...

The no-legacy issue is something that's an intentional change, per the patch notes > The legacy sheets are no longer available, as making them available would have required us to...

Yeah, I don't really want to edit hundreds of items because the spacing standards on the source field changed — I ran into this with zero modules on my copy...

Especially since there weren't any conventions or standards for what the Source: Book field meant or how it was used really prior to this update.

`SpellData#getCardData` returns `context.isSpell = true`, but the places `isSpell` gets used just do a plain type check for `type === "spell"`. This makes it difficult for module subtypes that are...