Obsidian - Initiative Tracker

TL;DR

Install Initiative Tracker from Obsidian community plugins, then enable it and follow the README’s encounter syntax and examples.

Briefing Cornell Notes

Briefing

Initiative Tracker turns Obsidian into a fast, table-ready combat manager by linking player and monster stats to encounter blocks that automatically roll initiative, track turns, apply damage, and manage status effects. Instead of prepping encounters in a separate tool or manually adding monsters at combat start, the workflow keeps everything inside Obsidian notes—so running a fight becomes mostly clicking, rolling, and updating damage rather than re-entering data.

Setup starts with installing the Initiative Tracker plugin (by Jeremy Valentine) from Obsidian’s community plugins, then enabling it and reading the README for encounter syntax and examples. The plugin is designed to work with D&D 5e-style data but isn’t tightly bound to any one system; it mainly needs structured creature and character fields. Players are added in the plugin settings by creating entries that can be linked to notes—so a linked note can supply name, level, hit points, armor class, and initiative modifier. Those player fields then need periodic updates as characters level up.

Monsters can be imported via the same stat-block workflow used by the ttrpg stat blocks plugin, with dice roller recommended as a prerequisite for smoother rolling. If ttrpg stat blocks is already installed, Initiative Tracker can sync a large monster library and optionally roll equivalent creatures together (for example, grouping goblins) to speed up encounter creation. Once players and monsters exist in the system, encounters are built using encounter blocks that specify an encounter name and the number of creatures, with creature names linked to the monster library. Hovering over a creature entry to see an XP pop-up acts as a quick validation that the monster link is correct.

During play, the combat panel shows initiative order, each combatant’s health and AC, and the current turn. Initiative can be rolled automatically for both players and monsters at combat start; results can also be manually overridden by clicking an initiative value. When a character attacks, the player can click the target and enter damage, which updates health and advances the turn. Status effects are handled through simple actions like adding a status (e.g., frightened), and the plugin can reflect outcomes such as unconsciousness when health drops to zero. It also calculates encounter challenge rating, helping the DM adjust difficulty mid-prep.

A major strength is how encounters are displayed and launched from normal notes. Encounter blocks can be embedded directly, converted into tables (using Obsidian table syntax), or combined into multi-encounter sections separated by delimiter lines. Dice roller integration enables randomization—rolling 2d6 worth of creatures to spawn a variable number of enemies. For more advanced prep, the plugin supports encounter tables that can include lines of narrative text mixed with encounter triggers, so a single note can function as both session script and combat launcher. There’s also an option to modify monster stats inline for a “challenging” variant (overriding HP/AC and related components), though that override behavior is limited to certain encounter formats.

Overall, Initiative Tracker streamlines the most error-prone part of tabletop running—initiative, turn order, damage bookkeeping, and status tracking—by binding combat mechanics to the same notes where the DM already writes prep and encounter instructions.

Cornell Notes

Initiative Tracker for Obsidian provides an in-note combat system that links player and monster stats to encounter blocks. After installation and setup (players added via linked notes; monsters synced/imported via ttrpg stat blocks; dice roller recommended), DMs can launch encounters that automatically roll initiative, show health and AC, and manage turn order. Combat becomes click-and-update: enter damage to update targets, add status effects like frightened, and track outcomes such as unconsciousness when health reaches zero. The plugin also supports embedding encounters in tables and using dice roller to randomize enemy counts, letting a single prep note act as both narrative script and combat launcher.

How does Initiative Tracker connect character data to the combat tracker without duplicating stats manually?

Players are added in Initiative Tracker’s settings using an “add player” workflow that can link each player entry to a specific Obsidian note. That linked note supplies fields like name, level, hit points, armor class, and initiative modifier. When characters level up, the DM updates those linked player stats so the combat panel stays current.

What’s the practical way to ensure a creature entry in an encounter block is linked to the correct monster?

When building an encounter block, the creature name must match a monster in the synced/imported monster library. The DM can validate the link by hovering over the creature entry; an XP pop-up indicates the monster was successfully grabbed. If the monster name is wrong, the link fails and the XP indicator won’t appear.

What changes during play when initiative is rolled automatically versus manually?

At combat start, the tracker can roll initiative for both players and monsters at the same time. The initiative order then appears in the combat panel. If a DM or table prefers control, initiative can be manually adjusted by clicking the initiative result and entering the desired value, which reorders turns accordingly.

How does the tracker handle damage, status effects, and turn progression?

On a character’s turn, the DM/player clicks the target and enters damage; the tracker updates the target’s health and advances the turn. Status effects are added through simple actions like “add status” (example given: frightened). When health reaches zero, the tracker can prompt or automatically support outcomes such as unconsciousness, and it continues the round/turn loop.

How can DMs launch randomized or variable encounters from a single note?

By embedding encounter blocks in tables or multi-encounter sections and integrating dice roller. Examples include rolling “2d6 worth of these guys” to spawn a variable number of enemies, then clicking “begin encounter” to start combat with that rolled quantity. Narrative prep can also be mixed with encounter triggers in an encounter table so the note functions as both script and combat launcher.

What does “challenging” monster modification look like, and where does it work?

In the plugin’s settings, the DM can create a modified encounter definition (example: “challenging goblin”) by overriding monster components like HP and AC using comma-separated parameters (e.g., changing HP to 14 and AC to 20). Clicking the modified entry starts combat using the overridden stats. The transcript notes this override behavior is supported in certain encounter formats but doesn’t work in the same way for the single-line encounter method.

Review Questions

What data sources does Initiative Tracker rely on for players and monsters, and how are those linked to combat encounters?
Describe the step-by-step flow from creating an encounter block to running combat and updating damage.
How do tables and dice roller integration change the way encounters are prepared and launched during a session?

Key Points

1
Install Initiative Tracker from Obsidian community plugins, then enable it and follow the README’s encounter syntax and examples.
2
Add players by linking each player entry to a note so name, hit points, armor class, and initiative modifier flow into combat automatically.
3
Sync or import monsters using ttrpg stat blocks (dice roller is recommended for smoother rolling and randomization).
4
Create encounters with encounter blocks that specify an encounter name and creature counts, linking creature names to the monster library.
5
Run combat by starting the encounter to roll initiative (automatically or manually), then update targets by entering damage and adding status effects.
6
Use tables, multi-encounter sections, and dice roller to randomize enemy counts and launch combat from a single prep note.
7
Leverage monster stat overrides for “challenging” variants, but expect different behavior depending on the encounter format used.

Highlights

Initiative Tracker brings initiative order, health/AC display, and turn-by-turn combat management into Obsidian notes—reducing manual bookkeeping at the table.

Hover validation (XP pop-up) provides a quick check that an encounter’s creature name correctly links to a monster definition.

Dice roller integration enables variable spawns—rolling 2d6 worth of enemies—so random encounters can start with a single click.

Encounter tables can mix narrative instructions with combat triggers, turning one note into both session script and combat launcher.

Topics

Obsidian Plugins
Combat Tracking
Initiative Management
Encounter Blocks
Dice Roller Integration