Questions

No, and it is not going to become one. There are no tokens, no grid, no initiative order and no dice roller at the centre of it. Keep whatever you already use for the battle map.

LeagueKit is the thing beside it: the wiki, the secrets, the money and the calendar. Those four are what a long campaign actually accumulates, and they are the four every virtual tabletop treats as an afterthought.

Any of them, because it does not model one. You define what fields an entity type carries, so a setting built on houses and holdings is not forced through a schema built for classes and levels.

The one place a system shows up is the 5e material that ships with it: a starter pack of SRD 5.2.1 tables and a character sheet template drawn from the same SRD, both bundled at build time from Open5e under its CC BY licence, and a rulebook where you add what your own table plays with. Nothing fetches from another service on your behalf. If you play something else, that is simply material you do not use.

They need one magic link each. No password to invent, no app to install, nothing to pay for. A player who never opens it costs you nothing and blocks nothing.

That is the design, and it is not built yet. The intent is that the copy you are entitled to sits on your device, so Table Mode opens without a network round trip.

There is a real consequence to that, and it belongs in the answer rather than in a document nobody reads: a device that is offline keeps the copy it already had. If a secret is withdrawn while a player's phone is in a basement, that phone still holds it until it reconnects.

Yes, and the phone is a different design rather than a narrower version of the desktop one. The rail becomes the bezel, the sheet comes up from the bottom, and sealed prose collapses to its tag so a person leaning over your shoulder does not read it.

In the database, by row level security, before anything is serialised. Concealed nodes are stripped out and the surrounding text is merged server side, so what reaches a player's browser does not contain the secret in any form.

This is worth asking about because the common implementation is the other one: send everything, hide it with CSS or a component check, and hope nobody opens the network tab. If a player's browser can fetch it, it has leaked, whatever the interface shows.

Yes. That is the point of the whole layer. Reveals are per member, not per role, so the player who bribed the harbourmaster gets a different encyclopedia from the other four.

No. There is no lock icon, no greyed out block, no "unavailable" placeholder and no count of things they cannot see. A placeholder tells a player a secret exists at that spot, which is most of the secret.

The trade-off is that removing a mention can leave a sentence reading oddly. The answer to that is an authoring-time warning, so you are told while you write, not a player discovering a gap while they read.

You can withdraw it, and the withdrawal is recorded permanently and visibly, struck through. It is deliberately a little ugly, because you cannot make somebody un-know a thing and an interface that pretends otherwise is lying to the person who mis-tapped.

Export is a commitment, not a paid feature, and it is on the free plan. The format is designed to be readable without us.

It is built. From the campaign's settings page the person running it downloads the whole campaign as Markdown or as versioned JSON. The entries a DM adds to the campaign rulebook are not in that bundle yet, and that is said here rather than discovered.

No. Not on your notes, not on your world, not on anything a player wrote. There is no generated lore feature and none is planned.

Postgres, on Supabase, in Frankfurt. The region is named on the privacy page, and the sub-processor list is published and kept current.

They stop being able to read the campaign immediately. Their own private notes are theirs and go with them; what they contributed to the shared Record stays, because a campaign that loses two years of session notes when somebody moves house is not a record of anything.

A player can ask for their account and their notes to be deleted outright, and that is a request the product must honour rather than a setting it may offer.

Whoever runs the game, and only them. Players are free permanently, with no seat count and no feature difference, and there is no upgrade prompt anywhere in a player's view.

No. There is no payment processor connected to this product, no card field anywhere in it, and no account to attach a subscription to. The amounts on the pricing page are indicative and labelled as such.

The campaign goes read only and stays exportable. Nothing is deleted because an invoice failed. Deleting a person's campaign notes over a lapsed card is not a business model, it is a hostage situation.

Yes, if you have been invited. Two campaigns are live in a private test, and a seat arrives as a link from the person running your game. Opening it and signing in by magic link is the whole process: no password, nothing to install.

There is no sign-up from this site. The feature list marks every line with whether it has been checked against the live database or only written and reviewed, and a line only moves to RUNNING on the day that check was actually made.

No date, deliberately. It is being built for two real tables first and tested there honestly. A date published now would be a guess presented as a plan.

The changelog is public and dated, which is the honest version of the same information.

Not today, and no decision has been announced. If that changes it will appear in the changelog rather than in a paragraph here that quietly changes meaning.

Same name and same domain, no shared code. That earlier product is a separate codebase, and nothing from it is used here.

LeagueKit is a campaign platform for tabletop role-playing games: a wiki, a reveal engine, a ledger and the logistics of a long campaign, for the person running it. It is not League of Legends tooling, and it has nothing to do with the sports league product that used to sit on this domain beyond the name and the address.