The engine this repo was extracted from originally generated Obsidian-
vault markdown files (campaign trackers, PC sheets, session logs) and
synced them via Nextcloud/WebDAV. That subsystem was intentionally
removed from the core engine — see the "What was intentionally removed"
section of docs/ARCHITECTURE.md — because it was tightly coupled to one
GM's specific note-taking workflow, not a generic engine feature.
If you use Obsidian for campaign notes and want this back, a clean
re-implementation as an optional module (not wired into core state
sync) would be a welcome contribution. Look at git history / the
ARCHITECTURE.md notes for what the original routes looked like
(/obsidian/sync, /obsidian/combat, etc.) as a reference for the
shape of the problem — not to copy verbatim, since that version was
deeply campaign-specific.
The engine this repo was extracted from originally generated Obsidian-
vault markdown files (campaign trackers, PC sheets, session logs) and
synced them via Nextcloud/WebDAV. That subsystem was intentionally
removed from the core engine — see the "What was intentionally removed"
section of docs/ARCHITECTURE.md — because it was tightly coupled to one
GM's specific note-taking workflow, not a generic engine feature.
If you use Obsidian for campaign notes and want this back, a clean
re-implementation as an optional module (not wired into core state
sync) would be a welcome contribution. Look at git history / the
ARCHITECTURE.md notes for what the original routes looked like
(
/obsidian/sync,/obsidian/combat, etc.) as a reference for theshape of the problem — not to copy verbatim, since that version was
deeply campaign-specific.