sephll
September 6, 2022, 6:40pm
1
I cant find my shared Compendiums in the “Manage Modules” Tab. Creating new Shared Compendiums doesnt help either.
Thanks in advance!
3 Likes
opened 05:33PM - 27 Jul 22 UTC
closed 03:57PM - 28 Jul 22 UTC
breaking
compendium
packages
## Implemented Change
Packages which include compendium packs with the "Actor",… "Item", or "Adventure" type must designate the `"system"` field which clarifies the ID of the game system that those packs are designed for.
This can be done in one of two ways, indirectly via package relationships which is **preferred if possible** or directly via the compendium pack definition itself.
### Indirect Declaration via Relationships
A package which only works for a single game system can declare that singular system dependency in the `"relationships"` field thusly:
```js
"relationships": {
"systems": [
{"id": "pf2e"}
]
}
```
For packages which only support a single game system (i.e. the length of the "systems" array is 1) that game system will be automatically inferred for any compendium packs of the "Actor", "Item", or "Adventure" type.
### Directly via Compendium Pack Data
In addition to or instead of the above method a system can be declared explicitly on the compendium pack itself. This is necessary in cases where a module supports multiple game systems.
```js
"packs": [
{
"name": "adventure",
"label": "Pathfinder Beginner Box",
"path": "packs/adventure.db",
"type": "Adventure",
"system": "pf2e"
}
],
```
Packages which include a compendium of type "Actor", "Item", or "Adventure" and do not clarify the system that pack is intended for will fail validation and that compendium pack will be unavailable to be loaded inside Foundry VTT.
-----------------------------
## Original Comment Below
Reported by `@Toasty#8538`
Adventures that support multiple systems can run into issues where the import will attempt to import documents for both systems when importing. Having the adventure import check `game.system.id` and filtering the list of importable Documents to match the game system by `DOCUMENT._stats.systemId` would resolve this (based on conversation with Toasty and Arcanist, i think i agree).
You’ll have to add one of those solutions to the module.json, or wait for @kakaroto to figure out a neato solution for it.
wokeye
September 17, 2022, 7:41am
3
Are shared compendia still broken in V10 in Forge (or generally)? Considering upgrading, but this is a showstopper.
Shared compendiums (and compendium in any module that doesn’t lock it to a single system) will still not work in v10. This is an issue with Foundry v10 locking things down, and we’re going to have to implement a migrator for users so they don’t lose their content. It will take time to do it, so please be patient. We’re not going to recommend Foundry v10 until we have that solution in place and until we are confident that it is stable and usable by our users. At this time we still do not recommend users upgrade to it.
1 Like
By the way, I wrote some instructions here on how you can manually migrate your shared compendiums until we release our own tool for it :
At this time, The Forge does not yet recommend users upgrade to Foundry VTT v10, due to stability issues and various major changes that are causing problems to users.
While The Forge is working on a user-friendly way to let users find any compendium that would fail to load on v10 due to its stricter requirements , and guide them through fixing it, we acknowledge that some users have already moved to Foundry v10 (either purposefully or accidentally) and find themselves stuck without access to the…
listo
May 1, 2023, 10:38am
6
Any updates on this issue?
phi
May 1, 2023, 3:21pm
7
Heya @listo
Yeah, the migrator tool is available here The Forge