Local data
- Generated dungeon state is saved as local JSON when you export or persist it.
- Generation profiles and last-used settings are stored locally so your setup can survive a restart.
- Generation runs inside the desktop app, with exported dungeons stored as local files.
Local LLMs
AI-assisted brief suggestions, director interviews, tool actions, and narrative polish are optional. When enabled, the desktop app sends those requests to a model running on your machine — either the app’s bundled llama.cpp runtime or a provider you run yourself, such as Ollama, LM Studio, or llama.cpp.
If you use the bundled runtime, the one-time model download fetches the model file from the internet; generation requests themselves never leave your machine. Inside DOA, director actions use a constrained list of validated tools with narrowly scoped DungeonState permissions.
DFRPG content boundary
The bundled DFRPG data path uses structural data, tags, references, and original templates to support table prep. Published rules text and stat blocks remain in their source books.
You should still use the source books you own at the table. Source-book filtering exists so the generator can stay aligned with your available library.