Crucible Version 0.7.7 - "V13 Beta 7"

Version 0.7.7 adds some new features and a number of bug fixes for more urgent issues that affect currently playtesting.

New Features

Improve the distance calculation to use the shortest distance between two tokens rather than the center-to-center ray
Simplify the expectations of Action usage flow by removing the option to skip ChatMessage generation (which is now required) and removing the option for the created ChatMessage to be temporary and non-persisted.
Track an array CrucibleActor#actionHistory which records the sequence of actions a chraracter has taken since the start of their most recent combat turn.
Add CrucibleActor#lastConfirmedAction which dynamically retrieves the CrucibleAction that was most recently confirmed in that Actor's action history.
Further streamline and improve summoning workflows for creatures that summon others.
Align the rules implementation of Arcane Archer and Spellblade so that they more closely (but not exactly) mirrored
The Shield Bash action no longer requires a melee weapon to be equipped, allowing combos like 1h talisman + shield or 1h projectile + shield
Reduce the amount of free movement granted by Evasive Shot to half your Stride instead of your full Stride.

Uppercut does not automate the requirement of the same target as the prior Strike.
Error in Spellband automation
Actions with the Projectile Tag incorrectly cannot be used with a projectile weapon equipped.
Elemental summons need to be able to cast spells and have their weapons treated as natural so they have available free hands for spellcasting
The Arcane Archer signature should treat Gesture: Arrow as not requiring any free hands if a ranged weapon is equipped.
Correct action usage bug that could occur when a linked actor has multiple tokens present in the Scene.
Evasive Shot generates error when adding movement bonus to a basic strike attack.
Fix bug that creates errors when hovering over a action card target that no longer exists in the scene.
Ensure that the strike sequence for actions with the strike tag is properly reset each time the action is configured. This was incorrectly causing actions like Shield Bash or Offhand Strike to accumulate multiple additional strikes each time they were prepared.
Ensure that postActivate action workflows are called for actions which don't target any other creatures.
The Flurry action was missing the Difficult usage tag described in its text.