# Obsidian - Foundry v11 Export Adventures to Markdown ![[images/Obsidian-Foundry-v11-Export-Adventures-to-Markdown.webp]] [Watch on YouTube](https://www.youtube.com/watch?v=NfK_EZSZ5YM) · 20:35 · Josh Plunkett · 2023-08-27 > Written from the video's full English captions (en-orig automatic captions via yt-dlp), with chapter times from the description. Supporting tutorials and community links live on [obsidianttrpgtutorials.com](https://obsidianttrpgtutorials.com). ## Outline ### 00:00 Intro - Welcome back to Obsidian for tabletop RPGs. Tonight is another look at getting **Foundry VTT** journal content into Obsidian. - Regular viewers saw his earlier video moving **D&D Beyond** / **Paizo** content through Foundry **v10**. Almost immediately, **Foundry v11** shipped, changed the data structure, and **broke** that plugin workflow. - He held off updating Foundry until now. **Farling** (developer of the original plugin) has released an updated path: a Foundry-side module called **Markdown Exporter**. This video walks the new process end to end. ### 00:34 Find Content - Source example: Paizo content for **Pathfinder 2e** (he is moving toward PF2e play). The same idea applies to anything you can get into a Foundry **Journal** — PDF importers, D&D Beyond→Foundry modules, etc. - He already owns **Abomination Vaults** in Foundry and will use that tonight. Other options: download PDFs (there used to be a Foundry PDF-import module; he is unsure if it still works) or D&D Beyond users' Foundry import modules. - Homework for the viewer: get your purchased content into Foundry Journals first. He will not cover that acquisition step tonight. ### 01:26 Foundry Config - He has updated to **Foundry Virtual Tabletop v11**. The new launch screen has three areas: **Game Worlds**, **Game Systems**, and **Add-on Modules**. - Creates a world **PF2e via version 11**, picks the Pathfinder Second Edition system, and notes you should install the game system before reading it into a world. - Add-on modules he already runs are sparse (he mostly uses Foundry as a shell / TV tabletop): **Fog Manager**, **Hide Player UI**, etc. For tonight he needs **Markdown Exporter**. - Install Module → search **Markdown** → **Markdown Exporter** by **Farling** (GitHub `farling42/fvtt-export-markdown`). Install; it may pull **libWrapper** as a prerequisite. Green status = up to date / tested. - Back to Game Worlds → **Play** on the PF2e v11 world → join as Game Master (no passwords; this world is a conversion shell, not a live table). ![[images/Obsidian-Foundry-v11-Export-Adventures-to-Markdown-t0350.webp]] *Foundry Install Module search for "Markdown": Markdown Exporter by Farling (v0.2.2) shows Installed, with GitHub link farling42/fvtt-export-markdown.* - Cog → **Manage Modules**: tick **Markdown Exporter** and **libWrapper**, Save Module Settings, reload when prompted. (He also has Battlezoo Bestiary content purchased; ignore that for the export walkthrough.) ### 05:52 Import Content to Foundry - Manage Modules again → enable **Pathfinder 2e: Abomination Vaults** → Save → the pack offers an **Import** action that creates the adventure journals inside the world. - After import finishes, he browses **Compendium packs** (he is still relatively new to Foundry beyond this shell use) and opens the **Journal** sidebar. Folders such as **Adventure Toolbox**, locations, and a **Getting Started** note are present — that is what will export. - Export is "super easy": Journal sidebar → right-click the **Abomination Vaults** folder → **Export to Markdown** (only appears with the module enabled) → save the resulting ZIP to Downloads (he appends `_new` to the filename). ![[images/Obsidian-Foundry-v11-Export-Adventures-to-Markdown-t0840.webp]] *Journal sidebar on Abomination Vaults: right-click context menu with Export to Markdown highlighted over the Gauntlight village art.* - Unzip / copy into his Obsidian vault under a test folder (**Abom Import 3** inside a PF2e vault). The ZIP contains (1) a folder of **`.md` notes** and (2) an **assets** folder of pictures referenced by those notes. - Placement tip: for adventures he keeps assets **with** the module so the whole pack can be moved later; alternatively dump images into a global attachments folder. - Reload Obsidian (Command palette → Restart/Reload) after bulk-dropping hundreds of notes — Obsidian will not reliably index a large paste until restart. Wait for indexing to finish. ### 11:25 Review Import - Inside **Abom Import 3**: assets folder (system pictures) plus the adventure tree. Opens **Getting Started**: pictures render, YAML/properties look sane, and internal links resolve. ![[images/Obsidian-Foundry-v11-Export-Adventures-to-Markdown-t1145.webp]] *Obsidian vault PF2E NEW after import: Getting Started note with wiki-links, Abom Import 3 folder tree, and Initiative Tracker / Encounter sidebar on the right.* - Spot-checks Adventure Toolbox / campaign background / credits / chapter notes. Most content is "pretty clean," but he hits a **broken table** (markdown pipes / templating did not migrate cleanly). - Table fix options (do not overthink the markdown): 1. Open the same content in **Foundry**, copy the table, paste into Obsidian. 2. If you have **Demiplane** content, copy the table from Demiplane — paste also works. - He would **not** run the adventure in the raw imported tree. Next steps are prep/massage: - Use **Demiplane** (books & bundles → Abomination Vaults: Player's Guide, Ruins of Gauntlight, Hands of the Devil, Eyes of the Empty Death) as a left-pane outline. Mirror that structure into Obsidian folders (Campaign Overview, Otari, Players Guide, books 1–3) instead of deep nested Abomination Vaults layers. - He has already reworked the same content into folder notes with chapter linking; raw import is only the on-ramp. ![[images/Obsidian-Foundry-v11-Export-Adventures-to-Markdown-t1550.webp]] *Post-massage Abomination Vaults vault: Adventures folder with 0 Campaign Overview / Otari / Players Guide and books 1–3, plus a chapter TOC callout panel.* - Visual polish: resize images; use a theme/CSS snippet (he mentions a "skull" / image-on-the-right style) so art takes less horizontal space. - Leftover Foundry tokens: e.g. room **A01. Damp Entrance** still shows `@Actor[…]{Mitflits (3)}` instead of a usable encounter. Cross-check the source callout ("Mitflits ×3"), then insert a **Fantasy Statblocks** / encounter block and delete the raw actor stub. Same idea for initiative trackers so the note is table-ready. ![[images/Obsidian-Foundry-v11-Export-Adventures-to-Markdown-t1748.webp]] *A01. Damp Entrance after prep: leftover @Actor Mitflits token beside art, EXAMPLE encounter callout with party vs 3 Mitflits, Encounter sidebar active.* ### 18:25 Outro - End-to-end: anything in a Foundry **Journal** can go through Markdown Exporter into Obsidian. It does **not** export items, actors, or scenes — purchased creature packs need a different (future) video. - Process is quick; shout-out to **Farling** for fixing issues he raised while filming and for building the "advanced data tools" that make bulk import practical. Tip coffee money his way if you can. - Share cool Journal-exportable packs on the community Discord; thanks to Patreon supporters; like/subscribe; see you on the socials. ## Things mentioned ### Obsidian plugins, themes and features - Obsidian core vault reload / Command palette Restart after bulk note drops (**free**) - **Fantasy Statblocks** (and encounter/initiative callouts) used when replacing leftover Foundry `@Actor` stubs during prep (**free** community plugin) - Initiative Tracker / Encounter Builder sidebar visible in his PF2e vault during review (**free** / community) - Theme + CSS snippet for pinning adventure art to the right ("skull" style) to reclaim screen space (**free** / vault CSS) - Folder notes and chapter TOC callouts in his restructured Abomination Vaults layout ### Foundry VTT modules and tools - **Foundry Virtual Tabletop v11** (paid VTT license; v11 broke the prior Obsidian export path) - **Markdown Exporter** by **Farling** (`farling42/fvtt-export-markdown`): Journal sidebar → Export to Markdown → ZIP of `.md` + assets (**free** Foundry module) - **libWrapper**: prerequisite pulled in with Markdown Exporter (**free**) - Other modules visible in his world (not required for export): Fog Manager, Hide Player UI, Battlezoo Bestiary, PDF to Foundry Importer, etc. - Pathfinder 2e system + **Abomination Vaults** premium adventure pack (Paizo / Foundry store — **paid** content) ### Websites, tools and guides - [Obsidian](https://obsidian.md/) (**free** core app) - [obsidianttrpgtutorials.com](https://obsidianttrpgtutorials.com) — tutorials and community links (**free**) - [Demiplane](https://demiplane.com/) Pathfinder / Abomination Vaults digital books (beta at filming; **paid** / subscription for owned titles) used as structuring reference and alternate table copy source - [Paizo](https://paizo.com/) Pathfinder 2e storefront for modules (**paid**) - Farling GitHub module page (linked from Foundry Install Module UI) (**free**) - Josh's **Patreon** (**paid**, optional) - Obsidian Keep TTRPG Community Discord via his site (**free**) ### TTRPG systems and content - **Pathfinder 2e** — Abomination Vaults (Ruins of Gauntlight, Hands of the Devil, Eyes of the Empty Death), Otari, Player's Guide, Adventure Toolbox - Sample room **A01. Damp Entrance** with **Mitflits ×3** (LOW 1) encounter cleanup - Prior pipeline also mentioned: **D&D Beyond** content via Foundry (v10-era video); journals-only limitation still applies - Battlezoo Bestiary content noted as purchased but out of scope for Journal export ### Free vs paid (quick) - Free: Obsidian core, Markdown Exporter, libWrapper, Fantasy Statblocks / encounter tooling, his tutorial site and Discord - Paid / licensed: Foundry VTT, Paizo/Foundry adventure modules (Abomination Vaults), Demiplane owned titles, optional Patreon ## Bios - **Josh Plunkett**: Australian GM and educator behind Obsidian TTRPG Tutorials (YouTube and obsidianttrpgtutorials.com). Here he treats Foundry mainly as an import shell to land purchased PF2e journals into Obsidian, then massages structure and encounters for table use. - **Farling**: Foundry module author of **Markdown Exporter** (and the earlier export tooling this video replaces). Josh calls out his quick bugfixes and recommends tipping him for the data tools that make bulk Journal→Markdown practical.