00:17: pick the next app: what newcomers broke out with

00:17: pick the next app: what newcomers broke out with

• Boss (27 Oct): "I'd like you to get another app. If we keep building eventually something will hit. And if something hits we can use it to make other apps more visible."
• Hullbound is shipped and on sale (Play and itch), so RULES §1 allows the next app. §7 says to prove the channel first.
• Look at Obsidian plugins added 27 Jul-27 Sep 2026 (2,112) and since then (1,576): the top ones by downloads, what each is, and whether the maker was a nobody (their first plugin). Check the year's top forum asks against what's been built.
• Pick a lane and a first plugin. Write it into scratch, then FACTS.md once committed.

00:27: what sells in the Obsidian directory

The boss: "If it sells I don't care what it is". So a plugin counts, if it sells, and the dice roller pick doesn't meet that bar: I said myself it won't sell.

• Write the boss's quote into FACTS.md, dated.
• Find the plugins labelled Paid or Optional payment, with downloads, and any public sales or subscriber numbers.
• Find what tabletop people pay for (map makers, VTT add-ons) and whether any of it sells inside Obsidian.
• Pick again on that evidence, or keep the dice roller as a funnel only if something paid sits behind it.

00:29: where a new seller's digital product measurably sells

Obsidian gives reach, not sales. Look for places that show public sales counts for shops that started recently with nothing: Etsy digital downloads (shop sales counts), Gumroad (sales shown on some products), and the Chrome Web Store (users, and paid tiers). For each: are new shops selling, what sells, at what price, and can AI-made goods be listed there truthfully. Write the evidence in scratch.

00:46: commit to the next app: Obsidian plugins, first a dice roller

The boss: "Whatever you truly think is the shortest path to money is the way we go. You have the knowledge and the research. You tell me". My call: a run of Obsidian plugins, free with optional paid tiers, starting with a dice roller that reads Dice Roller's syntax.

• Write it in FACTS.md as the current app with the boss's quotes and the channel proof.
• Read Obsidian's current plugin docs (sample plugin, manifest, API) and date them.
• Scaffold the plugin outside app/ in a new top-level folder? No: RULES say app/. Put it at app/plugins/dice/ with its own build, so the site keeps working.

00:56: scaffold Dice Tray, the first Obsidian plugin

• app/plugins/dice-tray/: manifest, esbuild, tsconfig, MIT, dice engine (src/dice.ts) reading Dice Roller's notation, src/main.ts with inline dice: chips, a roll modal and settings, styles.css.
• Boss said make it look cool: chip with die icon, tumble animation, nat-20 glow, hover card with the dice tiles.
• vitest on the engine; npm run build must pass.
• Boss said they will make the repo. Write that in FACTS.

01:05: add the boss's visit counter to every page and deploy

• Boss order: one script tag in the <head> of every page, src https://pulse.bananafest-destiny.com/p.js, data-site = the page's hostname, defer. Change nothing else.
• Find every HTML page (Vite entries and public/**/index.html), add the line, build, deploy, curl each deployed page for the tag, report the URLs.

01:08: Dice Tray passes Obsidian's own lint; section rolls

• Run eslint-plugin-obsidianmd (what the submission bot checks) on src/ and fix everything it flags.
• Start dice: [[Note]] section rolls and dice: [[Note^block]] table rolls using the metadata cache, since those are the Dice Roller uses old notes depend on.
• Tests for the table-row parsing; build must stay green.

01:13: smoke-test Dice Tray's Obsidian side without Obsidian

• No Obsidian on this server, so: a jsdom test with a shim of the obsidian module (Plugin, Modal, PluginSettingTab, MarkdownRenderer, createSpan/createDiv/setText/addClass helpers) that loads the plugin, feeds it HTML with dice: codes and a fake vault note, and checks the chips render and reroll on click.
• Then tag 0.1.0 on the mirror repo with main.js, manifest.json, styles.css, and tell the boss what a real-vault test needs.

01:26: live demo page for Dice Tray at /press/dice-tray/

• Bundle src/main.ts with the test shim in place of obsidian (esbuild alias) into a browser script, plus a page driver that fakes a note with headings, a list and tables, runs the post-processor over sample HTML, and uses the real styles.css with Obsidian-like CSS variables (dark and light).
• Put it at app/public/press/dice-tray/ (noindex, the counter tag like every page), deploy, curl it, give the boss the one URL.
• Later the same page gives the README screenshot or GIF.

01:32: README screenshot and demo link for Dice Tray

• Screenshot the live demo's note area in headless Chromium, crop it, save as app/plugins/dice-tray/docs/demo.png.
• README: picture at the top, a 'Try it in your browser' link to /press/dice-tray/.
• Commit, push, mirror push so the GitHub repo shows it.

01:36: how many plugins, free and paid, to reach money (boss question)

• Pull Obsidian's own download stats (obsidian-releases community-plugin-stats.json and community-plugins.json).
• Work out what a typical new plugin gets per month, what the top TTRPG plugins have, and what Dice Roller has.
• Answer the boss with one number for free, one for paid, one total, with the sums shown.

01:49: how Obsidian works, the TTRPG plugin list, speech-to-text (boss question)

• From Obsidian's own plugin list: the TTRPG plugins by what they do, and every speech/transcription plugin with downloads and how it works (local Whisper, OpenAI key, paid).
• WebSearch for tools outside Obsidian that record a tabletop session and write the notes, with prices.
• Answer the boss plainly; say whether a session-recorder plugin is a better first paid plugin than Dice Tray.

01:54: will a dice roller get our name in front of players (boss question)

• Check every dice plugin in Obsidian's list: downloads, last update, and Dice Roller's open issues and last commit on GitHub.
• Answer plainly whether Dice Tray can win reach against them.

01:57: one plugin that bundles several table tools (boss idea)

• Check how the existing bundles do (Solo RPG Toolkit, TTRPG UI Toolkit, RPG Manager) and when the big single-purpose ones were last updated (Statblocks, Initiative Tracker, Calendarium, Dice Roller).
• Answer the boss: is a bundle worth more than separate plugins, and what goes in it.

02:00: where Statblocks and Calendarium keep their data (boss question)

• Read both plugins' own docs/source for where monsters, homebrew and calendars are stored (note code blocks, frontmatter, the plugin's data.json in the vault).
• Answer whether GM Screen can read them in place, the way Dice Tray reads dice: codes.

02:03: confirm before building GM Screen (boss order)

• What GMs who use Obsidian search for and ask for: plugin search, Reddit and forum threads, words they use (GM screen, DM screen, session notes).
• That no plugin records a tabletop session into the vault: Obsidian's list (check Archivist GG, 1.6k downloads, seen earlier), GitHub/BRAT plugins, outside tools that write into Obsidian.
• Obsidian's developer policies on paid features, license keys, network use and recording.
• Whether a plugin can record audio on desktop and phone.
• Current transcription prices.
• Where sessions happen (in person vs Discord/online), since that decides where recording must work.
• Write each finding with its source in actual/, then report.

02:12: DM Screen name and the free-plugins-plus-paid-hub idea (boss idea)

• Check: Obsidian's naming rules for plugins; whether "Dungeon Master" is a Wizards of the Coast trademark; whether "DM Screen" is free in the list.
• Check that paid tiers in Obsidian plugins actually sell (Copilot Plus, Smart Connections Pro) and how they gate it.
• Check how plugins can talk to each other with the public API.
• Answer the boss with one recommendation.

03:04: Second plugin, an initiative tracker that reads Statblocks notes (boss yes)

• Boss said yes to repos per plugin and a rename if needed; they will make the Obsidian account. Write the quote in FACTS.
• Pick a free name and id (Initiative Tracker id is taken). Check obsidian-releases.
• Build it in app/plugins/<id>, same setup as dice-tray: tests, eslint, build, demo page on the site.
• Reads creatures from notes with statblock frontmatter (hp, ac, initiative modifier), rolls with Dice Tray's dice code, tracks turns, HP and conditions in a side view, saves the encounter in plugin data.
• Create the GitHub repo, push a subtree mirror, link both plugins to each other.

05:07: Third plugin, a session log (check the field, then build)

• Check what session-log plugins exist and what GMs search for (autocomplete, obsidian-releases).
• Build the smallest useful one in app/plugins/<id>: timestamped log lines during play, linked to the fight (listens for quick-initiative:change) and to the people and places named.
• Same setup: tests, lint, build, live demo page, repo and 0.1.0 release, cross-links.

05:30: Which small GM plugins come next (boss question)

• Check what GMs search for and which small tools already exist in obsidian-releases, with downloads, before naming any.

06:14: Fourth plugin, an encounter builder (boss yes)

• Check first that the difficulty math is in a free rules text (SRD 5.1 or 5.2, CC BY 4.0), and note the attribution it needs.
• Build in app/plugins/<id>: an encounter block lists the party and the monsters (links to Statblocks notes), shows XP and difficulty, and a Start fight button writes an initiative block for Quick Initiative.
• Same setup as the others: tests, lint, demo page, repo and release, cross-links.

06:34: Fifth plugin, progress clocks

Check the field first (Lancer Companion has clocks; look for any other clock or countdown plugin and the progress-clocks id). Build in app/plugins/<id>: a clock block draws a segmented circle (4, 6, 8 segments) with a name; click fills a segment and writes it back; several clocks in one block; a racing pair. Same setup as the others: tests, lint, demo page, repo and release, cross-links.

07:07: Launch posts for the five plugins (drafts for the boss)

The plugins are live but nobody knows. Read the current rules of r/ObsidianMD, the Obsidian forum's Share & showcase category, and one or two TTRPG subs (r/rpg, r/DMAcademy, r/bladesinthedark) on self-promotion and on AI-made tools; note them in LEARNED.md with dates. Check whether the 0.1.1 releases were rescanned. Then draft the posts in the boss's voice, one per place that allows it, with the link where each place wants it. Nothing gets posted by me.

07:12: Rename Progress Clocks to Tabletop Clocks

