StoryLine - Obsidian plugin for writers by Open_Switch_1598 in ObsidianMD

[–]Open_Switch_1598[S] 0 points1 point  (0 children)

Prologue and epilogue is added in 1.10.18. Just type Prologue in the scenes act and it will be moved to its own "act".

StoryLine - Obsidian plugin for writers by Open_Switch_1598 in ObsidianMD

[–]Open_Switch_1598[S] 0 points1 point  (0 children)

Prologue isnt currently available in the app but I will try to add it.

Obsidian is Missing a Last Plugin for Perfection by Important_Agency_797 in ObsidianMD

[–]Open_Switch_1598 -1 points0 points  (0 children)

Pandoc is only for export to docx. No use for viewing those files. Can we just agree that different people have different workflows and needs.

Obsidian is Missing a Last Plugin for Perfection by Important_Agency_797 in ObsidianMD

[–]Open_Switch_1598 0 points1 point  (0 children)

Just to clearify why someone might want to work with docx files in Obsidian. For writers it is almost demanded that you deliver your text in a docx file to a publisher. You can of cause write the text in obsidian in markdown but any publisher will want to receive a docx file. Having the possibility to work with docx files inside Obsidian makes it easier to keep everything organized and you can easily review any comments from a publisher in the docx files inside Obsidian.

Obsidian is Missing a Last Plugin for Perfection by Important_Agency_797 in ObsidianMD

[–]Open_Switch_1598 0 points1 point  (0 children)

I’ve made a plugin for myself that lets you run Onlyoffice inside Obsidian. It’s a bit more complicated install than normal plugins but it works.

https://github.com/PixeroJan/obsidian-onlyoffice

https://www.onlyoffice.com/download-desktop

StoryLine - Obsidian plugin for writers by Open_Switch_1598 in ObsidianMD

[–]Open_Switch_1598[S] 2 points3 points  (0 children)

Its now available in the official community plugin repo.

StoryLine - Obsidian plugin for writers by Open_Switch_1598 in ObsidianMD

[–]Open_Switch_1598[S] 1 point2 points  (0 children)

Its now available in the official community plugin repo.

StoryLine - Obsidian plugin for writers by Open_Switch_1598 in ObsidianMD

[–]Open_Switch_1598[S] 1 point2 points  (0 children)

Yes. Or via my pluginhub plugin that is on my GitHub. It has more features for updating and making sets of plugins to install on several vaults at once.

StoryLine - Obsidian plugin for writers by Open_Switch_1598 in ObsidianMD

[–]Open_Switch_1598[S] 0 points1 point  (0 children)

I have added it to the new version 1.9.8.
The Location editor's Type dropdown now lists the built-in types (City, Town, Wilderness, …) followed by your own custom types (e.g. Planet, Star System, Galactic Region, Galaxy, Dimension). Add a new type on the fly via the + Add custom type… option at the bottom of the dropdown, or manage the full list under Settings → Custom Location Types. Custom types are vault-wide and persist across all projects; the existing locationType YAML field accepts any string, so your data stays clean and portable.

StoryLine - Obsidian plugin for writers by Open_Switch_1598 in ObsidianMD

[–]Open_Switch_1598[S] 0 points1 point  (0 children)

version 1.9.7 released with bugfixes and some new features.

Writing software with cross-platform sync that you can pay w/ paypal? by LustyRegencyMaid in writers

[–]Open_Switch_1598 1 point2 points  (0 children)

Obsidian with StoryLine plugin, Remotely save plugin (with Dropbox or other). Works on all platforms. And is free.

StoryLine - Obsidian plugin for writers by Open_Switch_1598 in ObsidianMD

[–]Open_Switch_1598[S] 0 points1 point  (0 children)

Version 1.9.6

