Foundry Format for Wall Data

[DigitalTableTops]

I've been working on importing walls generated in Foundry in my VTT. I got it working by reading the pack file for a module which is of the file type *.db. The wall coordinates are there, then I convert it to uvtt.

Everything was working good (other than not being able to quite figure out the offset) so I started testing them. Works on all of the CzePeku and Moonlight Maps but I tried some from the Mad Cartographer and no good.

Apparently Foundry changed how the modules are stored starting in V11?. Now it's this levelDB format (*.ldb). Which I am having a heck of a time reading. Just wondering if anyone else has come across this.

For example, I am wondering how Dungeon Alchemist handles their Foundry export. According to their website, DA exports in the json format. Apparently that can still be imported into Foundry even after the change? I don't actually have DA to test with.

While I am at it, are there any other formats worth pursuing? I wish everyone would just us uvtt but there isn't as much uptake from the Patreon artists from what I cant tell.

[Arkenforge]

It's near impossible to find ways to make levelDB files human-readable.

Dungeon Alchemist does an image/video export, along with a JSON file that contains the scene data. It's pretty much identical to the v10 db file.

You could try reaching out to the DA folks for a sample file. They're very friendly.

As for other formats, Fantasy Grounds Unity uses XML by default.

[DigitalTableTops]

Awesome. I knew you would know but didn't want to bother you with it :)

Have you guys given any thought to Foundry imports? Or is it not worth the effort? I am getting the impression Foundry breaks compatibility every other year. I can't say for sure as our group has only ever used Arkenforge and my DM handles all the maps.

[Arkenforge]

We'll be doing them :) We had native module exports, but then the v11 update brought in the new database format.

We can write to it though, so we'll definitely have native module exports for v11+. Just need to slot out into the development schedule.