Shark that walks like a man
Shark that walks like a man
I don't think we're going to await a user-provided callback.
Comment from from #11620: > The [PackageCompatibility](https://foundryvtt.com/api/classes/foundry.packages.PackageCompatibility.html) and [PackageRelationships](https://foundryvtt.com/api/classes/foundry.PackageRelationships.html) fields do not properly share their `@property` values in the official docs. The type links for the typedefs in `resources/app/common/packages/module.mjs` are...
Reach isn't assessed, which is a prerequisite for highlighting reach assessment.
"check" roll options are for when you're rolling, and even then they're only used after the roll is completed.
lil experiment: ```diff diff --git a/client/data/abstract/client-document.js b/client/data/abstract/client-document.js index 85dad6485..874103d5f 100644 --- a/client/data/abstract/client-document.js +++ b/client/data/abstract/client-document.js @@ -1,3 +1,8 @@ +/** @import { abstract, utils } from "../../../client-esm/client.mjs" */ +/** @import {...
I think we'll be able to not have these type assertions once all actor/item subtypes are data models.
What information do you envision that isn't in the adjustment tooltip?
What information would the "synthetic" note contain? We can't reliably turn a predicate into a meaningful sentence or two.
The full item description?