Closed Gensokian closed 1 year ago
So I tried multiple things:
Reset Languages (Failed) Reset Cobalt Token (failed) Reset Cookies / Browser settings (failed) Different browser - Edge (failed) Different Browser - Firefox (Failed)
what DID work is creating a new world and re-downloading all monsters.... uhoh
This might indicate something odd with that world. maybe from a conflicting module or bad setting. Was this world upgraded from v10? If so it's worth noting that you can't currently update existing things in DDB Importer due to this core foundry bug in v11 https://github.com/foundryvtt/foundryvtt/issues/9552
Yes, this was updated from V10. But it also happens when completely nuking all compendiums that DDB-importer has created and completely fresh-install DDBI, thus re-creating the DDB Compendiums
Also it is not a module conflict, since all modules disabled bring the same issue.
As it can't be replicated in a new world there is not much I can do to attempt to fix your issue.
Alright, thanks anyways
Describe the bug Trying to munch all dnd beyond Monsters will lead to X error messages, and 0 monsters imported. X being however many monsters are found on DNDBeyond
To Reproduce Steps to reproduce the behavior:
Expected behavior The monsters get munched
Screenshots
Environment:
Additional context Any other munch works (example vehicle munch in screenshot above)
Resetting the Compendiums does NOT fix the issue :/
After looking into it for about 10 seconds and giving up, I noticed inside "
ddb-importer/dist/main.js:33344:22
" it searches for thenpcClass
which is defined one line above.const npcClass = await Actor.create({ name, type: "npc" }, options);
Maybe its because somehow my instance noticed my german backend and tries to get the npc part
...{ name, type: "npc" }...
ascha
, for charakter (german)Console Log