From c926ec40b007ab1a79ba159f0f7f5a6360399442 Mon Sep 17 00:00:00 2001 From: CPTN_Cosmo Date: Sat, 30 May 2026 23:07:47 +0200 Subject: [PATCH] Updated Third Party Development Details (markdown) --- Third-Party-Development-Details.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/Third-Party-Development-Details.md b/Third-Party-Development-Details.md index de4b2c9..a713c4e 100644 --- a/Third-Party-Development-Details.md +++ b/Third-Party-Development-Details.md @@ -1,5 +1,7 @@ As with any Foundry system, you make a module and define a few `compendiums` to store your items, journals or other entities in to distribute them to others. There are however some extra considerations if you are adding specific homebrew, and some help on those is found below: +Please also check [Module-Builder-Information](Module-Builder-Information) + ## Custom Domains If you are adding custom domains for your classes and domain cards, then those domains need to always be present when the module is active. Simply add your new domains as keys on the config path `CONFIG.DH.DOMAIN.domains` in the Foundry init hook for your module: @@ -88,8 +90,3 @@ Hooks.once('init', () => { }); ``` -## Custom Attribution Sources -If you want to add a new attribution source to the system you can register them with `CONFIG.DH.GENERAL.attributionSources` in the Foundry init hook. -```js -CONFIG.DH.GENERAL.attributionSources.forevermore = { label: "Forevermore", values: [{ label: "Campaign - Forevermore" }] } -``` \ No newline at end of file