Release v3.1.6

[Moon Wizard]

Fantasy Grounds v3.1.6 is now available via the FG updater or via the FG installer on the Downloads page.

Here's a list of what is included:

• ...Lots of minor features, bug fixes and data patches...

It you want the details, a comprehensive list of patch notes is available here.

Cheers,
JPG

[jamessmckay]

Magic weapons are still broken. For example take a werewolf and try to apply damage with a magic weapon

[Moon Wizard]

It will only add the magic damage type to the magic weapon entry, if the magic weapon was added since the v3.1.6 update. It does not update existing campaign data, since the magic property was not included in the DMG data until this update.

To update existing weapons entries, just append ",magic" to the damage detail of the weapon entry on the PC Actions tab.

Regards,
JPG

[Zacchaeus]

Magic weapons are still broken. For example take a werewolf and try to apply damage with a magic weapon

It's not the magic weapons that are broken in this case but rather the monster's resistances aren't being set up properly in the Combat Tracker. It should read IMMUNE: bludgeoning, piercing, slashing, !silver, !magic

I can't honestly remember if it used to properly create the correct effect. I notice that others, such as the Helmed Horror aren't adding in the !magic bit too.

[Hector Trelane]

Thanks for the update Moon Wizard. Different question: is there a wiki instruction set someone can link to here that explains "dragged strings"?

[Zacchaeus]

Thanks for the update Moon Wizard. Different question: is there a wiki instruction set someone can link to here that explains "dragged strings"?

Type something into chat but before you press return click and hold on the text and drag it to somewhere. This is a dragged string.

[Moon Wizard]

Just posted some quick hot fix items that were identified since last night; also included in the patch notes now.

• [CoreRPG+] Table text values are now draggable.
• [CoreRPG+] Modifier stack not accepting specific roll types (attack, damage, etc.). Fixed.
• [5E] Party sheet ability order different than PC sheet. Fixed.
• [5E] The NPC damage immunity parsing was only identifying "nonmagical weapons", not "nonmagical attacks". Fixed.

JPG

[Zacchaeus]

Well done M W. That was quick

[Vishera]

Just posted some quick hot fix items that were identified since last night; also included in the patch notes now.

• [5E] Party sheet ability order different than PC sheet. Fixed.

JPG

YES! Glad to know you guys saw my annoyance post! Thanks for the fix!

[Trenloe]

With this release there has been a change in how the auto calculation of which dice to use within a table if there are unnumbered rows.

Take the following example. A table with 8 rows, 1-8 rolls a d8 (correctly):



However, if I remove the 8 die roll number allocated for row 8 (#1 in the screenshot), the die changes to d8-1(#2):



I'm assuming this is because FG sees the "eight" row as being 0 rather than blank and so calculates a range of 0-7 which is 1d8-1.

In previous versions, any blank rows wouldn't have been included in the die roll auto calculation.

So, with this new calculation there are two issues:

1. It is not possible to remove a row temporarily from the table - the row would have to be deleted completely.
2. It completely breaks the Basic Cards Extension: https://www.fantasygrounds.com/forum...les-Extensions which relies on removing rows (cards) temporarily from the table (card deck) by setting the number range to 0.

Is this change to the way the auto die roll is calculated absolutely necessary (i.e. it's been implemented to cover other functionality) or could it be put back the way it was, please? Or, is there a way this could be worked around somehow?