Summary

Support the “Lonelog Card Notation Add-on” so that card draws (standard deck, tarot, and oracle decks) are recognized and highlighted just like core Lonelog events.

Motivation

Lonelog already supports a clean, consistent notation for dice, but many solo tools and systems rely on cards (standard decks, tarot, oracle).

The Lonelog Card Notation Add-on defines a compact, unambiguous grammar for these card draws (ranks, suits, jokers, Major/Minor Arcana, oracle names, spreads).

Right now, these card-based events show up as plain text in the plugin, even though they already have an official Lonelog-standard notation, which limits readability and future parsing.

Proposed Solution

Add first-class support for the Card Notation Add-on in the plugin, mirroring how dice notation is handled.

Concretely, the plugin could:

• Detect standard playing cards after d events in the form ranksuit with ranks A, 2–10, J, Q, K and suits h, d, c, s, plus Jkr, RJkr, BJkr for jokers.
• Detect Major Arcana as M0–M21 with optional r suffix for reversed cards (e.g. M16r).
• Detect Minor Arcana as A, 2–10, Pg, Kn, Q, K combined with Wa, Cu, Sw, Pe, with optional r (e.g. 7Wa, PgSwr).
• Treat oracle draws as d draw and at least highlight the draw token and card name as a card event.
• Support spreads where each card has a position label, both in single-line form (d Past5s, PresentKs, FutureACu) and multi-line form with outcomes.
• The goal is not necessarily full semantic parsing on day one, but recognition and highlighting of these official patterns so card-based logs become as readable as dice-based logs.

Alternatives Considered

• Keep using free-form text for card draws (e.g. “Queen of Spades”, “The Tower reversed”) without any plu- gin awareness. This works but loses the benefits of a standard notation and makes cross-tool support harder.
  Rely on custom regex snippets per user instead of supporting the standard Lonelog card grammar directly in the plugin, which would fragment behavior and duplicate work for users.