Foundry VTT - Base package Manifest
Base Module/system/World manifest to inherit from
| Type | object |
|---|---|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/foundry-vtt-base-package-manifest/latest.json |
| Source | https://www.schemastore.org/foundryvtt-base-package-manifest.json |
Validate with Lintel
npx @lintel/lintel check
Properties
This field can contain a more lengthy description of the package. This text can be used to describe the functionality, list contact information, provide recommendations to contributors or testers, or any other information you feel is important to provide. This field can contain HTML to structure and style your text. For a system, this is also a good place to include any special licensing or attribution information that you need to distribute.
An array listing each author as an object that contains a name and potentially some contact details.
A path to a license file relative to the root package folder or a publicly accessible URL which contains the software license that applies to this package.
A path to a read-me file relative to the root package folder or a publicly accessible URL which contains instructions or information about the package.
Flag data.
(undocumented, intended to be used by core Foundry in the future)
3 nested properties
A list of localization files that Foundry can use to translate strings.
Packages may come bundled with Compendium packs which include game content for various Document types. Compendium packs are defined as objects which have their own internal metadata structure.
Packages can require modules, systems, or worlds be installed to allow their use. If a package has been installed with dependencies, but its dependencies are missing, it cannot be enabled.
4 nested properties
Will only allow the package to activated within Worlds which are running one of these systems and with a compatible version.
If a package has been installed with dependencies, but its dependencies are missing, it cannot be enabled.
(undocumented, intended to be used by core Foundry in the future)
(undocumented, intended to be used by core Foundry in the future)
A package may request for a specialized socket namespace to be provided. If set to true, a socket event will be handled by the server with the name system.${id} (for a system) or module.${id} (for a module), and will transact a arbitrary data object by broadcasting that data to all connected clients. This allows the package to have a reserved channel for messaging events which are needed to coordinate actions across multiple connected clients.
(undocumented, used for premium packages)
(undocumented)
(undocumented, intended to be used by core Foundry in the future)
(intended to be used by core Foundry in the future, see Module Sub-Types article)
(Manifest+ field)
(Manifest+ field)
(Manifest+ field)
Definitions
"lib-wrapper""dnd5e"
Relative path to a file, case sensitive.
"src/main.mjs""lang/en.json""packs/loot.db"
A public URL.
"https://example.com""https://raw.githubusercontent.com/foundryvtt/worldbuilding/master/system.json"
"1.0.0""0.5.0-beta""1.0""9.361""2023-04-08""20220312"
Flag data.
The type attribute instructs FoundryVTT that the dependency may be on a different type of package. By default dependencies are assumed to be a module, so if you want to depend on a system or world you should be explicit.
3 nested properties
Flag data.