Asked and answered

Yes. The engine, the database and any rulebook you ingest live in your local data directory. The engine binds to loopback only, so it is not reachable from your network. The only traffic is to the model endpoint you chose, and that can be a local one. The privacy page has the full picture.

No. Run a local model for free, bring any API key you already have, or wait for the hosted tier. Measured on the recommended hosted-class model, a 200-turn session is about eight cents of inference, so five dollars with a provider is many long evenings.

Not with dice. Rolls are parsed, seeded and executed by the engine, and every result is logged with its full breakdown. The model narrates the consequences. It never touches a die, and a narrated dice ask in prose triggers a rescue that gives you a real tray instead.

LOOM Engine ships the System Reference Document 5.1 under its Creative Commons Attribution 4.0 licence, with the attribution shown in the app and on the systems page. Every built-in system is open licensed the same way, and each licence was verified against the publisher's own page on a recorded date.

No, and it never will be. An ingested book is your own copy, processed into your private data directory, and nothing is redistributed or mixed into the shipped rulesets. One honest nuance: with the engine's reading pass on (the default), pages of your book are sent once to the model endpoint you configured so it can propose the system. Switch the pass off and the book is read entirely on your machine. The privacy page has the detail.

A desktop on Windows, macOS or Linux. The client is a Godot 4 application and the engine is a Python service that runs beside it on your machine. A local model needs a machine that can run one; a hosted model needs only a key. Voice runs on the CPU you already have.

No. LOOM Engine is a game for one player and one DM today. Shared tables are an idea in the project's notes, not a plan, and any hosted version of one would be gated only by what it costs to run.

Yes. Exports are plain Markdown: the full transcript, chapter summaries, or a player-facing journal. The database is ordinary SQLite. To delete a campaign, delete it in the app or delete the file.

The table does. The engine, the client, the dice, the memory and the speech all run locally, so a campaign plays with no network at all on a local model. A hosted model is the one thing that needs a connection, by definition.

Six personas today, from Warm Storyteller to Chill Robot, any of them behind any face. Speech is local: the DM's narration streams to audio as it is written, first audio about a second in, and a cloning studio is built in so a DM can sound like a voice you recorded. Speech input is designed but not built, and the roadmap says so.

The weaver's reading: worlds as threads you set the pattern for. The engine holds the warp, the model tells the story across it, and the dice decide where the pattern knots.

The engine and client are proprietary, developed by SILO Apps LLC. The site never promised otherwise. What is open is the ruleset layer the game stands on: every shipped system is an open-licensed package with its attribution shown in the game, and your campaigns export to plain Markdown and SQLite, so nothing you make is ever locked in.

Not yet, and this site will not pretend otherwise. The game is pre-release: a plain-folder Windows build is already travelling between private playtesters, and signed installers for Windows, macOS and Linux are on the plan. The day there is a public download, it will be on the front page. A Kickstarter to fund the remaining art and audio is being prepared; it is not live, and the day it is, this site will say so.