Skip to content

dndpaste 0.11.0

Latest

Choose a tag to compare

@francescocompa francescocompa released this 21 Nov 22:29
· 2 commits to main since this release

dndpaste 0.11 names the ability scores on the Scores line and can say how they were made: standard array, point buy or custom. Every 0.10 paste still reads as before. The editor now shows each score's final value and the method behind the numbers. Most of this release answers feedback from r/3d6.

Try it: https://dndpaste.fcomfy.workers.dev

The format (SPEC 0.11)

  • The base line names each score: Scores: STR 8/DEX 14/CON 13/INT 12/WIS 10/CHA 15, or only the ones you know: Scores: DEX 16/CHA 17. Tidy and emit write this form.
  • The old forms still read, with no warning: six bare numbers (8/14/13/12/10/15) and the comma form (DEX 16, CHA 17) mean the same.
  • An optional method marker: Scores (standard array): …, Scores (point buy): … or Scores (custom): …. Nothing writes it by default, and the parser doesn't compare it with the numbers.
  • Increase lines (Scores: +2 WIS, +1 DEX) don't change.

The library

  • scoreKind(values) says whether a base is the standard array, point-buy legal (with the points left of 27) or custom. It also works on a partial base. It needs no data: the array and the point costs are a few numbers in the code.
  • A marker with an unknown method is E002. A marker on an increase line is E012, with a safe fix that drops it.
  • The UMD build loads again. In 0.10.0, dist/dndpaste.umd.cjs failed to load as a script, and a test now loads it.

The site

  • Click a score to see its final value, such as WIS 15 → 19 (+4), and the swaps its method allows.
  • A chip at the end of the Scores line shows the method: Std. Array, Point Buy 2/27 or Custom. Its chevron lists the methods.
  • Start a build asks for the method and remembers your last choice.
  • The shared and printed pages show the same mark.
  • Also live since earlier today: name lists open on any empty key, a click on a written name lists what can replace it, a level-up line adds the next level, and the caret moves to the next open choice.

Migrating from 0.10

Readers don't need to change anything. If your tests compare emitted text, they'll see the new base line. If you build lines from scopeLines, write them with lineOfValue to keep the method marker. The full table is in CHANGELOG.md.