While reading the post rules I found that the id progress-clocks is already taken in the directory by tokenshift's Progress Clocks (sidebar clocks, last updated Jan 2025). The boss can't submit ours under it. Rename to Tabletop Clocks, id tabletop-clocks (the directory says it's free): plugin folder, manifest, package, event name tabletop-clocks:change, README, demo page moved to /press/tabletop-clocks/, cross-links in the other four READMEs and demo footers, GitHub repo renamed by API, a fresh 0.1.0 release there. The clocks block stays (theirs has none). Tests, tsc, eslint, deploy, mirror. Then back to the launch-post drafts.

07:21: Encounter Builder !important warning the boss saw

The boss sent the directory's warning for Encounter Builder (styles.css:196 and :304). Check whether those lines are the 0.1.0 file and whether the 0.1.1 release is clean, and what the directory is scanning now.

07:25: Check the directory after the boss's release check

The boss says all are live and they checked for new releases. Read each directory page for version, review status and findings, and whether Tabletop Clocks is listed.

07:35: Forum account on hold

The boss's first Share & showcase post put the new forum account on hold for staff review. Note why it likely happened and what not to do in LEARNED.md; tell the boss to wait.

07:40: How new plugins get seen

The boss asks how the live plugins get seen. Check, don't guess: whether obsidianstats lists new plugins and ours, the weekly "Obsidian Plugin Stats" roundup post on r/ObsidianMD, Obsidian Roundup, and how the in-app browser sorts. Answer with what's checked.

07:49: Why the app's Browse can't find Dice Tray

The boss searched "dice tray" in Obsidian's Browse: 0 results. The app reads community-plugins.json; ours aren't in it. Look at what the mirror bot has added since our listings went live and find out what gets a directory plugin into that file (docs, the mirror commits, the releases repo README). Answer the boss with what's found.

07:54: Who covers running games in Obsidian

Find the people and places where tabletop players learn Obsidian: video makers, guide sites, Discord servers, and lists of TTRPG plugins. For each: how big, whether they take submissions or tips, and how to reach them by the rules. Write it into LEARNED.md and draft what the boss would send. Nothing sent by me.

08:03: Is the DM Screen the thing to build now

The boss asks whether the paid DM Screen should come first, since the small plugins are comparable at best. Check what already records, transcribes and recaps sessions in Obsidian, and what Obsidian's policy says about paid plugins, then answer with one recommendation.

08:05: What the other plugins do that ours don't

The boss asks what the bigger plugins do that ours don't. Read the actual READMEs of Dice Roller, Initiative Tracker, and the other clocks and encounter plugins, and list the gaps, one plugin at a time.

08:09: Bring the plugins up to the big ones, Dice Tray first

The boss: "I don't want to copy their plug ins clearly. We need to make ours at least as good as theirs". So: close the gaps listed in LEARNED.md with our own code, built from the feature lists and never their source. Order, biggest rival first:

1. Dice Tray: a side panel (d20 set, advantage and disadvantage, modifier, history); saved results (dice+:) and writing the result into the note (dice-mod:); rolling a random note by tag using Obsidian's own tags (no Dataview needed); frontmatter fields in formulas; Genesys narrative and Fantasy AGE stunt dice; an API for other plugins.
2. Quick Initiative and Encounter Builder: a side panel tracker, a Player View window, a party saved in settings, SRD 5.2.1 monsters and condition text built in, and more difficulty methods (2014 and 2024 5e, Pathfinder 2e).
3. Tabletop Clocks: counters and stopwatches.
4. 3D dice last.

Each step: tests, tsc, eslint, build, a 0.2.0 release, and a demo update. The DM Screen comes after.

08:16: Restarted; read HANDOFF, check the Browse listing and mail, then carry on with Dice Tray 0.2.0

• Read HANDOFF.md. Check whether the four plugins are in community-plugins.json yet (tell the boss if so), read mail/in, check if today's daily is due.
• Then continue Dice Tray 0.2.0 from where HANDOFF leaves it: tests on what's edited first.

08:20: The differentiator: the session note writes itself

The boss: "Then we need to figure out a differentiator. We need to make ours different from theres". Mine: everything that happens at the table lands in the session note as plain Markdown, by itself. Rolls with their dice, turns and rounds, damage and conditions, clock ticks, each one a line in the Session Log with links to the NPC and monster notes. The big ones keep their state in hidden plugin data (Dice Roller rerolls each time a note opens, and keeps saved results out of the note; Initiative Tracker's combat logger covers fights only). Then the paid DM Screen turns that log, and the recording, into a recap in the campaign notes. The free plugins fill the log, and the paid one reads it.

1. Dice Tray: a roll you click goes into the session log (the open note's session-log block, or a note set in settings), and an inline roll can keep its result in the text, so reopening the note doesn't reroll it.
2. Quick Initiative: new rounds, damage, downs and conditions go into the log.
3. Tabletop Clocks: ticks go into the log. Encounter Builder: starting a fight logs who is in it, linked.
4. Dropped from the parity list: 3D dice, tag rollers through Dataview, a plugin API. Kept: the d20 side panel, which people expect.

Each step: tests, tsc, eslint, build, demo update, then release.

08:25: A second differentiator, on top of the self-writing note

The boss: "We still need something else on top of that". Candidate: the players see the table on their own phones, live, from a link (initiative order and whose turn, clocks, rolls made in the open, handouts revealed), with nothing to install. Check first whether any Obsidian plugin already does that, and what Initiative Tracker's Player View actually is.

08:32: Dice Tray: a clicked roll goes into the session log

The boss: "go ahead. Then we need to match the other plugins and exceed them". So both differentiators go ahead, and the full parity list (3D dice, tag rolls, API included) comes back after them.

• A roll you click (not the first roll when the note renders) appends a line to the note's session-log list, in Session Log's own format (- HH:MM ...), with the dice spelled out: - 19:12 1d20 + 5 -> [17] + 5 -> 22. If the note has no log block, a setting names a log note; with neither, nothing is written.
• Same from the roll modal, into the active note.
• Read session-log's source for its entry format and where it inserts, so the two agree. Tests, tsc, eslint, build.

08:35: Dice Tray: rolls that keep their result in the note (dice+ and dice-mod)

• dice+: 1d20 + 5: rolled once, then the note itself is rewritten to dice+: 1d20 + 5 -> [17] + 5 -> 22, the same line the log uses. It shows that result on every open, and a click rerolls, rewrites and logs it. Dice Roller keeps these in plugin data keyed by path; ours is in the text, so renames, sync and other apps keep it.
• dice-mod: 3d6: rolled once and replaced by the plain text of the roll, as Dice Roller does.
• Found by the post processor's section info and the code's place among identical ones; if the section can't be found (an embed, a hover), it rolls without saving.
• Tests, tsc, eslint, build; then release Dice Tray 0.2.0 and Session Log 0.2.0 together.

08:42: Release Dice Tray 0.2.0 and Session Log 0.2.0

Bump manifest, package and versions.json in both; build; commit; subtree split and push each mirror; make the 0.2.0 releases with main.js, manifest.json, styles.css the same way 0.1.1 was made. Check both release pages list the three files. Then a short line to the boss on what the update adds.

08:44: Demo pages show 0.2.0

The Dice Tray and Session Log demo pages are how people try the plugins before installing. Find how each demo.js is built, rebuild both on 0.2.0, and add to the sample notes: a dice+: roll, a 1d20 + dex with a field, a narrative pool, and on the Session Log page a Dice Tray roll that lands in the log. Site tests, deploy, check both pages from outside.

08:54: Expired crew links answer 410

docent's served-check counts the expired-link answers on /api/crew/bellok, /wright and /unbell as served pages, because they return 200. Make the refusals 410 Gone with the same body, so a player clicking an old email link reads the same words. Worker tests, site tests, deploy, check all three from outside, tell docent.

09:03: The fight writes itself: rounds, damage and conditions into the log

The four plugins are in community-plugins.json now (checked 09:03), so Browse in the app finds them; tell the boss. Then the next piece of "the session note writes itself": today Session Log only notes a fight's start, who went down and its end. Read what quick-initiative:change carries, and log the useful middle too, without flooding the log: a hit or heal on a creature (Bugbear takes 9, 18/27 left), a condition put on or taken off, and each new round only as a short marker. One setting per kind, sensible defaults. Tests in both plugins, READMEs, demo; release QI and SL together.

09:15: Our plugins on a phone

The boss sent an r/ObsidianMD thread: people want notifications, widgets and PDF export on mobile. Checked: Mobile Export (PDF from mobile) is already in the directory; real phone notifications need a companion app (Notelert, ntfy on Android; Reminder Sync on iOS), because plugins can't raise system notifications. Not a gap for us. What it says about us: GMs use Obsidian on phones and tablets at the table, and Dice Tray shows each die only on hover, which a phone doesn't have (a tap rerolls). Open all five demos at phone size with touch in Chromium, find what breaks, fix the worst (dice on a phone first). Note it in LEARNED.

09:36: Clocks into the session log

The boss says Tabletop Clocks is submitted too: write that into FACTS and check whether it's in community-plugins.json yet. Then the next differentiator piece: a clock tick in Tabletop Clocks goes into the session note's log ("Clock 'The watch closes in' 3/6"), with a setting to turn it off, tests, demo, releases for both plugins.

09:52: The table on the players' phones: relay and player page

Boss: "Go for it." Second differentiator. A small Cloudflare relay in our worker: the GM's Obsidian posts the table (turn order with whose turn it is, clocks, the last few rolls) to a room; players open a short link or QR code and see it live, nothing to install. Today: the worker side (create room, post state with the room's secret, read state, live updates), the player page at /table/, and tests. The plugin side (the DM Screen) comes after. Opt-in only, nothing leaves the vault until the GM starts sharing, and the README will say what goes over the network. Nothing asks for money until the boss gives a pay URL.

10:07: DM Screen, first cut: share the table

The GM side of the phones view. A new plugin in app/plugins/, the start of the paid DM Screen. A "Share the table" command opens a room, shows the link and a QR code, and from then on sends the table whenever Quick Initiative, Tabletop Clocks or Dice Tray say something changed: turn order and whose turn, players' HP as numbers, monsters' as words (hurt, bloodied, down) unless the GM picks otherwise, clocks, the last rolls. "Stop sharing" closes the room. Off until the GM starts it, and the README says what goes over the network. Check the id is free first. Not submitted and nothing asks for money until the boss gives a pay URL.

10:23: DM Screen: handouts on the players' phones

The other player screen plugin (ttrpg-tools-screen) shows handouts and maps, but on a second window at the GM's own desk. Ours goes to the phones. "Show to players" on an image in the vault (file menu and command) or on selected text (a letter, a riddle) puts it at the top of the players' page until the GM hides it. Images are shrunk in Obsidian to 1280px JPEG before they leave, kept by the room next to the table, deleted with it. Relay: one image per room, 1MB cap, same key. Page: tap the image to see it full size. Tests on room, worker and plugin; demo gets a handout button; deploy and check live. Then tell the boss.

10:40: Dice Tray: a dice panel in the sidebar

Parity with Dice Roller's dice view: a side panel with a button for each die (d4 to d100, plus fudge), tap to add, a modifier, advantage and disadvantage, Roll, and a history of the session's rolls that a click copies. Its rolls are announced like any other (dice-tray:roll), so they go into the session log and onto the players' phones. Before building, open Dice Roller's README to see what its view does, and cite it. Tests, demo, release as 0.3.0 on the mirror. Run the 28 Oct daily on its own after 11:07Z.

10:55: Dice Tray: rolls in Live Preview

Live Preview is the editor most people write in, and Dice Tray only draws its chips in reading view, so there a dice: line stays code. Dice Roller draws its rolls in Live Preview too. Before building, open its source to see how it does it (a CodeMirror view plugin) and cite the file. Build a view plugin that swaps dice: inline code for the same chip when the cursor is outside it, with a click to roll again, and dice+: writing back as it does in reading view. Tests for finding the ranges; check it in a real CodeMirror in the demo. Release as 0.4.0. At 11:07, stop and run the 28 Oct daily on its own.

11:09: Dice Tray: rolls on a tag

Dice Tray's last "Not yet". Dice Roller's README (Obsidian-TTRPG-Community/dice-roller, "Tag Rollers" and "Links") does it this way: dice: #tag gives a random block from every note with the tag, |- one random note, |+ every note, |link a link to a random note; it needs the Dataview plugin. Mine reads tags from Obsidian's own metadata cache (body and frontmatter tags, nested #tag/sub too), so nothing else is needed. It uses the same block picking as dice: [[Note]], a click rolls again, and a link opens the note. Tests; a demo line; release as 0.5.0 once the daily is done (no push or deploy while it runs).

11:53: DM Screen: decide the price, the repo and how it is paid for

The boss, asked whether DM Screen can be sold on itch and whether a public repo is OK: "It's up to you. It's your product". Write that into FACTS. Before choosing, read Obsidian's developer policies on paid plugins and cite them with the date, and look at what paid Obsidian plugins charge and how they check payment. Then decide the price, whether the code goes in a public repo (the community list needs one), and how a license works, and write the decision down. The pay link itself still has to come from the boss: itch is their account (RULES §5), so ask them for the itch page once the decision is written.

12:39: DM Screen: the key and the one-hour trial

The boss on the key: "Ok sounds good". Build what LEARNED "How DM Screen is sold" says. Worker: a table room opened without a key closes after an hour; with a good key it lasts 12 hours as now. A key is the buyer's itch download key (or their download page URL), checked once with itch's download_keys lookup for the DM Screen game id, and remembered as a hash. A second way in: the email they bought with, a code mailed to it (the same as Shipwright's claim), then itch's lookup by that email. The game id comes from the itch page the boss is making, so until then the check answers "not sold yet" and every room is the trial. Plugin: a key field in settings that says it is kept in the vault's plugin folder, a "Check" button, the trial's time left on the share window, and the README's payment and network lines. Tests for the worker and the plugin. Don't release it until the itch page exists.

13:07: DM Screen: check the itch page and the trial live, then the next gap

• Read the itch page's state from the API (read-only): published or still a draft, the price, and whether it has the cover and upload.
• If it's public, open a table on the live site without a key: the answer should carry trial.ends about an hour out and the link the boss gave. With a made-up key, the "itch doesn't know that key" line. If it's still a draft, check the trial in a test against Keys instead.
• Then, with the time left, compare Quick Initiative to Initiative Tracker for the gap that matters most to a DM Screen buyer, and start on it.

13:35: The boss said "do it all": the order, and Encounter Builder's Pathfinder 2e first

The boss's answer to the list: "do it all". The order, each its own entry, shipped and released before the next:

1. Encounter Builder: Pathfinder 2e budgets (XP by level difference, Trivial to Extreme), beside the 5e math. This entry.
2. Tabletop Clocks: counters and stopwatches.
3. DM Screen: maps. A battle map with tokens moved from the note, live on the phones.
4. Dice Tray: 3D dice and an API for other plugins.
5. Encounter Builder: SRD 5.2.1 monsters, so a fight needs no hand-written notes.
6. Drafts for the boss: r/rpg's weekly self-promo thread, a note to obsidianstats, and a short phone clip. They lead with the free plugins and the demo.
7. Watch the first sale's key.

Alongside: the jam (closes 31 Oct 03:00Z), the 30 Oct Feedback Friday, and the daily run.

For 1: read Encounter Builder's difficulty code and the PF2e rules on Archives of Nethys (the GM Core encounter budget table), date the read, then add a system: pf2e line, tests, README, release.

13:43: Tabletop Clocks: counters and stopwatches

Item 2 of "do it all". Encounter Builder 0.2.0 (Pathfinder 2e) waits on the site tests for its demo deploy, then commit, mirror and release.

The bigger clock plugins also keep plain counters (a torch's turns, ammo, a ritual's progress) and timers. Tabletop Clocks should do both in the same block style:

• a counter line: a number with − and +, an optional max, kept in the note like the clock segments are;
• a stopwatch line: start, pause and reset, with the elapsed time written into the note when paused, so it survives a reload;
• both go to DM Screen like clocks do, if that's a small change on DM Screen's side;
• tests, README, a version bump, the build, the demo if it's cheap, commit, mirror (tc-split), release.

First, read the plugin's parser and what the clock lines look like.

13:52: DM Screen: a battle map on the players' phones

Item 3 of "do it all". DM Screen is paid, so the map has to be something the free plugins and the other initiative trackers don't do: a map the players see live on their phones, with tokens the GM moves in the note.

• A map block in a note: the first line is the picture (![[Cellar.png]]) and a grid size (grid 20x14); then one token per line, Aria C4 blue, Goblin 1 F7. A token is a name, a cell (column letter, row number) and an optional colour.
• In Obsidian the block draws the picture with the grid and the tokens. Dragging a token (or clicking it and then a cell) writes the new cell into its line, so the note keeps the map the way the clocks keep their count.
• Sharing sends the map: the picture once, shrunk (the same way as a handout, in its own slot in the room), and then the grid and tokens with each change. The players' page shows it under the turn order, and the token whose turn it is (by name from Quick Initiative) is ringed.
• Worker: a second picture slot, /api/table/<room>/map, the same limits as the handout's, deleted with the room. The table's map field is cleaned like the rest: at most 60 tokens, a grid at most 60x60, names cut short.
• Tests for the parsing, the line rewrite, clean(), and the page. A demo check in the browser. Then the site tests, deploy, the DM Screen version bump, mirror, release, README (network use: the map picture goes to the room).
• Not this round: fog of war, token pictures, measuring.

14:14: Solo TTRPGs: what players use, what they pay for, what is missing

The boss asked to look into solo TTRPGs once the battle map was out, said Reddit expects solo play to take off, and said it might be separate from Obsidian. This is research, not a build.

• Where solo players are and how many: r/Solo_Roleplaying size and activity, itch's solo tag, DriveThru solo bestsellers, Kickstarter solo campaigns in 2025-26.
• What they use: oracles (Mythic GME, Ironsworn/Starforged), journaling games, the apps that exist (Obsidian plugins like Ironvault, phone apps, web tools), with prices and ratings from their pages.
• What they ask for and don't have: threads asking "is there an app for", complaints about existing tools.
• Inside Obsidian or separate: where each would reach players and how it would get paid.
• Write it for the boss with a link for each claim, and a recommendation. FACTS and LEARNED as it goes.
• Done when the boss has the write-up.

14:28: Solo, part two: the r/rpg predictions thread and "what should I play" requests

The boss sent the r/rpg predictions thread and said people also ask for a game to fit specific wants ("Not too much fantasy, but some").

• Read the whole thread (Reddit blocks fetches; a browser read works) and sort the predictions.
• Count how often r/rpg gets "Game Suggestion" posts and how many replies they draw.
• Look at the finders that exist (ttrpg-games.com, ttrpglist.com, rpgbuilder.ai) and what they do.
• LEARNED, then tell the boss.

14:31: Dice Tray: dice that tumble in 3D, and a roll API for other plugins

The boss: "ok, finish it up". I take it as: finish the plugin list (Dice Tray, Encounter Builder monsters, the drafts), then go to solo.

• Dice Roller draws 3D dice. Ours tumble the number only. Add dice that roll across the note in 3D (d4, d6, d8, d10, d12, d20), drawn in code, landing on the rolled faces. Off by setting; respects reduced motion.
• An API other plugins can call: roll a notation and get the total and each die back, with the 3D dice if wanted. DM Screen and Quick Initiative can use it.
• Tests, build, README, release 0.6.0, mirror.

14:50: Encounter Builder: the free SRD 5.2.1 monsters, by name

• Item 5 of the list. Today a monster in Encounter Builder needs its CR or XP typed in. Add the monsters from the D&D SRD 5.2.1 (CC BY 4.0) so "Goblin Warrior 4" or "Owlbear" is enough: name to CR and XP, with a search as you type. Credit Wizards of the Coast as the licence asks, and say we are not endorsed.
• Only names, CR, type and size: no stat blocks, so the plugin stays small. Check the SRD's own monster list for the exact names; take nothing from non-SRD books.
• Tests, README, release 0.3.0, mirror, demo if it shows a fight.

14:56: Drafts for the boss: the r/rpg self-promo thread, a note to obsidianstats, a phone clip

Item 6 of "do it all". Three drafts, sent to the boss, none posted by me. All lead with the five free plugins and the browser demos, DM Screen last. Boss voice: lowercase, one thought, no em-dashes. r/rpg: the weekly self-promotion thread only, and that sub is strongly against AI, so the copy says nothing that isn't true and answers truthfully if asked. Before writing, open the current weekly thread and its rules and cite them. The clip: a short screen recording of the Dice Tray and DM Screen demos at phone width, made with Playwright, kept in the scratchpad until the boss says where it goes.

15:07: DM Screen's Obsidian review, and the first sale

DM Screen is the one plugin not yet in the community list. Read its obsidian-releases PR: the review bot's comments and any human review. Fix anything it flags in the plugin, release a patch if needed, and say what's left. Then read the worker's DM Screen trial and key-check counts (counts only: no keys, no emails) and the itch page's purchase count, read-only. 20 minutes.

16:05: The Reddit draft moves to r/rpgpromo

The boss has never posted on r/rpg, so under rule 7 the plugin post can't go there. Write that into FACTS. Read r/rpgpromo's rules and what does well there, then fit the draft to them.

16:07: A Free Tool Friday draft for r/DMToolkit

(Written a few minutes late: the reading began as part of the entry above.) r/DMToolkit has a weekly Free Tool Friday thread. Read its terms, check the free plugins against them, and draft a top-level comment for the boss to post on 30 Oct.

17:07: The next app: who already helps people find a TTRPG, and is anyone using it

Research before committing (RULES section 1 allows a next app now that DM Screen is shipped and on sale). Look for: existing TTRPG finders and recommenders (sites, quizzes, databases, the r/rpg wiki lists), how big and alive they are, what they miss. Also, how often "what should I play" requests come up and what the asks look like, and whether solo games are a big share. Cite every page. No build, no FACTS entry yet. 20 minutes.

17:10: The next app: solo play tools on phones, what exists and what people pay

• Read mail/in first.
• Look up the solo play apps on Google Play and the App Store (oracles, Mythic, Ironsworn companions, solo journals): ratings, installs, prices, last update.
• Look up what solo players say they miss on their phones (r/Solo_Roleplaying), citing threads.
• Write what I find into LEARNED with sources. No FACTS current-app entry and no build in this block.

19:07: Obsidian's solo plugins, what they do and what solo players miss

• Read mail/in. Check whether Obsidian's list has DM Screen yet, and the itch counts (read-only).
• Read the READMEs and download counts for Iron Vault, Mythic GME Support, OPSE Oracle and Solo RPG Toolkit, plus anything else tagged solo.
• Read r/Solo_Roleplaying threads about Obsidian setups and what people built by hand.
• Write the gaps into LEARNED with sources. No FACTS entry and no build.

19:32: The next app: commit to the solo plugin in FACTS, then start it

• The boss said go. Check RULES §1 (DM Screen shipped, tested, on sale and listed), read the Obsidian policy on paid and freemium, and pick the name, id and how it is sold.
• Write the current-app entry into FACTS with the boss's words, then scaffold app/plugins/<id> from Dice Tray's setup.
• First slice: the oracle (odds, chaos, scenes) as a code block, with tests.

19:42: Solo Oracle 0.1.0: commit, deploy the demo, mirror and release

• Site tests must pass first, then commit the plugin and the demo page, and deploy so the README's demo link works.
• Subtree split to so-split, push to walkertbrown/solo-oracle main, and make release 0.1.0 with main.js, manifest.json and styles.css.
• Check the release assets download. Then ask the boss to submit it to Obsidian as Free (Pro comes later).

21:07: Solo Oracle: roll on your own tables from the panel

• Read how Dice Tray finds and rolls tables, and reuse what fits (copy the code, no shared package).
• Free part: a table: [[Note#Section]] line in the block, a Roll button per table, and the result journalled like the other rolls. Weighted rows (3: A wolf) and nested rolls ([[Other table]] in a row) are Pro later; plain rows ship now.
• Tests, lint, build, demo update. Commit; release only if it's done and checked inside the time.

22:09: Solo Oracle listing: short and long description, featured picture, screenshots

• Boss asked for listing copy and images. Check what Obsidian's submission form asks for (from the DM Screen submission notes), then write them to fit.
• Images drawn from the real plugin (the demo page), hosted under /press/solo-oracle/listing/ with an index page, so the boss gets one link.

22:46: Solo Oracle long description under 1000 characters

• The boss's form caps the description at 1000 characters. Cut the long one to fit, keep the same facts, update the kit page.

23:07: Solo Oracle 0.2.1, no !important in the styles

• Obsidian's review warned about !important before (DM Screen). Solo Oracle isn't listed yet, so fix it before the review sees it: swap the four !important rules for selectors that win on their own, check the demo looks the same, release 0.2.1.

Next

• Docent's three Hullbound clips are up and mailed (25 Oct). 1 Nov: send Docent a week of /hb counts (crew-from-hb, crew-start-from-hb). Same /media/ spec plus claim JSON; the speed-up is said in notes. 1 Nov: send Docent a week of /hb counts.
• 25 Oct after 11:07Z: the daily, if today's derelict is missing.
• DERELICT (AI Browser Game Jam 5, submitted 20 Oct): competition check today. Rating opens 31 Oct; never rate entries myself.
• HULLBOUND (main work), live on Google Play since 24 Oct. Waiting on the boss: - itch: (zips uploaded by the boss 25 Oct 17:31Z, checked) before 31 Oct 03:00Z: post the "Rooms have pictures now" devlog (press page step 6), put desk-rooms.png first in the Derelict screenshots, upload the Hullbound zip again (432,405: the haul said at the top, a count of boards from the crew page, and the Play line for Android browsers), and paste the Hullbound description from /press/hullbound/ (25 Oct: episodes, Shipwright and the Play line together). - Reddit drafts in app/store/REDDIT-ANDROID.md (r/AndroidGaming [DEV], r/MobileGames). The next Reddit ask is not before 27 Oct. - Phone: check that Shipwright stays hidden after buying; uninstall com.bananafestdestiny.hullbound.test; turn off wireless debugging. - Offered, not yet decided: move the deck wall into the first session; count a Bulkhead purchase as Shipwright.
• Hullbound watch, each day: Android installs from strangers (events.sh distinct phone-app browsers above 1); crew-from-hb, crew-start-from-hb, crew-play-dock; tale-* pings; writer spend in crew-stats.sh against MONTHLY_CAP $10.
• Feedback Friday on r/incremental_games, 30 Oct, sidebar first (Rule 1D).
• Hullbound 1.7 (code 8) uploaded to Production by the boss, 26 Oct. pt-BR listing: dropped.
• Uploaded by the boss 27 Oct 01:48Z (checked): derelict-itch 317,278 and hullbound-itch 432,614. Read title-guest-itch against title-itch, stop-seen-*, choice-*, crewad from 27 Oct 01:48Z.
• 31 Oct 03:00Z, jam rating opens: tell the boss that rating other entries lifts Derelict in the "Most Karma" sort (forum posts, not docs). I never rate.
• BULKHEAD (upkeep): the daily keeps running. The boss sets the itch price from $12 to $9. Build the 1.20 upload round (plan/2026-10-22.md Next) only when the boss has an upload slot.
• 27 Oct: re-read sittings.sh (as in plan/2026-10-22.md Next) only if there are 20 or more web sittings.

00:17: pick the next app: what newcomers broke out with

• Corrected the newcomer list: several "new" plugins were old repos missing from my snapshots. Repos actually created Jul-Sep 2026 still reach 5K-60K (Atlas VTT 18,731 from 20 Sep).
• Fathom meeting sync out: its one plugin has 51 downloads after a month, against a third Granola plugin's 12,193. Bases views out (214 plugins).
• Tabletop in Obsidian: about 111 plugins, 1.14M downloads. jareika went from nothing in Oct 2025 to about 145K over six plugins. Their hit, Zoom Map (90K), replaces stale Leaflet (318K).
• Obsidian, 12 May 2026: plugins that fail the scan or go unmaintained will be phased out. Dice Roller (287,710; no release in 582 days; nine outsider PRs unmerged) and Calendarium (199,829; 395 days) are both "Review Caution", with no real successor.
• Pick, pending the boss: tabletop plugins under one maker name, first a maintained dice roller that reads the old dice: syntax, then a calendar that imports Calendarium. Written in scratch with three asks. Not in FACTS until confirmed.
• Finished 00:25

00:27: what sells in the Obsidian directory

• Wrote the boss's answer into FACTS.md: "If it sells I don't care what it is".
• Obsidian directory search: 10,496 entries; 35 paid, 321 optional payment. The paid ones that earn are fronts for outside services (Readwise 35,716 installs). The paid plugins by unknown makers have 7-256 installs at prices like ¥9.9. Optional-payment money is AI and sync subscriptions.
• Result: no evidence that an unknown maker sells an Obsidian plugin. The dice roller pick doesn't meet "if it sells". Next: find where a nobody's product measurably sells.
• Finished 00:29

00:29: where a new seller's digital product measurably sells

• Etsy is 403 to fetch. Gumroad search: the top sellers are Procreate brushes, Notion templates and presets, sold to the makers' own followers. Tabletop items are mostly free, and Obsidian's paid hit is a 99.99 kit by a known author.
• No evidence anywhere that a stranger buys from a nobody without reach. Revised pick: a free dice roller for reach, plus optional paid dice sets for the same users. Dice-set sales still need a sourced check.
• Finished 00:30

00:46: commit to the next app: Obsidian plugins, first a dice roller

• FACTS.md: current app is a run of Obsidian plugins, first a dice roller (committed in 04232bb). Docs read and dated there.
• Name check: "Dice Tray" / id dice-tray is not in community-plugins.json or the directory search. Author "Bananafest Destiny".
• Put it at app/plugins/dice-tray/ (not dice/), its own package.json and build, so the site build is untouched.
• Finished 00:56

00:56: scaffold Dice Tray, the first Obsidian plugin

• Written: manifest.json, package.json, esbuild.config.mjs, tsconfig.json, versions.json, LICENSE (MIT), README.md, styles.css, src/dice.ts (parser and roller), src/main.ts (inline chips, dice code block, Roll dice command with a modal, settings), test/dice.test.ts.
• Notation covered: arithmetic, kh/kl/k, dh/dl/d, ! !n !i !!, explode and reroll conditions, r/rn/ri, success counting, dF, d%, d66%, d[a,b], s/sd, u, |avg |form |noform |nodice |none |text().
• Not yet: section/tag/table rolls from notes. README says so.
• Look: pill chip with die icon, tumble animation, nat-20 glow and nat-1 red, hover card with every die as a tile (dropped struck out, exploded outlined).
• npm install clashed (esbuild 0.25.5 vs vitest 5's vite); moved to esbuild ^0.28. 19 plugin tests pass; app suite 263 pass. npm run build makes main.js (12.6 KB, gitignored).
• Boss: "make it look cool", "I will make the repo" (FACTS). Not tested in a real Obsidian yet; none on this server.
• Finished 01:05

01:05: add the boss's visit counter to every page and deploy

• 88 HTML pages under app/ (5 Vite entries, 83 under public/) got the one line; 82 before </head>, 6 head-less press/404 pages right after the charset meta. The worker's /api/crew/unbell page got it too. The four page generators (daily-derelict, jam-page, roll20-page, map-pages) got it so new pages carry it. release/ and store/ HTML are not served, left alone.
• tsc clean; built; deployed. Curled 89 URLs: tag present on all 89, missing on none. List in the chat reply.
• Finished 01:08

01:08: Dice Tray passes Obsidian's own lint; section rolls

• eslint-plugin-obsidianmd 0.4.2 (recommended config): 4 errors and 1 warning fixed. The warning wanted the 1.13 declarative settings API (getSettingDefinitions), adopted, so minAppVersion is now 1.13.0. The last error was passing the plugin as the render component; now a MarkdownRenderChild per roll via ctx.addChild. Lint clean.
• src/notes.ts: pipe-table parsing (escaped pipes), lists, lines, column pick, lookup tables (first column "1-5"), note-roll syntax [[Note]], Nd[[Note]], [[Note#Heading]], [[Note^block]]|Column, |line |list |table |norender. main.ts resolves the link through metadataCache, slices by block/heading offsets, renders picks as markdown. 8 new tests; 27 pass. Build 16.7 KB.
• README: note rolls documented; not yet: #tag rolls, dice-mod:, Dice View.
• Boss: "Create the plugin repo". Created github.com/walkertbrown/dice-tray via the API (201). Pushing the plugin folder there as a subtree.
• Finished 01:13

01:13: smoke-test Dice Tray's Obsidian side without Obsidian

• test/obsidian-shim.ts: a stand-in obsidian module (Plugin, Modal, PluginSettingTab, MarkdownRenderChild, MarkdownRenderer, setIcon, App with a fake metadata cache that computes heading/block/section offsets from note text) plus the createSpan/setText/addClass DOM helpers. vitest.config.ts in the plugin aliases obsidian to it; the site's vitest excludes plugins/** (site suite 244 pass).
• test/main.test.ts, jsdom: command and settings tab registered; dice: code becomes a chip with a sane total, 3 die tiles and a title; click rerolls; |form |avg |text() flags; non-roll code untouched; errors inline; dice code block; [[Note#Heading]] list item, [[Note^loot]]|Item column, [[Note^weather]] lookup table; 3d[[Note]] three distinct sections, no frontmatter or headings; missing note message; settings persist and change the default die.
• Found and fixed by it: heading/section slicing used a wrong offset; now explicit [from,to) and a lone list or table under a heading is picked from inside.
• 36 plugin tests pass, lint clean, build type-checks tests too. Mirror pushed. Release 0.1.0 on github.com/walkertbrown/dice-tray with main.js (16.7 KB), manifest.json, styles.css.
• Still untested in a real Obsidian; needs a machine with it, or the boss's.
• Finished 01:26

01:26: live demo page for Dice Tray at /press/dice-tray/

• Built app/plugins/dice-tray/demo/driver.ts + esbuild.demo.mjs (npm run demo): the real src/main.ts bundled with the test shim in place of obsidian into app/public/press/dice-tray/demo.js (21 KB), styles.css copied beside it, a small markdown renderer patched in so lists, tables and bold render.
• Page app/public/press/dice-tray/index.html: noindex, the pulse counter tag, Obsidian-like CSS variables in dark and light, a sample session-prep note with 15 dice: codes, an Encounters note baked in, a type-your-own box, toggles for animation, formula and light theme.
• Deployed twice. Headless Chromium check: 15 chips rendered, 0 leftover codes, 0 console errors, own-roll box works. URL: https://bulkhead.bananafest-destiny.com/press/dice-tray/
• Finished 01:32

01:32: README screenshot and demo link for Dice Tray

• docs/demo.png: the demo's note area at 2x (1440 px wide, 256 KB), taken from the live page in headless Chromium.
• README: picture under the intro plus a "Try it in your browser" link to the demo page.
• Committed and pushed; mirror pushed, so github.com/walkertbrown/dice-tray shows the picture.
• Finished 01:33

01:36: how many plugins, free and paid, to reach money (boss question)

• Source: obsidianmd/obsidian-releases community-plugins.json + community-plugin-stats.json, pulled 2026-10-28. 9,553 plugins, 165M downloads in all. Downloads count every release download, so updates inflate them; users are fewer.
• Whole list: median plugin 912 downloads; top 25% from 3,711; top 10% from 11,897; top 5% from 31,161.
• Newest 2,000 plugins (end of the list): median 75, 90th percentile 608, best 30,788. Newest 300: median 23.
• TTRPG-ish plugins (keyword match): 99, 1.6M downloads. Top: Fantasy Statblocks 364k, Dice Roller 288k, Calendarium 200k, Initiative Tracker 165k, Zoom Map 90k.
• One author already runs a set: Johannes Schwartz, 7 plugins, 144k in all, but 90k of that is one (Zoom Map); the other six 2k-18k.
• Money in this niche: none of 5 top TTRPG READMEs checked sells a paid tier; Dice Roller has Buy Me a Coffee, Statblocks a sponsor link. A paid tier here is unproven.
• Answer given: about 5 in the run (3 free, 2 with a paid feature), one hit matters more than the count; checkpoint 30 days after Dice Tray is listed.
• Finished 01:37

01:49: how Obsidian works, the TTRPG plugin list, speech-to-text (boss question)

• Speech in Obsidian's list (same stats pull): Whisper 59k downloads, Transcription 33k, Audio Notes 29k, Scribe 21k, Smart Memos 9k, Vox 8k. All general dictation/transcription, mostly bring-your-own OpenAI key. Nothing that turns a tabletop session into campaign notes: the closest, Resonance, is a general recorder with 203 downloads.
• Outside Obsidian, people pay for exactly that. Archivist (myarchivist.ai/pricing, read today): Casual $10/mo 4 sessions, Seasoned $20/mo 10, Pro $35/mo 20, Legend $60/mo 40; 30-day trial; it imports from Obsidian, no export to it listed. Goblin Scribe (Discord bot, top.gg): free tier, paid tiers listed $7-30/mo, prices differ between listings. Loracle (Discord bot, top.gg): 3 free sessions, from $5/mo.
• A small one: dnd scrybe (trustmrr.com, verified revenue): $186 all time, $18 in the last 30 days, since May 2025. The idea alone does not sell.
• Answer: Dice Tray stays the free first one; a session-to-notes plugin is the best candidate for the paid one.
• Finished 01:50

01:54: will a dice roller get our name in front of players (boss question)

• Dice Roller (GitHub API): last release 11.4.2 on 2025-03-24, last push the same day, 79 open issues and PRs, 345 stars, 288k downloads.
• Dice plugins added since (Obsidian stats): RPG Detect Dice Roll 948, Interactive Dice for Atlas VTT 891, Dice Table Calculator 727, RPG Dice Roller 563, Dice Table 389, Dice Rolls 164, VTMV5 Dice Roller 142, Power Roll Detector 82. None past 1k.
• Answer: on its own, no. A new dice roller gets hundreds of downloads. Dice Tray is done, so it gets listed, but the session recorder becomes the main product.
• Finished 01:54

01:57: one plugin that bundles several table tools (boss idea)

• Bundles do far better than new single tools: Fantasy Content Generator 53k, Solo RPG Toolkit 39k, TTRPG UI Toolkit 31k, against under 1k for every dice plugin added since March 2025.
• The big single tools are one group's and slow (GitHub API): Statblocks last push 2026-01-21, 61 open; Calendarium 2025-09-27, 73 open; Initiative Tracker 2026-04-12, 78 open; Dice Roller 2025-03-24, 79 open.
• Names free in the list: GM Screen, GM Toolkit, GM Tray, DM Screen, Table Tray, Dice Tray.
• Answer: yes. Grow Dice Tray (not submitted yet, so the id can still change) into one plugin "GM Screen": dice and tables (done), initiative tracker with HP, session log; the session recorder later as its paid part. Repo rename needs the boss's yes.
• Finished 01:58

02:00: where Statblocks and Calendarium keep their data (boss question)

• Their doc site (plugins.javalent.com) does not say; read the source instead (shallow clones in the scratchpad, grep only).
• Fantasy Statblocks: a creature can be a plain note with statblock: true (or "inline") in its frontmatter, the stats in the frontmatter; src/watcher/watcher.ts reads them through the metadata cache. Also ```statblock code blocks in notes. Its homebrew and settings go to its own data.json via saveData, inside the vault's .obsidian folder.
• Calendarium: events are notes with fc-date / fc-end / fc-calendar / fc-category frontmatter (src/watcher/watcher.worker.ts); the calendars themselves (months, weekdays) are in its data.json.
• So the boss is right: the data is in the vault and GM Screen can read it in place, like Dice Tray reads dice: codes. The initiative tracker will pull HP, AC and initiative from Statblocks creature notes. Drawing full statblocks and calendars stays out for size, not for data.
• Finished 02:00

02:03: confirm before building GM Screen (boss order)

• Searches (Google autocomplete, suggestqueries; shows that a search is common, not how many): "obsidian dm screen", "obsidian dungeon master screen", "obsidian dnd dm screen", "obsidian initiative tracker" (+ "add players", "player view", "can't add creature"), "obsidian dnd dice", "obsidian dnd plugins", "obsidian dnd session notes", "dnd session recap ai", "dnd session summary ai", "is obsidian free for dungeon masters".
• Recording into Obsidian already exists. General: Advanced Audio Recorder 5,149 downloads, updated 24 Oct 2026, records on desktop, iOS and Android, transcribes with speaker labels (Deepgram, Gemini, Voxtral, Whisper, local whisper.cpp), optional AI summary. Scribe 20,605, record + transcribe + summarize. TTRPG: Archivist sells an Obsidian plugin with paid plans and exports campaigns back to Markdown (myarchivist.ai/tools/integrations); Recap Raven plugin (94) imports its service's recaps; Azer (296) does AI session recaps with your own Anthropic key; Saga20's plugin page now says "Plugin not found". A GitHub pipeline (dannysollo/dnd-transcriber) does Discord, Whisper, Claude, Obsidian wiki updates. What is missing is only a TTRPG layer on top: recap linked to existing NPC and place notes, in one install, no subscription.
• GM bundles already exist and new ones stay small: D&D Campaign Manager (session runner, initiative tracker; Sep 2026) 615; TTRPG Campaign Manager (May 2026) 2,266; RPG Manager (older) 48,547.
• Obsidian Developer policies (obsidianmd/obsidian-developer-docs, read today): payment for full access, accounts and network use are allowed if the README says so; no client-side telemetry, no ads loaded from the net; forks not allowed without the author's OK. Dice Tray is our own code, not a fork.
• Cost (developers.openai.com pricing, read today): gpt-4o-transcribe and the diarize model $0.006/min, gpt-4o-mini-transcribe $0.003/min, so a 4-hour session is $0.72-1.44; summary text under a cent. Uploads max 25 MB, long audio must be split; the diarize model shuts down 26 Feb 2027.
• Phones: plugins can record on iOS and Android (Advanced Audio Recorder README), but on iOS the screen must stay on while recording (Scribe README). Obsidian's own Audio recorder help page says nothing about mobile.
• Where play happens: no 2025 survey found. Sly Flourish polls: 2023 YouTube poll of 2,900 GMs 46% mostly in person, 41% mostly online, 13% both. Online tables already have Discord recap bots.
• Result: GM Screen as a free bundle stands (the searches are real). The recorder as the main paid product does not stand: general recorders already do the hard part inside Obsidian. Paid feature left open until GM Screen has users.
• Finished 02:05

02:12: DM Screen name and the free-plugins-plus-paid-hub idea (boss idea)

• "Dungeon Master" is a registered trademark: reg. 1815460, owner Wizards of the Coast LLC, class 28 (games), registered and renewed, status date 24 Apr 2024 (furm.com/trademarks/dungeon-master-74264094, read today). So the name says "DM", never "Dungeon Master" spelled out. "DM screen" is used by many third-party products (Hammerdog, Gale Force Nine), and the SRD says "GM".
• Names: no plugin in obsidian-releases is called DM Screen or GM Screen; the only "DM" name is "DM Kit Sync". Google autocomplete has "obsidian dm screen" and "obsidian dungeon master screen", nothing for "gm screen". Obsidian rules: id cannot contain "obsidian"; name cannot be only a core feature name.
• Plugins talking to each other: Obsidian's public Events API (app.workspace.trigger / on, since 0.9.7) and shared vault notes with frontmatter. Both work across separate plugins without a private API.
• Paid tiers inside Obsidian plugins exist and get installed: Copilot (2.99M downloads) sells Plus at $14.99/mo; Smart Connections (1.25M) is open-core with a Pro tier. No revenue figures published for either. Developer policies allow "payment required for full access" if the README says so.
• Small plugins: each new plugin usually gets hundreds of downloads (newest 2,000 median 75, p90 608), so several small ones add reach mainly through names people search (initiative tracker, dm screen, dice).
• Result: the boss's structure works. Small free plugins, each named for a search; a paid "DM Screen" hub that links them and adds session recording with recaps written into the campaign notes. Payment needs a pay URL from the boss (RULES 5).
• Finished 02:15

03:04: Second plugin, an initiative tracker that reads Statblocks notes (boss yes)

• Name check: Initiative Tracker (id initiative-tracker, 165k, maintained, last release 13.0.21 on 12 Apr 2026, 78 open issues: players duplicated on start, Statblocks sync, needs Dice Roller). Generic Initiative Tracker 10k (repo idle since 2022), Combat Ledger 2.3k, Initiative Tracker Plus 286. "Quick Initiative" / quick-initiative is free.
• Built app/plugins/quick-initiative: an initiative code block; the fight is plain text in the note and every change is written back into the block (keeps callout prefixes; leaves the note alone if the block moved). Roll, next/prev with rounds, skip creatures at 0 HP, damage/heal, conditions, add mid-fight, open creature note. Reads Fantasy Statblocks frontmatter (hp, ac, Dex from stats, hit_dice with the roll-HP setting). Fires quick-initiative:change for other plugins (the later DM Screen hub).
• Checks: 27 plugin tests pass, tsc and eslint (obsidianmd rules) clean, main.js 14 KB. Dice Tray 36 pass. Site 244 pass.
• Demo live: https://bulkhead.bananafest-destiny.com/press/quick-initiative/ (real plugin code, note text updates beside the tracker; checked in headless Chromium at 1200 and 390 wide, no page errors; visit tag present). Deployed.
• Repo https://github.com/walkertbrown/quick-initiative created (boss yes), release 0.1.0 with main.js, manifest.json, styles.css. Dice Tray README and demo page link to it; dice-tray mirror pushed.
• Not tested inside real Obsidian (not installed here). Submission waits on the boss's Obsidian account.
• Finished 03:21

05:07: Third plugin, a session log (check the field, then build)

• Checked the field first. Nothing has the id session-log. The closest plugins are TTRPG Campaign Manager (2,266 downloads, a whole campaign manager), Lonelog (5,841, solo-play notation) and Azer (296). None is a quick box you type into during play. Google suggests "obsidian dnd session notes template", "obsidian ttrpg session template" and "obsidian session notes template", so the New session note command answers the template search too.
• Built Session Log (session-log, 0.1.0) in app/plugins/session-log, set up the same way as Quick Initiative: - A session-log block becomes a box. Enter adds - 20:14 text #tag to an ordinary Markdown list under the block, so links still count as backlinks and tags still show in tag search. Quick tags have counts. - Commands: Add log entry (a modal, can be bound to a hotkey), New session note (Session N+1 in a folder, with the date and a link to the last session), Insert log block. - It listens for Quick Initiative's quick-initiative:change and logs when a fight starts, who goes down and when the fight ends ("Goblin ×3" grouping). This is the first piece of the bundle where one plugin talks to another. - 25 tests pass. tsc and eslint (obsidianmd rules) are clean.
• Demo: https://bulkhead.bananafest-destiny.com/press/session-log/ runs Session Log and Quick Initiative together. Headless Chromium at 1200 and 390 wide showed no page errors. A typed entry, roll, knock-out and end gave 7 entries and no "unsaved".
• Repo https://github.com/walkertbrown/session-log with release 0.1.0 (main.js, manifest.json, styles.css). Dice Tray and Quick Initiative READMEs and demo footers now link it, and all three mirrors are re-pushed. Site tests 244 passed, deploy done, commit 743d21d.
• To submit after the account exists: dice-tray, quick-initiative, session-log.
• Finished 05:24

05:30: Which small GM plugins come next (boss question)

• Checked obsidian-releases (name and description, downloads from stats.json) against Google autocomplete.
• Gaps (searched, nothing dedicated): - Encounter builder: "obsidian encounter builder" and "obsidian encounter table" are suggested. No dedicated plugin; Arroweds Adversary Bank (1,443) is the nearest. - Progress clocks: "obsidian progress clocks" is suggested. The only plugin with game clocks is Lancer Companion (315), which bundles them for one game. - Loot: "obsidian loot generator" is suggested. Only TTRPG Campaign Manager (2,266) mentions loot. Tables would need content we can legally ship, which is not checked yet.
• Taken, skip: - Names and NPCs: TTRPG Content Generator, 53,472. - Character sheets: TTRPG UI Toolkit, 30,678. - Soundboard: TTRPG Tools - Soundboard, 13,981. - Calendars and timelines: Charted Roots, 77,292; TTRPG Tools - Timeline, 18,198. - Taverns: Tavernus, 1,483.
• Told the boss: Encounter Builder next (it feeds Quick Initiative), then Progress Clocks.
• Finished 05:31

06:14: Fourth plugin, an encounter builder (boss yes)

• The SRD 5.2.1 (CC BY 4.0) has the encounter rules: XP budget per character for Low/Moderate/High by level, XP by CR, and a troubleshooting list. No group multiplier in these rules. Attribution is one set sentence; it is in the README and on the demo page, plus "5E compatible" only.
• Field: no plugin with id encounter-builder. But javalent's Initiative Tracker (164,780 downloads) already draws encounter blocks, so ours uses encounter-builder as the block name to avoid a clash. Compendio SRD 2024 (93) also has an encounter budget, sent to Initiative Tracker.
• Built app/plugins/encounter-builder: party lines (party 4x level 3 or Aria level 4), creature lines (3x [[Goblin Warrior]], Ogre cr 2, xp 450), CR read from the creature note's cr frontmatter. The block shows total XP, a bar marked at the three budgets, difficulty badge, rows with − / + that edit the count in the note, an add box, SRD-based warnings, and Start fight, which writes a Quick Initiative block under it (once). Default party setting. Callout-safe edits.
• 30 tests (both SRD worked examples included), tsc and eslint clean. Site tests 244 pass. Demo at https://bulkhead.bananafest-destiny.com/press/encounter-builder/ runs it with Quick Initiative; checked in a browser, no errors, no sideways scroll on a phone.
• Repo https://github.com/walkertbrown/encounter-builder, release 0.1.0 (main.js 13,073 bytes). Cross-links added to the other three READMEs and demo footers; all four mirrors pushed.
• The boss asked where to sign up: https://community.obsidian.md, sign in with an Obsidian account, link GitHub, add each repo. Then "give me the file"; I asked which file the form wants.
• Finished 06:34

06:34: Fifth plugin, progress clocks

• Field: the only clocks for games in the directory are inside Lancer Companion (315 downloads); progress-clocks was a free id. Built app/plugins/progress-clocks: a clocks block, one clock per line (Alarm 1/4 red), vs for a racing pair, # headings for groups, [[links]], 2 to 12 segments. Click a segment to fill up to it, click again to clear; + and −, arrow keys; a full clock glows and gives a notice; each change fires progress-clocks:change. 26 tests, tsc and eslint clean.
• Demo: https://bulkhead.bananafest-destiny.com/press/progress-clocks/ (heist sample with generic names, no Blades setting names). Checked at 1200 and 390 wide, no errors, no sideways scroll.
• Repo https://github.com/walkertbrown/progress-clocks, release 0.1.0 (main.js 8151, manifest 337, styles 5261). Cross-links in the other four READMEs and demo footers.
• The boss said "all in, review pending" (in FACTS). The four plugins already show on community.obsidian.md with Add to Obsidian; Dice Tray has its first download and Review Passed. The other three were Satisfactory, held down by one medium warning, !important in the CSS. Removed it everywhere (higher selectors instead, demos look the same) and released encounter-builder, quick-initiative and session-log 0.1.1. The remaining note is info only: no GitHub artifact attestations.
• Site tests 244 pass, deployed, commit pushed, five mirrors pushed. Progress Clocks still needs the boss to add it on community.obsidian.md.
• Finished 07:06

07:12: Rename Progress Clocks to Tabletop Clocks

• Found by accident while reading post rules: community.obsidian.md/plugins/progress-clocks already belongs to tokenshift's Progress Clocks (sidebar clocks, counters, stopwatches; last updated Jan 2025). The legacy community-plugins.json doesn't list it, which is why my name check missed it. The boss would have hit a clash on submit.
• Renamed ours to Tabletop Clocks, id tabletop-clocks (directory says "Plugin not found" for it). Folder, manifest, package, class, event (tabletop-clocks:change), README, demo page and the cross-links in the other four READMEs and demo footers. The clocks block stays; theirs uses inline code, not blocks.
• README gained a Credit section: progress clocks come from John Harper's Blades in the Dark, not affiliated.
• 26 tests pass, tsc and eslint clean, build 8151 bytes. Demo moved to https://bulkhead.bananafest-destiny.com/press/tabletop-clocks/ (200); the old /press/progress-clocks/ 301s there. Deployed.
• GitHub repo renamed by API to https://github.com/walkertbrown/tabletop-clocks (old URL redirects). The folder move gave the subtree split a new history, so the mirror was force-pushed (ours, made today, never submitted), the old 0.1.0 release and tag deleted, and a new 0.1.0 made with main.js, manifest.json and styles.css.
• All five mirrors pushed for the README links.
• Finished 07:14

07:07: Launch posts for the five plugins (drafts for the boss)

• Rules read today in headless Chromium (Reddit 403s this server otherwise) and in Obsidian's docs; written into LEARNED.md. Result: the Obsidian forum's Share & showcase is the one place that asks for announcements. r/ObsidianMD bans AI-generated posts and bans anyone whose first post promotes their project, so we stay out. r/rpg only through its weekly self-promo thread. r/DMAcademy needs a history there first. r/bladesinthedark fits Tabletop Clocks only, once it is listed.
• The rename to Tabletop Clocks came out of this (see the entry above).
• 0.1.1 not rescanned yet: QI, SL and EB still show 0.1.0 and Satisfactory.
• Drafts given to the boss in chat: one forum topic for the four live plugins, one r/rpg weekly-thread comment, one r/bladesinthedark post plus link comment held until Tabletop Clocks is listed, and a one-line truthful answer if anyone asks about AI. Nothing posted by me.
• Finished 07:15

07:21: Encounter Builder !important warning the boss saw

• Lines 196 and 304 of the 0.1.0 release's styles.css are the two !important rules (height: 28px, color: text-on-accent). The 0.1.1 release's styles.css has none, and neither does the source. main's manifest says 0.1.1 for EB, QI and SL.
• The directory still lists 0.1.0 for EB, so the warning the boss saw is the old scan. Obsidian's release docs don't say when or how the directory rescans an update. Asked the boss whether their dashboard has a rescan or update button.
• Finished 07:21

07:25: Check the directory after the boss's release check

• All four pages are up. The release list on QI, SL and EB now includes 0.1.1, but "Current version" still says 0.1.0 and the Review (Satisfactory, the !important warning) is still the 0.1.0 scan. Dice Tray: Passed, info only.
• Obsidian's app updates from the manifest on GitHub, so users get 0.1.1 (the boss confirms updates work). The directory's review badge is just behind.
• tabletop-clocks: "Plugin not found", so it is not listed yet (not submitted, or in review).
• Finished 07:25

07:35: Forum account on hold

• The boss posted the Dice Tray thread (disclaimer filled, vibe-coded: Yes). The forum's automatic check held the new account for staff review. The profile then gave the reason: "New user typed too fast" (pasting the whole first post at once). Told the boss to wait and not repost. Forum template rules written into LEARNED.md.
• Finished 07:35

07:40: How new plugins get seen

• obsidianstats has no page for ours yet (404). Its weekly roundups count about 250 new plugins a week, so a listing there won't be noticed. It reads community-plugins.json, which a bot mirrors from the directory every hour or two; our four weren't in it as of the 06:33Z mirror.
• Asked the boss whether "Dice Tray" shows up in the app's own Browse search, which tells us whether the app reads that file or the new directory.
• Finished 07:41

07:49: Why the app's Browse can't find Dice Tray

• The boss has Obsidian on a Mac now. Browse search "dice tray": 0 results. So the app reads community-plugins.json, not the new directory.
• The mirror bot added 15 plugins at 05:22Z and 06:33Z, all updated 28 Oct; some have Satisfactory reviews and some lack attestations, so neither blocks the mirror. Ours just weren't live yet when it last ran. Dice Tray's page already shows 2 installations (from the directory's Add button).
• Next mirror run is due within an hour or two; watching for dice-tray in the file.
• Finished 07:50

07:54: Who covers running games in Obsidian

• Read the Obsidian Hub TTRPG page (its repo is archived, so no edits), the TTRPG Discord's listing, obsidianstats' ttrpg tag (8 plugins, no submission form), and Josh Plunkett's numbers (15.2K subscribers on Social Blade, plugin list on Patreon).
• Wrote the findings into LEARNED.md. Drafted a note to Josh Plunkett and a Discord message for the boss, in chat. Nothing sent by me.
• The app's Browse list still doesn't have our plugins; the watcher keeps checking.
• Finished 07:57

08:03: Is the DM Screen the thing to build now

• Answer: yes, the DM Screen goes next. The small plugins stay free and listed, and they feed it.
• Scribe (20k downloads) already does generic record, transcribe and summarize, so the DM Screen has to win on campaign-aware recaps. Obsidian policy allows payment if the README discloses it.
• The ask that's still open: where the license is sold (a pay URL, §5).
• Finished 08:04

08:05: What the other plugins do that ours don't

• Read Dice Roller's README, Initiative Tracker's README and source tree, and tokenshift's Progress Clocks README. Took download counts from community-plugin-stats.json.
• Listed the gaps in LEARNED.md and answered the boss: the big two do much more, and ours only differ in keeping state as text.
• Finished 08:06

08:16: Restarted; read HANDOFF, check the Browse listing and mail, then carry on with Dice Tray 0.2.0

• community-plugins.json: last mirror 06:33Z, ours not in it yet. mail/in empty.
• Dice Tray, part of 0.2.0 (not released): narrative pools (Genesys/SWRPG) get their own chip; isNarrative now lets the ordinary parser decide when a "d" is followed by a digit, so 2g2d1s reads as a pool; Fantasy AGE 1dS shows stunt points and marks the stunt die; formulas read fields from their note (frontmatter, field:: n, [field:: n]); the roll modal reads them from the open note. Rolls that name no field still land at once.
• Tests 52 passed (was 36); tsc, eslint and build clean.
• Boss mid-turn: "Then we need to figure out a differentiator. We need to make ours different from theres". Parity stops here until that is answered.
• Finished 08:19

08:25: A second differentiator, on top of the self-writing note

• Looked (WebSearch, community.obsidian.md, 28 Oct). Player-facing views today are windows on the GM's computer: TTRPG Tools: Player Screen is a pop-out window for a second monitor, TV or projector; Javalent's Image Window likewise. Initiative Tracker Plus (a fork) has a player view, how it's shown not stated. Javalent's README and docs page I fetched didn't describe a player view at all.
• Closest to a link for players: Atlas VTT Connect (441 downloads, desktop only): players join from a web page by link, but it shows an Atlas VTT map scene, peer to peer over PeerJS. Not initiative, clocks or rolls.
• Proposed to the boss: the table on the players' phones. A link or QR code, nothing to install, showing whose turn it is, clocks filling, rolls made in the open and handouts revealed, live. It goes in the paid DM Screen (a relay costs money to run, which is a fair reason to pay). Opt-in, and the README says what goes over the network, as Obsidian's policy wants.
• Finished 08:25

08:32: Dice Tray: a clicked roll goes into the session log

• Done as an event instead of Dice Tray writing the note itself: Dice Tray triggers dice-tray:roll ({sourcePath, expression, text}) on a click or a modal roll, never on the roll a note makes as it opens. Session Log already hears quick-initiative:change the same way, so one plugin decides where the log is: the same note's log, else the last log used. New Session Log setting "Log rolls", on by default. The event is also the API item from the parity list.
• Logged text has the dice and the field values written in: Rolled 1d20 + dex -> [17] + 3 -> 20; note rolls log as Rolled [[Encounters#Forest]]: Wolves.
• READMEs: Dice Tray gets Narrative dice and "Into your session log" sections plus the new notation rows; Session Log gets a Rolls section.
• Tests: Dice Tray 54 passed, Session Log 26 passed; tsc, eslint and build clean for both. Not released yet: next is a roll that keeps its result in the note, then one release of both.
• Finished 08:34

08:35: Dice Tray: rolls that keep their result in the note (dice+ and dice-mod)

• dice+: 1d20 + 5 rolls once and writes the result into the note after it (dice+: 1d20 + 5 -> [17] + 5 -> 22); on open the chip shows the saved total and does not roll; a click rerolls, rewrites and logs. Two identical copies in one paragraph each save to their own spot.
• dice-mod: 4d6dl1 rolls once and replaces itself with the plain line (4d6dl1 -> [5, 4, 3] -> 12). With no section info (source mode, embeds) both just roll and write nothing.
• Writes go through vault.process on the section's lines only. README gains "Rolls that stay"; both are off the "Not yet" line.
• 59 Dice Tray tests, tsc, eslint, build clean. Release 0.2.0 next, with Session Log 0.2.0.
• Mail: docent asked about /api/crew/tell (POST only, needs a session, GET is 404, checked from outside), the 200s on expired bellok/wright/unbell links (agreed to make them 410, next work wake) and the public .aab (deliberate, the boss uploads it by hand; comes down once 1.8 is live). Replied, filed.
• Finished 08:42

08:42: Release Dice Tray 0.2.0 and Session Log 0.2.0

• Bumped both to 0.2.0 (manifest, package, versions.json; min app 1.13.0), built, committed, mirrors pushed by subtree split.
• Releases 0.2.0 on github.com/walkertbrown/dice-tray and github.com/walkertbrown/session-log, each with main.js, manifest.json and styles.css. Checked from outside: raw manifest on main says 0.2.0 and the latest release is 0.2.0 with all three files for both.
• The earlier session's release commands weren't in the log; used the same API pattern as the Bulkhead releases.
• Obsidian offers the update from the GitHub manifest, so anyone with them installed gets 0.2.0 on their next update check. The demo pages still run 0.1 code; rebuilding them is next.
• Finished 08:44

08:44: Demo pages show 0.2.0

• Dice Tray demo (/press/dice-tray/): new section "From your character, and other games" with 1d20 + str reading str:: 4 from the note, a Genesys pool, a Fantasy AGE stunt die and a saved dice+: roll; and an "Into your session log" box that shows the line each clicked roll would write.
• Session Log demo (/press/session-log/): bundles the real Dice Tray too. The Fight section has the bugbear's dice: 1d20 + 4 for dice: 2d8 + 2; a click puts "Rolled 1d20 + 4 -> [14] + 4 -> 18" in the log and in the note text beside it. One tip line added.
• Headless Chromium was missing (cache wiped); reinstalled with npx playwright install chromium. The daily needs it too.
• Site tests 244 passed, exit 0. Deployed. Checked both pages live in Chromium: rolls render, clicks land in the log, no page errors.
• Mail: docent confirmed /api/crew/tell from the zone's edge log (POST only, no GETs); no reply needed. Filed.
• Finished 08:54

08:54: Expired crew links answer 410

• worker/index.ts: the refusal on unbell (HTML page), bellok and wright (plain text) now has status 410; the body is unchanged and a live link still gets 200.
• Site tests 244 passed, exit 0. Deployed. From outside with a dead code: unbell 410, bellok 410, wright 410, same text; /api/crew/tell GET still 404.
• Told docent (no reply needed). Its edge-log read says 17 POSTs to /api/crew/tell in 7 days, so Hullbound episodes are still being finished on the web.
• Finished 09:03

09:03: The fight writes itself: rounds, damage and conditions into the log

• community-plugins.json has dice-tray, quick-initiative, session-log and encounter-builder (checked 09:03), so Browse in the app finds them.
• Quick Initiative 0.2.0: the change event now carries each combatant's conditions.
• Session Log 0.3.0: new setting Log the whole fight (on). Besides start, down and end it writes "Round 2", "Bugbear takes 9 (18/27)", "Aria heals 7 (31/31)", "Aria is back up (5 left)", "Borin is poisoned", "Borin is no longer poisoned". With an older QI that sends no conditions, nothing is logged for them. Off gives the old three lines.
• Tests: SL 28, QI 27; tsc, eslint, build clean. READMEs updated. Site tests 244 passed, exit 0. Deployed; the live Session Log demo logs "Bugbear takes 9 (18/27)" after a -9 in Chromium, no page errors.
• Mail: docent verified the three 410s from outside; it raised whether the visit counter belongs on the stop-mail page, as a question for the boss. Filed.
• Finished 09:14

09:15: Our plugins on a phone

• Phone check (Pixel 7, touch, Chromium) on all five demos: no sideways scroll, no page errors.
• Reddit asks checked: mobile PDF export exists (Mobile Export); phone reminders need a companion app (Notelert, ntfy, a Mac Reminders sync). Not a gap for us. Written into LEARNED with links.
• Dice Tray 0.2.1: on a screen with no hover, a tap rolls and shows the dice for 4 seconds, one card open at a time, moved left so it stays on screen (measured against the screen width, because a phone widens the page first). Genesys and Star Wars pools now get a card listing each die too, instead of only a tooltip. 60 tests pass (one new), 244 site tests pass. Demos rebuilt and deployed; the live demo.js and styles.css carry the fix.
• Finished 09:30

09:36: Clocks into the session log

• Boss: "I submitted the clocks already." In FACTS. tabletop-clocks isn't in community-plugins.json yet, but its community.obsidian.md page is up (fetched 28 Oct), so all five are in.
• Session Log 0.4.0: a clock tick from Tabletop Clocks goes into the log as "The trail goes cold: 2/4", "...: full (4/4)", "...: back to 1/4", "...: cleared", keeping a [[link]] name. I first wrote "ticks to", but clock names are often phrases and "The trail goes cold ticks to 2/4" reads badly, so it's a colon now. New setting Log clocks, on by default. 31 tests pass (3 new).
• Tabletop Clocks needed no code change (its event already carried previous and filled); its README now says Session Log hears it.
• The Session Log demo now runs the real Tabletop Clocks too: a clock under ## Clocks, and clicking segments writes the lines (checked in Chromium, no errors). 244 site tests pass; deployed and live.
• Finished 09:48

09:52: The table on the players' phones: relay and player page

• Built and deployed the relay and the players' page. The worker has a new Durable Object, Table, one per room (migration v3). POST /api/table/open gives a room name (10 letters with no 0/o/1/l/i lookalikes) and a secret; only the secret's hash is kept. PUT /api/table/<room> with the secret sends the table: turn order, whose turn, round, scene, clocks, the last rolls. GET reads it, and a WebSocket gets each new one (hibernating, so a quiet table costs nothing). DELETE closes the room, and an untouched room clears itself after 12 hours. Every field is cut to a known shape and size (src/table/room.ts, 32 KB cap); writes from another site's pages are refused; nothing is logged.
• Players' page: /table/#<room>, phone first, drawn as text only. It shows whose turn it is in big type, the order with what HP the GM chose to show, conditions, clocks as pies, and the rolls with how long ago. It reconnects when the phone wakes, and says so when the GM closes the table or the link is dead.
• Tests: 7 new (test/table.test.ts); the site run is 251 passed. Checked locally under wrangler dev, then live on a Pixel 7 profile: the page followed a turn change and a clock tick without a reload, stayed 412 wide, and showed "Your GM closed this table." when the room closed; a dead room answers 404.
• Not yet: the GM side. The DM Screen plugin opens the room, shows the QR code, and sends the table from Quick Initiative, Tabletop Clocks and Dice Tray. Opt-in, with the README saying what goes over the network.
• Finished 10:07

10:07: DM Screen, first cut: share the table

• app/plugins/dm-screen (0.1.0): "Share the table with players" (command, ribbon, status bar) opens a room on the relay, saves it, seeds clocks from the open note's clocks blocks, and shows a window with a QR code, the link, Copy link, Stop sharing, "N phones watching" and a Scene line. From then on it listens to quick-initiative:change, tabletop-clocks:change and dice-tray:roll and sends the table 250ms after things settle. Settings: player hit points on/off, monster hit points as words (hurt, bloodied, down), numbers or hidden, how many recent rolls.
• A room that closed itself (12 quiet hours) is noticed on the next send and the GM is told to share again.
• README has a Network use section: the maker's server, only while sharing, gone on stop or after 12h, only the last table and a hash of the key kept, no accounts, logs or addresses.
• 12 plugin tests; tsc, eslint and build clean. Site tests 251 passed.
• Demo at /press/dm-screen/ runs real DM Screen, Quick Initiative, Dice Tray and Tabletop Clocks over a sample note, against the real relay, with the players' page in a phone frame beside it. A visitor leaving closes their room.
• Checked live with playwright: share, QR and link; phone shows the clocks before the fight; roll initiative, hurt the Bugbear (phone says bloodied, no numbers), tick a clock, click a roll, all show on the phone; 1 phone watching; scene line; Stop sharing shows "Your GM closed this table." on the phone.
• Not submitted, no mirror repo, nothing asks for money.
• Finished 10:23

10:23: DM Screen: handouts on the players' phones

• Relay: a room can hold one picture (/api/table/<room>/image), JPEG, PNG or WebP only (SVG refused, it can carry script), 1MB cap, same key as the table, served with nosniff and a no-script CSP, deleted with the room. The table carries a handout (title, words with their line breaks up to 4000 characters, the picture's version).
• Players' page: the handout sits at the top on a paper-coloured card; tap the picture for full size.
• DM Screen: "Show to players" in a picture's or note's file menu and the editor menu (selected text), commands for the note, the selection and hiding. A note shows its words with properties, %% comments %% and code blocks left behind, links as their words, and its first embedded picture. Pictures are shrunk in Obsidian to 1600px JPEG under 1MB before they leave. Hiding deletes the picture from the room. Showing starts sharing if it hadn't. The share window says what is showing, with a Hide button.
• Tests: plugin 18, site 253, all pass; tsc, eslint, build clean. README has a Handouts section and the Network use section covers pictures.
• Demo: "Show the letter" (a note with a property and a GM comment, both kept back) and "Show the map" (a 2000px PNG drawn in the page, arrives as 1600x1120 JPEG, about 48KB).
• Checked live with playwright: letter and map on the phone, Hide clears the card and the picture answers 404. With curl on a throwaway room: SVG 415, 2MB 413, wrong key 403, another site 403, after close 404.
• Finished 10:40

10:40: Dice Tray: a dice panel in the sidebar

• Dice Roller's README (raw.githubusercontent.com/javalent/dice-roller/main/README.md) shows its Dice View: buttons for each die, advantage and disadvantage, a modifier, a formula box, saved formulas, 3D dice. I found no roll history in it.
• Dice Tray 0.3.0 adds a dice panel in the sidebar (ribbon icon, or "Open the dice panel"). It has d4 to d100 plus Fate dice: a tap adds a die, a right-click takes one away. It has − and + for the modifier, Adv and Dis, and a formula box. Roll, Clear and Save are there, with saved formulas as chips you can remove with ×, and "This session", which keeps the last 50 rolls; a click rolls one again. Panel rolls are announced as dice-tray:roll, so they go into Session Log and onto the players' phones.
• Advantage on more than one d20 is ignored rather than guessed at.
• Fixed along the way: the detail line in the roll window dropped the modifier ("2d6 [2, 3] = 6" for 2d6 + 1). Typed rolls now show "2d6 + 1 -> [2, 3] + 1 -> 6".
• 67 plugin tests (4 new panel tests and 3 pool tests); tsc, eslint and build clean. Site run: 253 passed, exit 0.
• The demo at /press/dice-tray/ has a "The dice panel" section running the real panel. Checked live in playwright: 8 dice, two d6s plus 1 gives "2d6 + 1", a roll lands in the panel, in This session and in the session log box, and there were no page errors.
• README: a new "The dice panel" section; "Not yet" now lists only tag rolls.
• Finished 10:55

10:55: Dice Tray: rolls in Live Preview

• Dice Roller draws rolls in Live Preview in src/processor/live-preview.ts (github.com/Obsidian-TTRPG-Community/dice-roller, which javalent/dice-roller now redirects to). It uses a CodeMirror ViewPlugin that walks the syntax tree for inline-code nodes and skips any the selection touches. Mine is my own code, written against Dice Tray's chips.
• Dice Tray 0.4.0, src/live.ts: a ViewPlugin replaces each dice: inline code with the same chip as reading view while the cursor is elsewhere, in Live Preview only (editorLivePreviewField); source mode is left alone. The widget's eq() keeps a chip's DOM, so typing elsewhere doesn't reroll it. ignoreEvent means a click rolls again instead of moving the cursor. dice+: and dice-mod: write back through the editor (a change at posAtDOM, only if the code there is unchanged), one tick after drawing.
• It reads both Obsidian's tree names (inline-code) and lezer markdown's (InlineCode), so the tests run against a real CodeMirror editor: 6 new tests (finding, chips vs cursor, source mode, keep-on-typing plus click, dice+ write and stay, dice-mod replace). 73 plugin tests; tsc, eslint and build clean; main.js is 31KB, with @codemirror/language and view kept external.
• Dev dependencies, pinned: @codemirror/language 6.13.1 and lang-markdown 6.5.2, both over two weeks old, plus state 6.7.6 and view 6.43.13 to match Obsidian's peers.
• The demo has a "While you write" section with a real editor (the demo bundle is now 305KB, from 35KB, all CodeMirror). Checked live: 4 chips; arrowing in shows the code; a click rolls and lands in the session log box; no errors. The panel is still fine.
• Site run 253 passed, exit 0. Deployed.
• Finished 11:09

11:09: Dice Tray: rolls on a tag

• Dice Tray 0.5.0: dice: #npc rolls on every note with the tag, |- on one random note, |link gives a link to one, and 2d#npc takes two parts. Tags come from Obsidian's own cache, so body tags, frontmatter tags and nested tags (#npc/elf) all count, with no Dataview needed. The note the roll is in is left out. Lines that hold only tags are no longer picked, which also helps [[Note]] rolls.
• Dice Roller does this through Dataview (its README, "Tag Rollers" and "Links").
• README: "## Rolling on a tag" added, and "Not yet" removed. The demo has a "From your tags" section with three NPC notes.
• Checks: 74 plugin tests, tsc, eslint and the build pass. Site tests: 253 passed, exit 0. Deployed. Live /press/dice-tray/: 1 tag chip; three runs of 3 clicks each picked Mira, Tobin and Old Hesk; each roll landed in the log; no page errors. The panel and Live Preview checks still pass live.
• The 28 Oct daily ran on its own (11:09 to 11:15Z) and committed itself as 4bb6146: Farthing Station, 2 decks, Bluesky posted (the URL is in meta.json). Status: all 31 clear.
• Finished 11:23

11:53: DM Screen: decide the price, the repo and how it is paid for

• The boss left it to me: "It's up to you. It's your product". Written into FACTS with the three pages I read (Obsidian's blog and developer policies, Bases Power Pack, itch's download_keys lookup).
• Decided (LEARNED, "How DM Screen is sold"): open source, MIT, public repo walkertbrown/dm-screen, because Obsidian takes no new closed-source plugins. Labelled "Paid" with a free trial: a one-hour room for free, 12 hours with a key. $12 one-time on itch. The key is the buyer's itch download key, checked by the worker.
• Still needed from the boss: the itch page (their account). Asked in chat.
• Finished 11:55

12:39: DM Screen: the key and the one-hour trial

• Built as planned. The worker has a new Keys object (migration v4). It asks itch once whether a key is a DM Screen download key and keeps only a hash. A key opens at most 20 tables a UTC day. A table without a key gets an alarm one hour out and closes with code 4001; the players' page says the free hour is over. "Lost your key?" asks itch for that address's key and mails it, once an hour per address, and always answers the same, so it never says whether an address bought.
• The trial only turns on once itch lists a published game titled "DM Screen". The link the plugin shows comes from itch's API, and it is the URL the boss gave. Until then every table stays open all evening, so nothing asks for money before the page is public.
• Plugin 0.2.0: a Key row with a Check button, a "Lost your key?" row, a trial line and "Get a key" in the share window, and a Payment section in the README ("Payment is required for full access.").
• Tests: plugin 23/23, with tsc, eslint and the build clean. Site 257 passed, exit 0. The worker passes strict tsc.
• Deployed. Live: the kit page /press/dm-screen/itch/, the zip (14 KB) and the screenshot all return 200. POST /api/table/key with a made-up key returns {ok:false, sold:false}. The demo share check passes end to end: link, QR, turn, clocks, rolls, scene, stop. No errors.
• The repo walkertbrown/dm-screen was made public (MIT). The boss has the itch page as a draft, with no descriptions yet. The kit link goes to them now.
• Finished 12:52

13:07: DM Screen: check the itch page and the trial live, then the next gap

• At the first look the itch page was a draft. I tested Keys against a pretend itch instead, in 6 tests: before the page is public nothing asks for money; no key and a bad key get the trial and the buy link; a download page address is asked of itch once and kept only as a hash; the 21st table in a day is stopped; "Lost your key?" mails a buyer once an hour and answers the same for anyone, keeping no address.
• Found and fixed: if itch's API was down, a buyer's key not yet remembered got "itch doesn't know that key" and the trial. Now, while itch can't be asked, a key is taken on trust and not remembered. Tested.
• Site 263 passed, exit 0. Deployed. Live: the itch API shows DM Screen published at 13:08Z, 2, with cover and short text, and the page shows Buy Now and dm-screen.zip. /api/table/key with a made-up key returns ok:false, sold:true, with the buy link the boss gave. A keyless /api/table/open now carries trial.ends 59 min out. The paywall is on.
• Quick Initiative 0.3.0, the party: a Party setting (a textarea: one player per line in the block format). A line that says party in a block brings them in as players. The first change writes them into the note, and Insert initiative block starts with party once one is set. 30/30 tests, tsc, eslint and the build clean. Initiative Tracker's party was the gap that costs a DM Screen buyer the most typing every fight.
• The boss asked for the repo name and how charging works on Obsidian. I read the 12 May blog: Paid label, not a store, the dashboard sets pricing.
• Finished 13:18

13:35: The boss said "do it all": the order, and Encounter Builder's Pathfinder 2e first

• Encounter Builder 0.2.0 does Pathfinder 2e. Add system pf2e to a fight block, or pick it under Settings → Rules. The meter then has GM Core's five steps (Trivial 40, Low 60, Moderate 80, Severe 120, Extreme 160 for four characters, adjusted by 10/20/20/30/40 per character). Creatures count by level against the party level, from 4 below to 4 above. It warns about mixed levels and creatures off the table. The figures were read on Archives of Nethys (GM Core pp. 75-76) the same day, and the ORC/Paizo credit is in the README and on the demo.
• Plugin: 41 tests, tsc, eslint and the build are clean. Site: Tests 263 passed (263), exit 0.
• The demo (/press/encounter-builder/) has a Pathfinder 2e button with its own sample note. It is deployed and checked live with no errors.
• Mirrored to walkertbrown/encounter-builder; release 0.2.0 has main.js, manifest.json and styles.css.
• Finished 13:52

13:43: Tabletop Clocks: counters and stopwatches

• Tabletop Clocks 0.2.0 adds counters and stopwatches. - A counter is Arrows: 18 of 20: − and + buttons, arrow keys, and a bar when it has a max. - A stopwatch is Ritual: 4:12 of 10:00: play/pause and reset. Its start time is kept in the plugin's data by note and name, so it keeps running across notes and restarts. Pausing writes the time into the note. It gives a time's-up notice once. - New events tabletop-clocks:count and tabletop-clocks:stopwatch. :change stays for clocks only, so Session Log and DM Screen are unaffected.
• One bug was found in the browser demo, not by the tests: pausing redrew from the note before the running mark cleared, so the time counted twice. The mark is now set first.
• 35 plugin tests are clean. The demo (/press/tabletop-clocks/) has a counter and a stopwatch in the sample; it is deployed and checked live with no errors. Mirrored, release 0.2.0 with 3 assets. README: new section, the events and privacy (the stopwatch start times).
• Finished 13:52

13:52: DM Screen: a battle map on the players' phones

• DM Screen 0.3.0: a battlemap code block draws a picture from the vault (or a plain grid) with tokens on it. The plan said a map block; I used battlemap because map is too likely to clash with other plugins' blocks.
• The first line is ![[picture]] 12x8 or grid 12x8; each token line is name [cell] [colour] [hidden]. Tokens move by drag, by click then square, or by arrow keys, and Delete sets one beside the map. Every move is written back into the note's text, so the note stays the record.
• "Show to players" sends the map to the table room; the players' phones show it under the turn order. Hidden tokens and tokens beside the map never leave the vault. The picture is shrunk and sent once; moves send only the token list. The token whose turn it is in Quick Initiative gets a ring, and a token at 0 hp is dimmed.
• Worker and room: a second picture slot, map, beside the handout (same 1 MB limit and type check), dropped when the room closes. 2 new table tests.
• Demo page: a cellar map drawn on a canvas in code (no AI), under the tracker. DM Screen's test shim needed stubs for the newer Dice Tray and Tabletop Clocks imports so all four plugins still bundle into the demo.
• Checks: 37 plugin tests, tsc, eslint, build; site tests 265 passed (265); local browser check of drag, keys, Delete and the ring; live check after deploy: the phone gets the map, the hidden Bugbear stays off it, a drag reaches the phone, the ring follows the turn, Hide clears it.
• The itch download (dm-screen.zip) is rebuilt at 0.3.0. The boss needs to upload the new zip on itch; I will batch that ask.
• Boss, during the tests: "after this is finished, I want to look into solo ttrpgs", with Reddit speculation that solo play is about to take off, and that it may be separate from Obsidian. In FACTS. Research comes next, before Dice Tray.
• Finished 14:14

14:14: Solo TTRPGs: what players use, what they pay for, what is missing

• Read: Obsidian's own download stats for every solo plugin; itch's solo top sellers (games and tools); the App Store and itch pages for Mythic GME Mobile, PUM Companion, One Page Solo Engine, Traveler's Ironsworn and Solo-Explorer; the Datasworn licence. Reddit blocks my reads, so the subreddit size is GummySearch's figure (about 77k).
• Found: the money in solo is in the games (journaling and drawing games at $3-15 lead itch's 1,093 solo top sellers). Solo tools are a small, crowded shelf: 28 tools on itch, several oracle phone apps at $3-13, and inside Obsidian solo-rpg-toolkit (38.9k downloads) and iron-vault (20.7k, free). Details and links are in LEARNED, "Solo TTRPGs, first look".
• My read for the boss: if we go solo, make a solo game people play on their phone, not another oracle tool; that would be separate from Obsidian. Asked the boss for the Reddit threads they saw.
• Finished 14:17

14:28: Solo, part two: the r/rpg predictions thread and "what should I play" requests

• The plan entry was written after I had started reading the thread, so it is late.
• Read the thread in a headless browser (Reddit blocks plain fetches). About seven of 36 top-level replies agree solo will grow, one says it's observer bias, and at least five are hostile to AI.
• Logged out, Reddit served the "Game Suggestion" list from mid-September, not this week: 24 posts in about 3.5 days, most with 10 to 100 replies.
• The finders that exist browse by category or tag; none takes a request in the asker's own words. Details are in LEARNED, "Solo, part two".
• Finished 14:28

14:31: Dice Tray: dice that tumble in 3D, and a roll API for other plugins

• Dice Tray 0.6.0. New src/solids.ts: the six dice as solids built from one "faces from the directions they face" routine, and the turn that brings any face to the front with its number upright. New src/tray3d.ts: a canvas over the window that clicks pass through; the dice fly in from the right, spin down onto the rolled faces near the chip and lie still about 1.4 s, then fade. Drawn in code in the theme's accent colour; no new dependency, no AI art.
• First test run caught the d12 and d20 using the wrong-handed partner solid for their face directions (one corner per face); fixed with the other orientation. d100 groups are faces "100", not "%", so the d100 mapping missed them at first; fixed.
• Landed dice first faced straight on, so a d6 read as a flat square. Now they lean back a little, less on the many-sided dice so the rolled face stays the most frontal (on the d20 the first lean made a neighbouring face look like the result).
• Fate dice as d6 with − opposite +, blank opposite blank.
• Only rolls you make throw dice: a click on a chip (the number waits for the dice), the panel and the roll window. Note-open rolls never do, nor more than 20 dice. Setting "Throw dice", on by default; off under reduced motion.
• API: plugin.api.roll(expression, {sourcePath, show, announce}) gives total, text and each die; api.average(). README sections for both.
• Tests: dice-tray 95 passed (new: face counts and flatness per die, each face turned to the front upright, the dice thrown for a roll, the API). DM Screen 37 passed (its shim needed activeDocument). Site 265 passed, exit 0. Deployed; live demo threw dice on 2d20kh1, 2d6, 4dF and d% with no page errors (screenshots viewed).
• Finished 14:49

14:50: Encounter Builder: the free SRD 5.2.1 monsters, by name

• Encounter Builder 0.3.0: the 329 monsters of the SRD 5.2.1 are built in by name. "Owlbear", "2x Goblin Warrior" or "3x Wolves" rates with no note and no cr. The add box suggests all 329 names, and hovering the CR shows size, type, AC and HP.
• Different from the plan: besides the name, CR, size and type, it also keeps AC, HP and initiative, so Start fight can hand Quick Initiative real numbers ("2x Owlbear hp 59 ac 13 init +1"). It still keeps no stat blocks. Your own numbers win: a cr or xp on the line, or a linked note, beats the SRD.
• Attribution: the plan said "say we are not endorsed", but the SRD PDF asks for no other attribution to Wizards beyond its statement. So the README, the release notes and the demo page carry only that statement, word for word, plus "5E compatible", which the PDF allows.
• Parse: per-column pdftotext of the SRD PDF, pages 250-364, gave 329 monsters with 0 bad rows. Spot checks against the PDF: Owlbear CR 3 AC 13 HP 59 +1, Goblin Warrior 1/4 AC 15 HP 10 +2, Bugbear Warrior 1 AC 14 HP 33 +2, Ogre 2 AC 11 HP 68 -1. A test checks that every CR is in the XP table.
• The demo's sample note now uses plain names, and its hint says so.
• Plugin tests 47 passed; tsc and eslint clean. Site tests 265 passed, exit 0. Deployed. Checked live with Playwright: 329 suggestions, the SRD hover text, Start fight gave "3x Goblin Warrior hp 10 ac 15 init +2", no page errors.
• Finished 15:04

14:56: Drafts for the boss: the r/rpg self-promo thread, a note to obsidianstats, a phone clip

• r/rpg rules read (https://www.reddit.com/r/rpg/wiki/rules/). There is no weekly self-promo thread; my LEARNED note saying there was is now corrected. Rule 7: a Self Promotion-flaired post, once a week, only for members whose r/rpg activity in the last six months is at least 90% not promotion; everyone else goes to r/rpgpromo. Asked the boss which applies.
• All five free plugins are now in obsidianmd/obsidian-releases community-plugins.json (checked 15:06); DM Screen isn't yet.
• Drafts are in chat for the boss: one Reddit post (the same text for r/rpg or r/rpgpromo; links in the first comment) and an email to obsidianstats (the address is behind the link on https://www.obsidianstats.com/about). They lead with the free plugins and the browser demos. AI isn't mentioned because the post isn't about AI. If someone asks, the answer is yes.
• Clip: a 390x844 phone recording of the Dice Tray demo, three rolls with the new 3D dice, about 12 s, WebM (there's no ffmpeg here for mp4). It's at /press/clips/dice-tray-phone.webm. I didn't do the DM Screen part of the plan; one plugin per clip reads better.
• Nothing posted or sent by me.
• Finished 15:06

15:07: DM Screen's Obsidian review, and the first sale

• There's no obsidian-releases PR to read: the boss submitted all six through Obsidian's form. The five free plugins are in community-plugins.json; DM Screen, submitted as Paid, isn't yet. Nothing I can see to fix.
• itch, read-only (my-games): dm-screen has 0 views, 0 downloads, 0 purchases at $12. No sale yet; total revenue is still $18.09. Nobody reaches the itch page because nothing pointed there.
• Changed the plan: the five free plugins are live in Obsidian, and their READMEs are what Obsidian shows on each plugin's page. None of them mentioned DM Screen. Each README now has a short "On your players' phones" section: what DM Screen shows for that plugin, that it costs $12 once on itch with a free one-hour trial, and that the plugin itself stays free. Each demo page footer has one more sentence linking /press/dm-screen/. Obsidian's developer policies ban dynamic ads and ads outside a plugin's own interface; a README line is neither, and the plugins' UI is unchanged. Obsidian reads READMEs from each repo's main branch, so there's no new release.
• Site tests 265 passed, exit 0. Deployed, and the live footers checked. The READMEs are mirrored to the five repos.
• Finished 15:16

16:05: The Reddit draft moves to r/rpgpromo

• The boss's answer is in FACTS. r/rpg is out for now.
• r/rpgpromo checked: its rules allow the post, but the top posts this month are artist commission ads with at most 25 points. Told the boss it's fine to post the same draft there but not to expect much, and that I'll look for a subreddit where a newcomer may post a free tool and people actually read it.
• Finished 16:05

16:07: A Free Tool Friday draft for r/DMToolkit

• Read the 2 Oct Free Tool Friday thread: "no paid or AI powered tools". The five free plugins qualify: no AI at runtime, and no network calls in their source (checked by grep). Draft comment sent to the boss for 30 Oct; it leaves DM Screen out. A small, on-target audience: comments there get 1 to 7 points.
• Finished 16:07

17:07: The next app: who already helps people find a TTRPG, and is anyone using it

• Solo RPG List already covers the solo-first finder. It has 1391 solo and duet games with ten filters, won an ENNIE Silver in 2026, and bars AI-generated content (sources are in LEARNED).
• The group-game ask is open, but not for us. I found no real tool for "describe what you want" for group games. The natural way to build one is an LLM, and that is what this audience turns away.
• My lean toward a finder is weaker now. I've told the boss, and the next block looks at solo play apps on phones. No FACTS current-app entry, no build.
• Finished 17:08

17:10: The next app: solo play tools on phones, what exists and what people pay

• mail/in was empty.
• Play listings (via Playwright). The official Mythic app has "5K+" downloads at $2.99. RPG Spark and Solo RPG Oracle each have "1K+". One Page Solo Engine isn't on Play. A free, offline, no-AI all-in-one (Fantasy World Generator) got 115 points on r/Solo_Roleplaying.
• What players ask for (r/Solo_Roleplaying). An all-in-one with no AI. The replies name free apps and Obsidian. Iron Vault leads the Obsidian TTRPG plugins.
• Lean. A paid phone app looks like a small market. A solo add-on to the Obsidian line may fit better. Not decided. Sources are in LEARNED.
• Finished 17:13

19:07: Obsidian's solo plugins, what they do and what solo players miss

• Mail and the listing. mail/in was empty. DM Screen is now in Obsidian's community list. It has no download stats yet, and neither do the other five.
• Downloads. Solo RPG Toolkit 38,877. Iron Vault 20,653. Mythic GME Support 228. OPSE Oracle 692.
• What Solo RPG Toolkit lacks. No yes/no oracle. 42 open issues, mostly with no reply, including weighted and nested tables and "too many tables" in the sidebar.
• What players say. r/Solo_Roleplaying: "a proper rolltable manager plugin doesn't really exist yet".
• Strongest candidate so far. A solo plugin with a table manager and an original generic oracle, built on Dice Tray. Not decided. Sources are in LEARNED.
• Finished 19:09

19:32: The next app: commit to the solo plugin in FACTS, then start it

• Committed. FACTS has "Current app, 28 Oct: Solo Oracle" with the boss's words ("just go for it, whats the worst that can happen") and the §1 check.
• Built. Solo Oracle 0.1.0 is in app/plugins/solo-oracle. It is a solo block that becomes a panel. It holds: - tension 0 to 6; - a yes/no oracle at five odds, with "and"/"but" bands and a tension die for twists; - scenes that go as expected, change or get interrupted, and move the tension when they end; - threads and people with Pick one; - Twist and Two words.
• Notes. Every roll is appended to the note as Markdown. The odds, focuses and 60+60 word lists are original. No network.
• Checks. 21 tests pass. tsc and eslint are clean. main.js is 10.6 KB.
• Demo. Built at app/public/press/solo-oracle/ (index.html, demo.js, styles.css). I drove it in Playwright at 1280 and 390 wide: no page errors and no sideways scroll on a phone. The README screenshot is docs/demo.png.
• Repo. Created github.com/walkertbrown/solo-oracle (public, empty until the mirror).
• Mail. market-nana found that Hullbound's itch page shows Derelict's jam description. I checked the live page and it does. I replied with the kit page that has the right text and a Copy button (/press/hullbound/), and said the "vibecoded app" first line on Play is on purpose. Filed to mail/read.
• Finished 19:42

19:42: Solo Oracle 0.1.0: commit, deploy the demo, mirror and release

• Site tests 265 passed (exit 0). Committed the plugin and the demo page, then deployed: /press/solo-oracle/, demo.js and styles.css return 200.
• Mirrored with a subtree split to so-split and pushed to walkertbrown/solo-oracle main. The raw manifest reads solo-oracle 0.1.0.
• Release 0.1.0 is up with main.js (10625 bytes), manifest.json and styles.css. All three download with 200 at the same sizes.
• Next: the boss submits it to Obsidian as Free. The form needs the repo (walkertbrown/solo-oracle).
• Finished 19:50

21:07: Solo Oracle: roll on your own tables from the panel

• Tables. A table: [[Note#Heading]] line in the block gives the panel a Roll button. An alias (|Sky) names the button. The box under the panel adds a line, and × removes one.
• How a table rolls. It works like Dice Tray, with the code copied into src/tables.ts as pure text functions: - a lookup table, whose first column holds numbers or ranges, rolls the dice in its header (d6, 2d6) or 1 to the highest number; - any other table gives a row, a list gives an item, and anything else gives a line.
• Notes. A heading's part runs to the next heading as high as it. Frontmatter is skipped. A missing note or heading says why and writes nothing. The journal line reads - **Weather** *(3)*: Fog off the water.
• Kept for Pro. Weighted and nested rows were left out.
• Checks. Plugin tests 31 pass (10 new). tsc and eslint are clean. Site tests 265 passed (exit 0).
• Demo. It has a second note with two tables (Weather, On the dock). Driven in Playwright with no page errors, including the "No heading" message.
• Cross-links. The five other plugin demo pages and DM Screen's page now link to Solo Oracle.
• Shipped. Deployed, mirrored and released 0.2.0. main.js is 14010 bytes and the release files download with 200. The raw manifest reads 0.2.0.
• Finished 21:20

22:09: Solo Oracle listing: short and long description, featured picture, screenshots

• Made a listing kit at /press/solo-oracle/listing/: a short description, a long one, install instructions (each with a Copy button), a featured picture at 1280×720, an itch cover at 630×500, three screenshots (the note beside its text, the panel alone, a phone), and solo-oracle.zip (0.2.0, the same main.js as the GitHub release).
• The pictures are drawn in code or are screenshots of the demo, played with fixed rolls so the panel shows "Yes, but" and a twist. The rolls first came out one step off: something on the page drew a random number while it loaded, so the queue is now loaded after the page.
• The demo page's input boxes used a typewriter font, unlike Obsidian; they now use the interface font.
• The README opens with the new note screenshot (docs/demo.png); mirrored to the repo.
• Solo Oracle still isn't in Obsidian's list (its community page says "Plugin not found"), so the install text covers the zip and the in-app list both.
• Site tests: 265 passed, exit 0. Deployed; the page, five pictures and the zip return 200.
• Finished 22:25

22:46: Solo Oracle long description under 1000 characters

• The boss said the description field takes at most 1000 characters. Cut the long description to 929, keeping the same facts but dropping the demo link and the "two words" line, and sent it in chat.
• The kit page now has the short version, with its character count above the Copy button.
• Site tests: 265 passed, exit 0. Deployed; the live page shows the new text.
• Finished 22:55