[Foundry P3] Additional system adapters (after real-instance testing) #15

New issue

Open

opened 2026-06-23 00:42:37 +00:00 by rbrooks · 0 comments

rbrooks commented

2026-06-23 00:42:37 +00:00

Owner

Phase 3 - only after the systems can be tested against a real Foundry instance.

Scope

Add adapters for additional systems as campaigns using them become active: Ryuutama, Honey Heist, Discworld RPG.
These likely differ significantly from PF2e - implement only after actually playing/testing against a live Foundry world.

Boundary reminder

Each system is wired in on its own terms behind the adapter interface; no shared-code changes, no system branches in routes/model.

Roadmap: Phase 3 step 13.

> Phase 3 - only after the systems can be tested against a real Foundry instance. ## Scope - Add adapters for additional systems as campaigns using them become active: **Ryuutama, Honey Heist, Discworld RPG**. - These likely differ significantly from PF2e - implement only after actually playing/testing against a live Foundry world. ## Boundary reminder - Each system is wired in on its own terms behind the adapter interface; no shared-code changes, no system branches in routes/model. _Roadmap: Phase 3 step 13._

rbrooks added this to the v4.3.0 - FoundryVTT Phase 3: Lore Sync & Deeper Pulls milestone

2026-06-23 00:42:37 +00:00

rbrooks added the

backend

enhancement

labels

2026-06-23 00:42:37 +00:00

rbrooks referenced this issue

2026-06-24 04:21:51 +00:00

[Foundry] Bidirectional integration — architecture & design reference #24