Skip to content

EXPERIMENTAL System Version 7.0.3-exp: Scene Region Templates and Activity App

Pre-release
Pre-release

Choose a tag to compare

@Savantford Savantford released this 12 Aug 20:39
· 64 commits to v14-support since this release

WARNING: THIS IS AN EXPERIMENTAL VERSION, EXPECT UNFINISHED FEATURES AND BUGS. AND PLEASE REPORT THEM!

WARNING: MAKE SURE TO BACKUP YOUR WORLDS BEFORE TESTING! Upgrading to Foundry v14 and Weird Wizard 7.0.X-exp at this moment will most likely corrupt your world data! You have been warned!

Hello, everyone!

This experimental release brings you two big overhauls with a bunch of new features, namely Scene Region Templates and the new Activity app, but also a bunch of polishing to what we have.

I could try to make a highlight, but I believe it's better to read the patch notes to understand what changed. Please read them!

That's all!

As always, a big thank you for all the continued support and patience! Have a nice week!

Changes

Targeting & Scene Region Templates

In addition to the existing manual token targeting, you can configure Items (Equipment, Traits, Talents and Spells) to prompt the placement of Scene Regions when used.

  • You can configure this behavior in the dedicated Targeting section, in the Item sheet's Automations & Effects tab.
  • Two distinct Scene Region operations are available:
    • Targeting tokens within an area: This Region is used for area targeting. Templates here are ephemeral, removed once targeting is complete.
      • This replaces the old measured templates we had, with roughly the same functionality.
    • Create a persistent area: This Regions stays in the scene until removed manually. This was only available before with an unintended bug breaking functionality, but now it's here to stay! As a regular Scene Region, once placed, it has a configuration sheet that can be accessed through the Region Controls layer.
  • You can preconfigure the Region template within the Item sheet with Weird Wizard friendly fields:
    • Radius in yards: The template's Size. If you want a Size 5 area, change it here.
    • Attach To Token: Whether the region should be attached to a token, moving along with it. If you want an aura effect, check this.
    • Color: The color of the generated scene region. If the field is blank, the User's color will be used instead.
    • Wall Restriction: You can restrict the region's expansion from its center towards the edges:
      • Enabling Is Restricted will allow restriction to take place. (Enabled by default.)
      • You can change the restriction method by changing the Restricted By dropdown menu. (By default, movement-blocking walls will restrict the expansion.)
      • You can change the Priority Threshold for advanced fine tuning of the expansion. (Default is 0.)
  • Once a Scene Region is configured and used, the new Activity app (see below) will handle the Scene Region placement.
  • The template should work at any scene grid configuration: square, hex or gridless!

Activity App

A new app joins the family: the Activity Use app, or simply Activity app. Initially designed to support the new Scene Region templates, they put two important things in the same place: Targeting and Dice Rolling.

  • All functions previously handled by the retired Roll Details app were merged into the Activity app, but with a few new additions and improvements:
    • A new fancy icon expression will display the dice and numbers being used. This is complementary to the existing full text expression (i.e. "Agility with 2 boons against Defense").
    • You can now change the Attribute modifier used for the roll directly from the app.
    • You can now also change the targeted Attribute you are rolling against.
    • Roll Details were put in a collapsible element to make the app look cleaner, since most of the time you don't need to see or change it.
      • Roll Details include Modifiers, Total Boons and Banes and Against/Target Number sections.
  • A dedicated Targeting section is available with mostly new functionality:
    • You can click the Target tokens manually button to open the Targeting HUD.
      • Once open, the Activity app is minimized and Foundry's Target tool is enabled, allowing you to target tokens easily.
      • Once closed, the Activity app is open once again.
      • If you want, you can open the Activity app anytime to see the live targeting feed!
    • Like before, the app always take targets you previously selected before opening the app, but it now also automatically updates if your targets change!
    • If preconfigured correctly, a button will show for placing down an appropriate Scene Region template either for targeting tokens or for creating a persistent area (see Targeting & Scene Region Templates section above for details).
    • You can now restrict your targets to Enemies or Allies, in addition to targeting Anyone.
  • The Confirm button now becomes red and has a tooltip when Targets were not selected for an activity expecting targets.
    • The button functionality is unchanged while in this state, it's just a reminder that maybe you should select targets before clicking it!
  • You can now change the Message Mode (aka Roll Mode in Foundry v13 and below) directly on the app, next to the Confirm button. No need to interact with Foundry's UI when making that sneaky secret roll!
  • The app automatically minimizes the origin actor's sheet to improve visibility.

Other Changes

  • In order to test Secrets in v14, everything from 6.3.6 and 6.3.7 and versions were merged into this experimental release, including the new public domain token art pieces created by @yschnellbach!
  • Blinded affliction now blinds the token.
  • Item Sheets now show the Attribute modifier value in the dropdown in the Automations tab.
  • The Targeting HUD app was upgraded to V2 and simplified to be used by the Activity app.

Bug Fixes

  • CRITICAL: Fixed an issue where Afflictions affecting calculated stats (Defense, Health, Speed) were not being applied correctly. (By @BoyBoyMan)
  • CRITICAL: Fixed upgrade/downgrade Active Effect changes not working if you assigned the value to 0. (By @BoyBoyMan)