Foundry VTT in Roliando

Bring your Foundry world (scenes with walls, lights and regions, characters and journals) and install its systems and modules to play them at the table with no server; versions v9 to v14.

If you come from Foundry VTT, you don't start from scratch. Roliando brings in what you already have in two ways:

• Your world: scenes with their walls, doors, lights and regions, your non-player characters and your journals, from a single .zip.
• Its systems and modules: install a Foundry system's .zip and play it on the Roliando table with its own sheet and rules, without Foundry or a server.

Roliando is an independent project, not affiliated with Foundry Gaming LLC; "Foundry VTT" is named only to indicate compatibility.

Where everything is

In My Library, under the Foundry VTT group, each thing has its own section with its upload button and its explanation:

If you upload a module in the systems section (or the other way round), it is installed anyway and you are told where it went. The old shortcut, Scenes → Import from Foundry, still works for everything.

Bring your world

In My Library → Foundry worlds → Import a world. Upload a .zip and the wizard recognises what it is:

What arrives

• Scenes, with their folder tree: background (image or video), square or hex grid, walls (doors, secret doors, locked doors, windows, curtains, cover), lights, tiles, drawings, notes, ambient sounds and tokens.
• Regions: they come in as event zones; teleports, as portals. Whatever can't be translated comes in switched off, with a report of what's missing, so nothing fires on its own before you have reviewed it.
• Levels: floors from Levels or v14 are split into levels of the same map.
• Non-player characters (D&D 5e): into My Library → NPCs with their stat block, and the map tokens linked to them, as playable creatures. When you bring the scene into a campaign, each token is linked to its NPC there: if it wasn't yet, it comes from your library (or is created from its stat block), one per creature even with twenty goblins. A token left unlinked can be linked by hand with right click → Link to an NPC….
• Characters (D&D 5e): into Roliando sheets, resolved against the compendium.
• Journals: one Document in My Library per journal, with its folders and editable. Its links (@UUID[…]) become wiki links: to another journal, one of its pages or an NPC. When used in a campaign they go into its World, in the same folders, and the links open the linked entry. Map notes pointing to a journal carry its name and open that Document from the note reader.

Playlists, tables and loose world items are not imported.

Just part of the world

You don't have to bring everything: in the wizard you pick which scenes, NPCs and characters, one by one or by folder, and anything left unticked is not imported. For a single scene there is also the map shortcut (below).

A single scene, from the map

On the combat map, Bring from outside has two shortcuts:

• Foundry or Dungeon Alchemist (.json + image): one scene with its image or video. From Dungeon Alchemist, with all its levels at once.
• Only the walls from Foundry: lays the walls and lights over the map you already have.

And back again

A Roliando scene can go to Foundry with Export to Foundry, or to any table that reads the universal format with Export UVTT (.dd2vtt).

Install Foundry systems and modules

In My Library → Foundry systems (or Foundry modules), drop the .zip of the system or module (the one with its system.json or module.json) and press Install. The .zip comes from your Foundry: the whole Data/systems/<system> or Data/modules/<module> folder, zipped.

Loose macros, tables and items

In Foundry, right-click a macro, a table or an item → Export Data saves a .json. In My Library → Macros, Tables or Items, Import from Foundry (.json) brings them in (one or several at once), each to its own section. Macros come in Foundry mode; tables with their ranges and die. The table's macro panel accepts that .json too.

Removing a package

The bin icon on each row removes it from your library. If any campaign uses it (as its system or with the module), it cannot be removed and you are told which ones: change their system or turn the module off first.

New versions

A new version of a system is uploaded the same way and installed next to the old one: your campaigns keep theirs, untouched. In each campaign's settings (Foundry system: modules and rules) you get Switch the campaign to vX when another version is installed. Sheets are kept, and the previous version stays installed in case you want to go back.

• An installed system shows up when creating a campaign and a sheet, and in My Library under Foundry systems, with Create sheet. Its players use the system's own sheet (or Roliando's, if they prefer) and the system itself makes the rolls.
• Modules are switched on and off per campaign in its settings, under Foundry system: modules and rules. Their settings, menus and windows open as in Foundry, and their macros go to the bar.
• The system's compendiums open at the table and drag onto the sheet. A compendium journal (rules, lore) is copied to the campaign's World from the GM Screen → search → the entry → Copy to World: editable and with its links to the other journals.
• The sheet can be exported as Foundry JSON.

What you install is yours: only you and the campaigns where you use it can see it.

Who can

Any account can install Foundry systems and modules. A free account gets one system (with as many modules as you like, and its new versions); with Legend GM, as many as you want. Playing in a campaign that already has them asks for nothing: your players join for free.

Which versions

Packages from Foundry v9 to v14 are read. Compatibility is built on v13 and v14; with an older package, Roliando warns you when installing. The reference system, tested end to end at the table, is Pathfinder Second Edition (pf2e), with its character builder guided by its real rules.

Known limits

• Modules work in Foundry-system campaigns; not yet on native D&D campaigns or your own system.
• What a module adds to Foundry's interface (its sidebar, the tracker, the HUD) doesn't show yet.
• Not every system and module is tested: if one fails, tell us in the community.

Common problems

• I don't see "Install". The .zip must have its system.json or module.json at the root, and and, on a free account, you must not have another system installed already.
• A region from my world does nothing. It came in switched off because it couldn't be fully translated: open it as an event zone, check the report and switch it on.
• A scene is missing images. If the scene pointed to images outside the .zip, upload them or export the world with its files.
• My system builds its compendiums on startup. Are they saved? Yes, like a Foundry world. Compendiums the system creates while playing (with createCompendium and Item.create(…, { pack })) and the items it leaves loose in the world are saved with the campaign when the GM's table creates them, and next time they are already there before the system starts: a system that checks if (!game.packs.get(…)) won't rebuild them. Your players see them even if the system only creates them for the GM (game.user.isGM), and if the GM changes them while the table is open, they get the update on their own. They show up in the sheet's Compendiums and in its sheet catalog; loose items, as World items. On a sheet with no campaign, the world is yours: it is saved for your loose sheets of that system. Two things to know:
• If the system creates them every time without checking whether they exist, they don't pile up: while the table starts, whatever it creates identical to what was saved (same type, name and content) stays as one, and if it empties its compendium and rebuilds it the same way, its items keep their old ids (links to them keep working). Opening the table with no changes saves nothing. After startup, if you create two identical items on purpose, both are saved. Whatever the system rebuilds differently (a new version with other text) is added to the old one: delete it by hand if you don't need it.
• There is a 3 MB limit per world; past it, the table warns you and nothing is saved. For large content (and a faster table start), declaring them under packs in system.json with their content inside the .zip is still the best option.
• How do I change a character's image? Click its portrait on the system's sheet, as in Foundry: Roliando's image picker opens (upload, crop). You can also do it from the Roliando sheet (hover the portrait → Image): both sheets show the same one.

All Roliando guides