Skip to content

1.11.0

Latest

Choose a tag to compare

@github-actions github-actions released this 14 Aug 03:24
· 10 commits to main since this release

Fixed

  • Your codex now follows you into new drafts. Creating a new draft no longer presents an empty codex: characters, concepts, locations, and every other entry scoped to the book are visible from all of its drafts (the codex describes the story, not one draft of it). This also works retroactively — entries that "disappeared" after making a draft reappear on update, with no changes to your files. Entries created while a later draft was active are likewise visible from the original, and the scene inspector's character/location pickers offer them from any draft.
  • New drafts no longer nest inside each other. Creating a draft while a copied draft was active used to bury it at Drafts/Draft 2/Drafts/Draft 3/…; every new draft now lands in the story's one flat Drafts/ folder, whichever draft you copied it from. Existing nested drafts keep working where they are.
  • Draft-aware consistency fixes across the app. The codex scope dropdown now lists each book once instead of listing every draft as a separate book; new codex files created alongside a book land in the story's folder, never inside a draft copy's folder; "Appears in" lists each scene once instead of once per draft (this also fixes existing duplicates for series-scoped entries); the "Set word target" command now saves to the same place the progress bars read from (previously, with a revision draft active, it silently saved where nothing read it); adding a book to a series from a revision draft now tags the book itself, so the series no longer "loses" the book when you switch drafts; series-wide search no longer returns every result twice per draft; and Track → Targets measures progress against the draft you're actually writing instead of the frozen original.
  • The plot grid no longer jumps back to the top when you tag a scene. Tagging or untagging a scene, dragging a chip, renaming/recoloring/deleting a plotline, or dropping a card on the Board now refreshes the grid in place — scroll position (vertical and horizontal) and any focused field survive, instead of the whole panel rebuilding and landing you back at the top.
  • The same "editing something scrolled you back to the top" fix, applied everywhere it existed. Every panel with autosaving fields now refreshes in place after its own saves instead of rebuilding the whole view: Plan → Overview fields, the Beats sheet, Revise → Audit checklists (whose progress counters previously could also fail to update), the Publish checklist / launch trackers / compile settings, the Home hero card (logline, theme, target, cover), the word-target dialog, and the scene row menus (synopsis, rename, remove from project). Long forms keep their scroll position and open sections; the field you were editing keeps its caret.

Added

  • Daily backups of the plugin's own data file. Obsidian's File Recovery protects your notes but never sees the plugin's data.json — which holds your settings, writing history, sprints, and ideas inbox. Inkswell now keeps a daily copy (the last 7 days) in .obsidian/plugins/inkswell/backups/, captured at load before the session writes anything. To restore one: disable Inkswell, copy the backup over data.json, re-enable.
  • A "Your data & backups" section in Help (and the README) documenting where everything is stored — most importantly that plan data (beats, goals, revision log, checklists) lives in the project index note's frontmatter, so File Recovery searches for it by your project's name — plus the "Inkswell conflicts" folder and the new data.json backups.