0.3.0
[0.3.0] — 2026-08-02
Your notes will start showing warnings
They always existed; this plugin was throwing them away. Only errors reached a note, so the whole of Chartdown's coherence checking was invisible here — a river running through a wall with no door, a room nothing can reach, a structure standing on nothing. Every other way of running Chartdown reported them; a note rendered the map and looked finished.
Warnings now appear beneath the map in their own colour. An error means the map is wrong; a warning means it may not be what you meant.
If a map you have had for months suddenly shows a warning, nothing changed about your map. The check was always failing and you were never told.
A fence can import a file beside it
use: ./my-vocabulary.cd now resolves against your vault, so a shared vocabulary can live in its own file instead of being repeated in every note — and a .cd file opened as a file does the same. inset: parents resolve too.
A path that does not resolve says so rather than rendering quietly without it.
.cd files open to their map
Keep a map as its own file, not only as a fence inside a note. Opening a .cd file shows the rendered map with the same toolbar you get in a note — GM/player toggle, SVG and UVTT export, the copy/paste source round trip — and a Source button swaps to the text, editable in place.
Exports take the file's own name, so sunless-hollow.cd writes sunless-hollow.svg beside the source it came from.
Before this the plugin registered only the markdown code-block processor, so it handled a fence inside a note and nothing else: no view claimed the extension, and a .cd file in a vault could not be opened at all.
While the plugin is enabled it claims the .cd extension for the vault. Disable it and those files go back to being unopenable, since nothing else knows what they are.
Built from Nossimonov/Chartdown@v0.5.0.