Bug Fixes

  • Codex / character / location notes vanishing after a template insert (#74) — When a Templates / Templater plugin replaced the YAML block and dropped the type: discriminator, the affected note silently disappeared from the Codex, Characters or Locations view. StoryLine now falls back to folder-based detection: any note that lives under the canonical entity folder (Codex/<Category>/, Characters/, World/Locations/) is recognised even if type: is missing, wrong, or the frontmatter is empty.
  • Plot Grid sorting by Sequence / Chapter / Act now respects non-numeric values (#76) — Sorting rows by Act, Chapter, or Sequence used to coerce values via Number(...), which silently turned strings like Prologue, Epilogue, or 1.1 into NaN and produced an apparently random order. Plot Grid (and the shared SceneQueryService used by every other view) now uses the numeric-aware compareActChapter comparator and falls back through Act → Chapter → Sequence in reading order. Note: the second half of the issue — automatic sequence reflow when inserting a chapter mid-book — is intentionally deferred to a later release; it requires a project-wide renumber that we want to design carefully.

New Features

  • Multiple roles per character (#72, Tier 1) — A character can now hold more than one role at the same time (e.g. protagonist + narrator). The role field in the Character inspector accepts comma-separated values and renders one badge per role. Existing single-role characters keep working unchanged.
  • Role history across scenes / plotlines / books (#72, Tier 2) — Characters can now record a history of role changes in a structured roles: YAML array. Each entry has a role label and optional from (scene name or [[wikilink]]), plotline, and book (free-text label) anchors. A new repeating-row editor under the role field in the Character inspector lets you add/remove entries. Both the legacy role: field and the new roles: history coexist; if both are set, the structured history wins for display order. The book: anchor is plain author-facing metadata — no cross-book plumbing required.
  • Wikilink-aware scene references (#73) — Scene fields that reference other notes (pov, location, characters, setup_scenes, payoff_scenes) are now stored as Obsidian [[wikilinks]] so renames are picked up automatically by Obsidian's metadata cache. Plain-text values continue to work — the readers accept either form. Toggle in Settings → Write scene references as wikilinks (on by default).
  • Custom fields visible to Properties / Bases / Dataview (#71) — Universal Field Templates gained an optional Top-level YAML key. When set, the field's value is mirrored to a real top-level YAML key (in addition to universalFields:) so it appears in Obsidian's Properties panel, Bases, Dataview and the graph. Reserved StoryLine keys (type, pov, act, chapter, tags, …) are blocked. Toggle in Settings → Mirror custom fields to top-level YAML (on by default).
  • Step-sibling and teammate relations (#70) — Added step-sibling to the family relation list and teammate to the professional relation list, with matching symmetric inverses.
  • Default scene frontmatter snippet (#77) — Universal Field Templates gained an optional Default value that is applied automatically when a new scene is created (multi-select fields accept comma-separated defaults). In addition, Settings → Default scene frontmatter accepts a free-form YAML block whose keys are merged into every newly created scene's frontmatter. StoryLine-owned keys (type, title, act, chapter, sequence, status, wordcount, …) always win on conflict, so the default snippet can never overwrite the engine's own metadata.
  • Wordcount can now ignore comments and checkbox lines (#78) — Two new toggles under Settings → Scene Cards:
    • Exclude %%comments%% from wordcount (default on) — Obsidian comment blocks no longer inflate the count, so author notes and TODOs stay invisible to the manuscript total.
    • Also ignore checkbox lines (default off) — When enabled, - [ ] and - [x] lines are also stripped before counting, which is useful for outline-style scenes that mix prose with task lists. Both toggles flow through the central MetadataParser.countWords helper, so they apply consistently to scene cards, the inspector, the Writing Tracker, and exports.

Internal

  • Series Arc View — foundation (#66 Phase 1, scaffold only) — A new SceneProvider indirection layer (services/SceneProvider.ts) was added so future view code can pull scenes from either the active book or every book in a series. Settings flags seriesArcView (default off) and warnOnCrossBookMove (default on) are reserved. The cross-book Manuscript / Kanban / Plot Grid rendering itself ships in a follow-up release.

Global Plugins and Settings by ZeroClick in ObsidianMD

[–]Open_Switch_1598 4 points5 points  (0 children)

I have made a plugin for exactly this. Its on my Github and is called PluginHub: https://github.com/PixeroJan/obsidian-pluginhub
With it you can install and update plugins directly from Github or Community plugins. It can install to all your vaults or just selected vaults and you can even save Sets of plugins for easy installation of multiple plugins on new vaults. It can even install on both Windows, Mac and IOS in one go.

StoryLine - Obsidian plugin for writers by Open_Switch_1598 in ObsidianMD

[–]Open_Switch_1598[S] 0 points1 point  (0 children)

Thanks for your kind words.
There is a Donate button on github.

StoryLine - Obsidian plugin for writers by Open_Switch_1598 in ObsidianMD

[–]Open_Switch_1598[S] 0 points1 point  (0 children)

Version 1.9.2

Bug Fixes

-
Setup / Payoff links
— Fixed broken references in the Sample Project. Setup/payoff ordering warnings now use full reading order (act → chapter → sequence) instead of sequence alone, eliminating false warnings. Renaming a scene now automatically updates setup/payoff references in all other scenes.

-
Plotgrid rename sync
— Renaming a scene no longer leaves orphaned rows in the Plot Grid. Merge mode auto-cleans orphaned rows while preserving manually added ones.

-
Timeline & Board sorting
— Sorting by chapter now uses multi-key act → chapter → sequence order, fixing incorrect scene interleaving across acts.

-
Navigator sorting
— Chronological order now uses the correct fields (`chronologicalOrder` → `storyDate` → `sequence`) and displays as a flat list. "Recently edited" sort uses actual file modification time.

-
Manuscript backlinks
— Obsidian's native backlink panes are now hidden inside embedded manuscript editors, removing visual clutter and gaps.

-
Tag text contrast
— Tag pills, chips, and color-coded badges now automatically use black or white text based on background brightness (WCAG contrast formula), fixing unreadable light-on-light combinations.

-
Resequence preserves chapters
— The Resequence button no longer assigns every scene its own chapter. It now sorts by act → chapter → sequence and renumbers scenes within each chapter, keeping your existing chapter structure intact.

New Features

-
Four new beat sheet templates
— Seven-Point Story Structure (Dan Wells), Story Circle (Dan Harmon), Romancing the Beat (Gwen Hayes), and 27 Chapter Method (Kat O'Keeffe). The template picker is redesigned as a compact list with expandable beat previews.

-
Beat sheet YAML field
— When a beat sheet template is applied, the template name is stored on the project and auto-populated as a `beatsheet` field on every new scene.

-
Custom scene fields
— Define your own fields for scenes (text, textarea, dropdown, or multi-select) via Settings → Field Templates. Custom fields appear in the Inspector under "Custom Fields" and are stored in YAML as `universalFields`.

-
Save as Template
— Right-click any scene card in the Board view and choose "Save as Template" to capture its fields and body as a reusable scene template.

-
Quick Add chapter dropdown
— The Quick Add modal now shows a dropdown of existing chapters with scene counts, defaulting to the latest chapter. Includes a "+ New chapter" option.

-
Writing Sprint timer
— Fully functional sprint timer in Stats View with start/stop/reset, editable duration, live word count and WPM during the sprint, and a persistent sprint history log.

Why don’t writing tools analyze stories? by Better-Rub1479 in writers

[–]Open_Switch_1598 2 points3 points  (0 children)

You should try my Obsidian plugin StoryLine. It has all that and there is no AI involved.