Release v3.1.2

[Moon Wizard]

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

This release is primarily focused on fixes and minor enhancements.

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

Cheers,
JPG

[WhtZombie]

Awesome, thanks I have been looking forward to this update. I had to search the forums to find the following info so I thought I would put it here for others. The following extensions are no longer needed:
Optional Conditions
Alignment Conditions
Move Dice Tower
Alt Wound Colors
HP Under Zero
Original Post https://www.fantasygrounds.com/forum...l=1#post218857

[HoloGnome]

After updating, I am seeing lots of script errors with portraits and tokens as shown below. Everything was working fine prior to the update.

This one shows up when trying to open a PFRPG character sheet:
Script Error: [string "scripts/manager_actor2.lua"]:94: attempt to index global 'ColorManager' (a nil value)

This one shows up when the PFRPG campaign is loading:
Script Error: [string "scripts/manager_actor2.lua"]:110: attempt to index global 'ColorManager' (a nil value)

Also, I can no longer move tokens to character sheets and the token images that were on the character sheets are now missing.

[JohnD]

Ran a game tonight. The skip if hidden in the CT was great... really cut down on CK confusion.

[kane280484]

Can anyone post an example or two of ALIGN effects? I.e. Smite Evil in PFRPG?

[Nickademus]

Ran a game tonight. The skip if hidden in the CT was great... really cut down on CK confusion.

Played in a game the day of the update. The GM was very confused why it kept skipping his gnolls. I had to inform him that the update added this and show him how to turn it off (though why it is set to on by default in beyond me). I guess it's a matter of perspective.

[Zacchaeus]

Can anyone post an example or two of ALIGN effects? I.e. Smite Evil in PFRPG?

The syntax would be something like IFT: ALIGN(evil); DMG: 1d8. I don't know what Divine Smite is in PFRPG but I'm fairly sure the syntax will be the same across all of the game types. Check out the Wiki for more information as to what can appear in the brackets.

[HoloGnome]

Is anyone else seeing the script errors and token problem? For me, the new release is unusable. I tried making new campaigns with no extensions and using the built-in theme in both PFRPG and 5e and see the same issues.

In 5e, the script error is at line 78 (vs. 94 in PFRPF):
Script Error: [string "scripts/manager_actor2.lua"]:78: attempt to index global 'ColorManager' (a nil value)

[dulux-oz]

Is anyone else seeing the script errors and token problem? For me, the new release is unusable. I tried making new campaigns with no extensions and using the built-in theme in both PFRPG and 5e and see the same issues.

In 5e, the script error is at line 78 (vs. 94 in PFRPF):
Script Error: [string "scripts/manager_actor2.lua"]:78: attempt to index global 'ColorManager' (a nil value)

I'm not seeing it Gnome - the ColorManager is defined in the CoreRPG base.xml file, so if its happening to you then it should be happening to all Rulesets which are child Rulesets of the CoreRPG. It also means that either:
a) something is corrupt (ie the CoreRPG), or
b) something is "replacing" the definition of ColorManager from the CoreRPG base.xml file.

All I can suggest is removing the Rulesets (the .pak files) from their current location on your HDD, ensuring that you have "Live" selected in the FG Settings, and running a fresh update.

[Trenloe]

Is anyone else seeing the script errors and token problem? For me, the new release is unusable. I tried making new campaigns with no extensions and using the built-in theme in both PFRPG and 5e and see the same issues.

In 5e, the script error is at line 78 (vs. 94 in PFRPF):
Script Error: [string "scripts/manager_actor2.lua"]:78: attempt to index global 'ColorManager' (a nil value)

Sounds like you're not running CoreRPG 3.1.2 - check the version for the "CoreRPG ruleset" in the chat window when you load up a campaign. It must be 3.1.2. If it isn't, check in your <FG app data>\rulesets directory for a directory called CoreRPG - rename it if one exists. If a CoreRPG directory doesn't exist, delete CoreRPG.pak and run an update.