DroidCartographer
patreon
Foundry VTT V10 Compatibility
🕑 Added 2022-10-02 13:14:42 +0000 UTCI had fixed errors that prevented my modules from running with Foundry Core V10.
Please note that these are not compatible with older Foundry VTT V9. You can download the latest stable V9 compatible DC modules manually from here:
V9 DC modules
https://www.dropbox.com/sh/v7uwjmxs3raz933/AABMW3Xx21rcgmgIEt3isANPa?dl=0
Although I had tested them, If you have everything in working condition, please backup your local DC modules in case the update breaks anything.
V10 Installation:
There are currently 3 modules to be downloaded the usual way - through feeding Foundry a manifest url (they had not changed, you can click update in Foundry if you had installed them already ).
After you boot up your game world, you would be suggested to import compendiums. Say yes.
If you already have these compendiums in your world, you may manually delete them, and reimport through Configure Settings - DC_Maps_Modular/Starships - DC GM Menu - Force Reimport, then press F5
DC-core manifest URL: https://www.dropbox.com/s/8uvb3o5b8wrbs19/module.json?dl=1
DC-starships manifest URL: https://www.dropbox.com/s/046l3lf46pubxdp/module.json?dl=1
DC-maps-modular manifest URL: https://www.dropbox.com/s/ioezgg62sz8abif/module.json?dl=1
Dependencies : Token Attacher, Levels, Wall-Height. DC-core is required for all the other DC modules.
Comments
Chris Engel
I'm not sure, I can't test further because any time I re-enable the module set the errors resume :( so it's impossible to tell.
DroidCartographer
Got it, will try to recreate the problem and see what causes it. Did it happen only when you opened the locked compendium? There should be other ones, imported into your world, that are not locked. Do they generate similar issue?
Chris Engel
Hey there! There seems to be a bug or something in the modules where if you click to open the character sheet for a map from the compendium viewer it gives infinite errors about not being able to edit because its locked. Have to completely disable the module to get the errors to stop spamming. Edit: It seems that once this bug starts, it never stops. Disabling the module stops the messages but reenabling the module resumes the error spam.
