PF2E Automated Action Tracker streamlines Foundry combat economy for Pathfinder players

Why this tracker matters in the middle of a fight

The ugliest pauses in a Foundry PF2E session are rarely the big rules questions. They are the small ones: a forgotten reaction, a token that crossed difficult terrain one square too far, or a turn that bogs down while everyone checks whether Slowed, Stunned, or a temporary bonus action changed the count. PF2E Automated Action Tracker exists to remove exactly that friction, so the table can stay on the fight instead of on the math.

That focus is what makes it feel so useful to Pathfinder players. The module is built as a high-performance economy manager for Pathfinder Second Edition, and its job is not to replace the rules. It is to surface them fast enough that combat still feels reactive, especially when the encounter is busy and the GM is already juggling enemy tactics, conditions, and player questions.

What it automates without getting in the way

The tracker’s core value is that it keeps the Pathfinder action economy visible at a glance. In practice, that means it can show real-time action pips in the Combat Tracker, recognize movement as actual movement rather than just token drift, and account for difficult terrain through V12 Regions support. It also handles Slowed and Stunned automatically at the start of turns, which is exactly where those conditions tend to trip up even experienced tables.

A few of the most important pieces are easy to see in play:

• Dynamic action-slot calculations for overlapping conditions such as Quickened plus Slowed plus Stunned
• Extra action or reaction slots from feats like Combat Reflexes, Divine Reflexes, Esoteric Reflexes, and Tactical Reflexes
• Multiple Attack Penalty tracking so the round’s pressure stays visible
• Token HUD integration for players who want the relevant state right where they are already looking
• Sustain reminders for ongoing spells, so buffs and lingering magic do not vanish from memory in the middle of initiative

That list matters because PF2E combat is not just about “how many actions do I have.” It is about what changed since the last turn, what was spent on movement, what is still available as a reaction, and how penalties are stacking as the round develops. The tracker is designed to keep those moving pieces in view without forcing the GM to rebuild the turn every time someone asks a question.

The table-speed difference, before and after

Before automation, a busy combat round often turns into a miniature audit. The GM checks whether a creature is Slowed 1 or Stunned 2, whether a feat granted an extra reaction, whether a spell still needs to be Sustained, and whether a move action actually burned the expected amount of movement because difficult terrain got involved. If multiple conditions overlap, the bookkeeping can become its own side encounter.

After automation, the same encounter flow is cleaner. The Combat Tracker shows the current economy state, the module updates action availability as conditions change, and the table spends less time reconstructing the round from memory. That matters most at organized play tables and in busy online groups, where the pace is tighter and the GM cannot afford to stop and verify every micro-decision twice.

The practical payoff is not just speed. It is confidence. When the module is handling action-slot math and reaction visibility, players are less likely to hesitate over whether a defense is still available, and GMs are less likely to pause the whole fight to settle an action-count dispute. The result feels like a more responsive encounter, which is exactly what PF2E’s tight action economy is supposed to deliver.

Why the current release matters right now

The current package page lists version 0.15.0 as the active release and shows compatibility with Foundry 14.360. The repository’s module.json also points to minimum Foundry 13 support and a PF2e system compatibility target of 8.1.1. That combination is a useful signal for tables that want modern Foundry support without losing sight of slightly older installs still in active use.

The recent release workflow adds another layer of context. It includes node v24 support, an action library, and a compact PF2e HUD path that explicitly mentions MAP handling. That is not generic maintenance noise. It shows the project is being shaped around Pathfinder-specific quality-of-life concerns, especially the kind that show up every round: action economy, MAP, and the right information at the right moment.

For the wider Pathfinder VTT community, this kind of automation matters because it protects the texture of PF2E combat. The game’s tactical identity depends on small decisions, and those decisions only stay fun when the bookkeeping stays out of the way. A tracker that understands reactions, movement costs, condition timing, and ongoing spell upkeep is not just a convenience feature. It is the difference between a fight that stalls and a fight that keeps its momentum all the way to the final initiative card.