How ShawnsVTTs is built, and where AI is and is not used
Last updated: 2026-10-09
The short version
We use an AI coding assistant to help write the code for our Foundry modules and our ShawnsVTTs. We decide what gets built, we review what it writes, and we are the ones who answer for it. Nothing AI-made runs inside your game, and none of our products has an AI feature of its own. The Foundry modules go further: the modules themselves make no requests to any server while you play and send nothing anywhere. Shawn has over 30 years as a software developer and applies that knowledge to everything that is built with our AI coding tool.
No AI runs in your game
For every ShawnsVTTs product:
- Nothing ships an AI model, an AI service or a hidden AI switch. There is nothing in a game to turn off. The one place an AI assistant can touch a game is the optional API described below, and it stays off until a game's owner switches it on.
- Your game content is never used to train, tune or test an AI model, and we do not hand it to an AI company for that. The Terms of Service say so, and this page repeats it.
For the Foundry modules:
- They make no network requests.
- They collect no analytics or telemetry.
- Fonts are bundled inside the module. Nothing is loaded from another company's server.
- What a table creates, such as messages, notes, photos and settings, is saved in your own Foundry world on your own server. ShawnsVTTs never receives it.
The one time anything contacts our servers is when Foundry downloads a paid module through your install link. That is a file download, and the Privacy Policy lists what the download record keeps.
For the web tabletops:
- They are hosted services, so your game content lives on our servers. The Privacy Policy lists every provider that touches your data. No AI provider is among them.
- The marketing site uses Google Analytics for visit counts. The tabletops do not run AI on anything you create.
- A game's owner (a user of one of the VTTs) can switch on an optional API for one of their games and connect their own tools to it, including an AI assistant, so those tools can read and run the game from outside. That is the owner's choice, it runs on the owner's account, and it is off until the owner turns it on.
How the modules are built
Here is the actual process. It applies to everything ShawnsVTTs produces: the tabletops, the Foundry modules and the shared packages.
- We write down what a feature should do before any code exists. Plans live in the repository next to the code.
- Claude writes code in a separate branch. Each feature gets its own branch and its own pull request, and nothing goes straight to the main line.
- Tests come first. We require a failing unit test that describes the behaviour before the code that satisfies it exists. A change that arrives with a test that never failed is rejected.
- Every change is reviewed before it merges.
- We merge. Releases are manual and each one is a decision we make, never an automatic push.
- Anything that touches the database is written as a file and applied by us by hand. The assistant is not allowed to run it.
- For anything with a screen, we check the real thing in a real browser, not only the tests.
What every change has to pass
| Check | What it is |
|---|---|
| Automated tests | Counted on 2026-10-09: Stars Without Number 3,327; Old-School Essentials 1,115; Derelict 1,550; Wyrmfall 5,830; GrimDelve 649; Cyberpunk 8,411; the Foundry Phone 290; the Foundry Library 303. They run on every change. |
| Type checking | TypeScript checks each whole project, and a failure blocks the change. |
| Copy rules | Automated checks on the site's text catch banned words, punctuation, and any potential license violations. |
| Guard tests | Tests that fail if a removed thing comes back or a promise is broken, such as the Foundry modules making a network request. |
| Live testing | We use a combination of Playwright and Chrome DevTools to capture screenshots and run automated tests, and we also run manual tests on all features. |
| Database changes | Written as files and applied by us by hand, never by the assistant, with a check that reports its own result. |
| Release gate | Every release is manual. A published Foundry module version is immutable, so a fix means a new version. |
Screenshots and artwork
- All screenshots are taken of our product - not generated by AI
- Fonts in the Foundry modules are open source under the SIL Open Font License, and each font's licence and copyright notice ship inside the module.
- We don't ship any of our VTTs or Phone with artwork derived from AI.
- Game rules and content come from the games' publishers, under each publisher's own licence. We do not use AI to invent rules, and no tabletop generates game content with AI while you play. The terms differ by game:
- Stars Without Number: the rules text, class names and world-tag tables belong to Sine Nomine Publishing and are used under the publisher's stated permissions for third-party compatible material. The tabletop is a fan product and is not affiliated with or endorsed by Sine Nomine.
- Old-School Essentials: mechanical numbers and tables are bundled as they are. Spell and monster descriptions are Open Game Content under the OGL and are bundled word for word.
- Shadowdark and the other OSR games in GrimDelve: published under the Shadowdark RPG Third-Party License, and not affiliated with The Arcane Library.
- 5th Edition (Wyrmfall): built on the 5e System Reference Document under the CC-BY-4.0 licence, with the attribution notice on screen. Anything outside the SRD, such as named settings and monsters that are not in it, is not included.
- d100 sci-fi horror (Derelict): a generic sci-fi horror tabletop. Mechanical numbers only, and no publisher artwork, monster prose or setting text.
- Cyberpunk: free and unlimited for everyone, published within the rights holder's rules for fan content.
Why we work this way
Shawn has been writing software for over thirty years. He has built software in health care, automotive, ecommerce, deaf assisted software and hardware devices, service providers, and more. He has also run the engineering for products from the first line to the first paying user, which is what ShawnsVTTs is. He has built AI governance tools that other companies use to make sure their AI builds exactly what they need it to build.
That history is why we work the way we do. Over those years we have watched what breaks: untested changes, unreviewed merges, a database change nobody could undo. The rules on this page are the rules we would put on any team, and they apply to the assistant the same way they apply to a person.
We use AI because it lets us keep the safeguards we would want on any project, the tests and the reviews and the real-browser checks, without them swallowing the time we need to build the thing. The tests, the reviews and our own judgment protect your data. The AI does not.
If you would rather not
That is a fair choice. Foundry's own AI Content Policy lets AI help write code as long as the author can understand, explain and maintain it, and we hold every ShawnsVTTs product to the same standard. If you would rather not use something built this way, you can skip it. The Foundry modules are optional extras, and the free tier of every tabletop works without them.
Questions or concerns about any of this: https://www.patreon.com/c/shawnsvtts