Importing maps: UVTT, Dungeondraft, Owlbear, Foundry and TaleSpire
Bring a map with its grid, walls, doors and lights from Universal VTT, Owlbear, Foundry or TaleSpire, and export it back to Foundry or the universal format.
A map made in another tool arrives in Roliando with the important parts already in place: the image, the grid, the walls, the doors and the lights. It can be brought into a table's map or into your library, and it can be exported back to Foundry or to the universal format.
Where it is
In the table's map settings, Import and export tab, Import group. Foundry scenes and worlds and Dungeondraft packs can also be imported from the Library (Importing content, Foundry VTT in Roliando: systems, modules and worlds), and Owlbear copies from the Library into My Library.
Requirements and permissions
Whoever runs the table. Importing a map with an image counts against your storage quota, because the images are copied to your private storage (Storage and quotas); the notice says so when they are links.
Formats that come in
| What you bring | Where it comes from | What arrives |
|---|---|---|
| Map with walls (.uvtt, .dd2vtt, Owlbear .ob2) | Dungeondraft, Dungeon Alchemist, DungeonFog and other tools that export Universal VTT; Owlbear Rodeo 2 with its .ob2 copy | Image, grid, walls, doors and lights; from Owlbear, also tokens and drawings |
| Foundry scene (.json and image) | A scene exported from Foundry, with its image | Grid, walls and lights |
| Foundry walls over this map | A Foundry scene onto a map you already have | Only the walls and lights |
| Roliando scene (.json) | A scene exported from Roliando | The whole scene |
| TaleSpire slab | A TaleSpire slab code | The structure, with a top-down photo if there is one |
Step by step
- Open the map settings and go to Import and export.
- Choose the format. A map with walls (.uvtt, .dd2vtt, .df2vtt), an Owlbear backup (.ob2) or a Foundry scene (.json). A new map is created from whatever it holds.
- If the Owlbear file holds several scenes, choose the one to bring (Owlbear scenes). In Owlbear the file comes from the three-dot menu, Manage storage, Export copy.
- For Foundry walls over a finished map, adjust before applying: the Horizontal scale and the Vertical scale, Move the walls and the Map opacity to see the map beneath; then Apply walls and lights.
- For a building with several floors there is Import a building (one file per floor): one file per floor.
- At the end a report shows what had no equivalent, for example Owlbear extensions that were translated into walls, doors and lights, or images that could not be copied and stayed as a link.
Exporting
Export to Universal VTT leaves the map for any table that reads Universal VTT (only maps with an image are exported; the format only defines a square grid); Export to Foundry takes it to Foundry; Export the scene makes a copy of the Roliando scene.
Examples
A Dungeondraft dungeon is exported with "Export as UVTT", imported here and arrives with its walls and doors: dynamic fog works from the first moment. See Fog, vision and light and Walls, doors, portals and cover.
Known limits
- UVTT only describes a square grid: a hex map is exported with the equivalent geometry.
- What Owlbear has and this does not (the notice says how many) is ignored and flagged.
- Dungeondraft packs (
.dungeondraft_pack) bring art, not maps: see Importing content.
Frequent problems
"The walls do not fit the map." Adjust the scale and move the walls before applying them.
"A map with an image is needed." A map with an image is needed: walls are placed over an image and exporting only works with an image.
"That file is not a JSON." A Foundry scene is exported as .json; check the extension.
See also
Building the map at the table, Walls, doors, portals and cover, Foundry VTT in Roliando: systems, modules and worlds, Importing content.