Skip to content

Releases: Filroden/rmu-combat-storyboard

v1.0.0

12 Jun 11:39

Choose a tag to compare

Release v1.0.0

Build Details:


Changelog

Changes since v1.0.0-beta1

IMPROVEMENTS

  • Visual descriptors for a combatant's size are now based on their token footprint on the grid, capturing any enlarging or shrinking effects.
  • The Cast & Roster automatically generates natural language descriptions for a combatant's main armour and any equipped shield, removing the need to type them out manually.
  • Combatants going below 0 hitpoints are now highlighted in the exports showing them as incapacitated.
  • Saved combat encounters now use "YYYY/MM/DD" for their date format so when they sort they remain in time order.

v1.0.0-beta1

16 May 16:11
8cea3bb

Choose a tag to compare

v1.0.0-beta1 Pre-release
Pre-release

Release v1.0.0-beta1

Build Details:


Changelog

Changes since start

Initial Beta Release

FEATURES

  • Automated Combat Logging: Hooks directly into RMU combats to silently record attacks, spells, resistance rolls, and applied damage.
  • Storyboard Wizard UI: An interface accessed from the Combat Tracker to review and export the combat timeline.
  • Cast & Roster Management: Allows the GM to replace actor names with physical descriptions to guide AI script and image generation.
  • Hero Moments: Provides a toggle to spotlight specific combat actions so they become focal points in the generated script.
  • Prompt Export: Compiles the curated combat data into a token-optimised prompt that instructs external AI models to generate both a narrative script and image generation prompts.
  • Plain Text Export: Includes a one-click download to save a human-readable text file of the combat timeline.

IMPROVEMENTS

  • (Initial release - no prior improvements)

BUG FIXES

  • (Initial release - no prior bug fixes)

UNDER THE HOOD

  • Journal Data Storage: Combat logs, custom rosters, and campaign context are saved as flags on standard Foundry Journal Entries so data persists between game sessions.
  • ETL Ingestion Pipeline: Intercepts and parses hook data before it reaches the database so only relevant, sanitised data is stored.