Deploy deepseek 2
Some checks failed
Test / test (push) Failing after 2s
Build and Deploy Nuxt / build (push) Successful in 1m51s

This commit is contained in:
2026-10-19 19:04:28 +02:00
parent b5d5e570d5
commit 1ec29121e1
45 changed files with 3438 additions and 166 deletions

View File

@@ -15,9 +15,15 @@ Character and item sync works without the bridge.
## Installing the module
Foundry VTT v12 to v14. Copy the `dragonroll-foundry` folder into
`{Foundry user data}/Data/modules/dragonroll-foundry/`, restart Foundry, and enable **Dragonroll
Foundry API** in the world's module settings.
Foundry VTT v12 to v14. In Foundry's **Setup → Add-on Modules → Install Module**, paste the
manifest URL `https://dragonroll.aranroig.com/foundry/module.json`. Foundry downloads the module
from your Dragonroll server, and the same URL later tells it when an update is available.
A self-hosted Dragonroll serves its own manifest at `https://<your-dragonroll-host>/foundry/module.json`.
Then enable **Dragonroll Foundry API** in the world's module settings. To install by hand instead,
copy the `dragonroll-foundry` folder into `{Foundry user data}/Data/modules/dragonroll-foundry/`
and restart Foundry.
The module's own settings hold two things you set: the **Dragonroll Endpoint** — the address of your
Dragonroll server, `https://dragonroll.aranroig.com` by default — and **Dragonroll Auto-sync**, which
@@ -52,7 +58,7 @@ Worth knowing:
| The folders grouping that item directory | Item folders with the same names and nesting |
| A folder's colour | The campaign's folder colour — and the other way round, what you colour in Dragonroll lands on the world's folder |
| The world's **scenes** | The campaign's maps: the scene's background picture and the grid laid over it, in the scene's own cell size |
| A journal called **Dragonroll** — one page per note | Your campaign's notes. They arrive **from** Dragonroll: what you write in the journal does not go back |
| A journal per note folder, named after its path — one page per note | Your campaign's notes. They arrive **from** Dragonroll: what you write in a journal does not go back |
The item list is the world's item directory and nothing else. The gear a character carries is that
character's inventory: it travels with the character and stays on its sheet, so a sword a fighter owns
@@ -78,11 +84,20 @@ few seconds. A **full** snapshot — the one taken when the world links, or forc
directory — is the only thing that prunes: it is the only moment either side can see the whole list and
notice what is gone. Live edits never delete anything.
Notes are the exception that runs one way, because notes are written in Dragonroll: every note stands
as a page of a single journal called **Dragonroll**. A note you make or edit in the app appears on that
journal within a few seconds, and deleting one takes its page with it. Pages the campaign does not own
— one the GM made in that journal themselves — are left alone, and nothing written in the journal
travels back to the campaign.
Notes are the exception that runs one way, because notes are written in Dragonroll: each folder
stands as a journal named after its path. Notes in the root of the campaign share the journal called
**Dragonroll**, while notes in a folder called *Sessions* with a subfolder *Arc 1* share the journal
**Sessions / Arc 1**; every note is a page of the journal of its folder. A note's dice widgets are
buttons there as well: press one in the journal and Foundry rolls it and posts the result to chat, so
advantage and disadvantage roll the way the campaign's notes describe them. The note's `[[links]]`
work in the page too: a link to a note page, a character, an item or a scene opens it in Foundry, and
`![[a character or item]]` is drawn as a sheet preview inside the page. Renaming a folder renames
its journal, and moving a note to another folder moves its page along. The module only pulls the notes
over when something has changed, checking every fifteen seconds, so a note you make, edit or move in
the app appears in its journal within that time, and deleting one takes its page with it. Pages the
campaign does not own — ones the GM made in those journals themselves — are left alone, and nothing
written in a journal travels back to the campaign. A folder journal whose notes have all left is
removed too, unless the GM keeps pages of their own in it.
## Auto-sync, and sending one actor on purpose