Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

v1.1.2 is live! Let me know if that fixes your issues.

(1 edit)

Is there an option to select when exporting the JSON to change between 2.0.3 and 2.1.5? I'm still getting an Uncaught (in promise) Error: undefined. Actor5e Model Validation Errors when importing into 2.1.5.

  • Bug description: Upon import of exported file into FoundryVTT v10.291 with dnd5e system version 2.1.5, getting an Uncaught (in promise) Error: undefined. Actor5e Model Validation Errors.

Are you getting those errors after trying to import an actor? I can't reproduce it in my test world.
Can you create an empty world without modules for me and import the character in there? It might be a module issue, but I'm not sure at this point. I'll do some more testing.

(1 edit)

Similar error, as far as I can tell. Log is error @ pastebin.com. Has just the dnd5e version 2.1.5 game module enabled, nothing else, on a freshly created world.

I created a new world as well and I'm now able to reproduce the errors. Seems like the dnd5e system does something to new worlds that causes this. I'll look into it and do some more extensive testing. Once I've found a solution, I'll let you know and create a new release with a fix.

Cheers for that.

A quick update: I found the issue. 

The new version of the dnd5e system hasn't changed its format as far as I can tell, but it does a TON of checks now for missing and empty values which it didn't care about before. This means a lot of changes under the hood of the converter for just about all conversion stages.

I'll have to implement the fix in a few stages:

  1. Add lots of empty strings and null values all over the place as placeholders until the import in Foundry works for a single character.
  2. Create 10+ characters and test if the import works correctly while finetuning and rewriting parts of the converter

As this touches upon most of the converter code, it will take me a while to get the converter to a semi-stable state again and I have a feeling it will introduce some bugs here and there. I'll create a post to warn people not to update to 2.1.5 for now.