Obsidian - Inline Scripts

Inline Scripts for Obsidian lets users run JavaScript inside a Vault and have the results render directly as formatted text—often as ready-to-use tables or linked records—at the moment they type a trigger. That turns “random tables” from static, pre-made assets into on-demand generators that can pull from notes, roll dice, and even store roll history inside the note for later reference.

A key example shows how a single inline command can generate a random “blacksmith” inventory table. Instead of hunting down a separate rollable table, the user types a trigger (using a prefix/suffix like “;; … : :”) and immediately gets a table of items. The results change on each run, but the output is embedded right where it’s needed—useful for game prep and for documenting what happened during play.

The workflow becomes more powerful when Inline Scripts pull data from existing notes. A hard-coded table can work, but it’s labor-intensive to maintain. The more scalable approach uses a “folder randomizer” pattern: the script selects random notes from a chosen folder (or subfolder), then reads their frontmatter fields (like cost, rarity, level, or other metadata) to populate table columns. That means adding new notes to a folder automatically expands what the generator can produce—no manual table edits required.

The transcript also highlights a practical advantage over interactive dice rollers. Traditional dice plugins typically roll again every time the note is reopened, leaving no persistent record. Inline Scripts can write the roll result into the note itself, so a later “journal” entry can show what the players rolled (for example, a d20 check) and whether it succeeded.

Installation is done through Obsidian’s Community Plugins: search for “Inline Scripts,” install and enable it, then import the “full library” so the needed helper libraries (including a “notepic” library) are available. The setup includes configurable shortcut prefixes/suffixes and a library of prebuilt buttons. From there, users can create custom shortcuts that prompt for parameters (using question-mark placeholders), such as asking how many spells or potions to generate.

The most concrete implementation details focus on how the folder-based scripts are structured. The script defines a trigger name (e.g., “get my folder” or “get spell book”), declares a result-building loop, and constructs markdown table rows by concatenating strings and inserting newlines. It also relies on consistent frontmatter: every note in the target folder must include the metadata fields the script expects, or the output will show undefined values or errors. The transcript stresses that the number of requested random results can’t exceed the number of eligible notes.

By the end, the appeal is clear: Inline Scripts turns Obsidian into a lightweight RPG content engine. With folder-driven random tables, users can generate shop inventories, spell lists, mundane items, and other structured content on demand—then link each generated item back to its source note for quick reference during play.