2019-08-28 Update: Build 506C918
 

New Features and Content

• PF2 - A new Lost Omens World Guide package is now available.
• PF2 - Added support for Pathfinder Society, including Factions, Boons, and Pathfinder Training. To begin, on the Character/Settings tab, choose "Pathfinder Society Character", and the on the Character/Profile tab, choose a faction.

Client Changes

• Added faction selector elements to journal details, and Slotted checkbox for boons, and Starting Faction checkbox for factions
• Adds several lines to the Details for journal picks
• Adds the boon and faction tables to the Profile tab

Client Bug Fixes

• Fixes changes to characters such as name changes not showing up on the character selection screen or the character selection dropdown until the screen was reloaded or some other change occurred such as adding a character
• Fixes a rare error that could occur when applying changes to a character in one tab that was recently loaded in a different tab
• Fixes special characters causing search field to throw an error
• Fixes gear upgrades prompt dialog throwing an error

Game Mechanics

• PF2 - Pathfinder Society has some different rules for languages. In the Chraacter/Settings tab, new house rule options have been added so that these rules can be used on characters who are not Pathfinder Society characters.
• SF - In Starfinder Society Journal entries, the "Bonus Reputation Awarded" options were not functioning. Note that to fix up existing journal entries, you will need to re-select the faction to apply these to. Also, in order to add reputation to a faction, you must add the faction to your character first.
• PF2 - Existing spell adjustments have been updated to the Pathfinder Second Edition final rules.
• PF2 - A note was added to all class kits with "optional" gear that the optional gear must be purchased separate from the kit.
• PF2 - The Bear animal companion was not showing a scent range value of 30ft.
• PF2 - The Bear animal companion had the Bird support text instead of the bear support text.
• PF2 - Barbarian Giant Instinct was always applying the clumsy condition instead of when wielding a bigger weapon.
• PF2 - Sorcerer spellcasting was allowing selection of all spells instead of the bloodlines specific tradition.
• PF2 - Sorcerer was not showing the correct Spell DC.
• PF2 - The Monk's Wild Winds Initiate feat was providing three focus points instead of only one.
• PF2 - The Druid archetype feat Order Spell was providing two focus points instead of only one.
• PF2 - The Summary window was only showing the maximum for resource pools like Hit Points and Hero Points, rather than the current and maximum values.
• PF2 - The Frost Brand was showing up when "Hide Special Items" was checked.
• PF2 - The Frost Brand was not giving Fire Resistance when it was equipped.
• PF2 - The custom background was only allowing training in a lore skill, and not also allowing the selection of a general skill.
• PF2 - +2 and +3 potency runes were incorrectly requiring lower potency runes.
• PF2 - Familiars where unable to learn a language when the Speech ability was taken.
• PF2 - If your armor's speed penalty was improved by more than one thing (such as the Dwarf's Unburdened Iron feat and meeting the armor's strength requirement), it could end up adding a bonus to your speed.
• PF2 - The "Other" deity was not allowing the selection of a favored weapon option.
• SF - Fixed descriptions that had incorrect bold and italic mark up tags.

so, previously I was able to add a lore skill to my custom background. Now all of the characters I'd made successfully had their lore skills unchecked and I don't see a way to add the lore skill back to the background. I hadn't logged back in since this update went into effect.

I can check the box under the custom Background on the skills list. But it doesn't add the lore skill to the background tab and it is still flagged red.

I have submitted a bug for this a few days ago. The bug I'd is 248320.

They LWD replied with:

Thanks for the info. I'm getting this sent up to our team now with documentation on the problem. We appreciate very much your help and I hope we have this corrected swiftly.

I'm confused. With build numbers not having any possibility of sanity, are we regressing? The latest build from 9/18 has no notes, but all of a sudden this appears in an update from 3 weeks ago?

Note the date of the last post - an old announcement thread (not the newest one) was necro-ed to add a bug report instead of reporting the bug through the bug link in the program.

It's a good reason why you should lock old announcement threads at the same time you unsticky them. (Presumably you're only doing so because there's a new build.)