• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Version 11.1 of the Pathfinder files for Hero Lab is now available!

Aaron

Well-known member
This month's release includes the much discussed Pathfinder Unchained package, as well as Heroes of the Wild and the monthly AP content. Experiment with options like Variant multiclassing, or create a nature themed hero for your next adventure!

New Releases!
  • Content from Pathfinder Unchained is now available in a new package! Most optional rules are turned off by default, so you'll need to turn on the ones you want from the Configure Hero form. Please note: Overclocked Spells, Innate Item Bonuses, Scaling Items, Dynamic Magic Item Creation, and Simple Monster Creation are not yet supported, and will be added later as a free update to this package.
  • Content from Heroes of the Wild is now available as the first book in the new Pathfinder Player Companion #19.
  • All users now have access to player content from Pathfinder #92, "The Hill Giant's Pledge". To see this content, check the "Giantslayer" setting under "Pathfinder Adventure Paths" on the Configure Hero form.

Enhancements &amp Changes
  • Moving your mouse over a saving throw on the basics summary will now show a breakdown of what went into those calculations.
  • Added a new Mythic Path tab to the editor (thanks, ShadowChemosh!).

Bug Fixes
  • Half-Elves and other characters who must choose more than one favored class were not automatically setting a second or third favored class if they had added enough different classes to a character.
  • The natural attacks granted by a polymorph effect were not getting most of the damage modifiers that apply to a character, like an amulet of mighty fists, or spells like Divine Power.
  • When using a polymorph effect to take the form of a quadruped/many legs/snaky body race, the new form was not being reflected in the hero's reach, encumberance limits, and trip CMD.
  • The Blessing of the Faithful cleric ability was increasing it's range too quickly.
  • The Battle Cry feat was incorrectly requiring Wisdom 13, rather than Charisma 13.
  • The Blasting Charge feat was checking for 2nd level Bloodrager spells in a way which would not always work.
  • The Wand Key Ring was not able to select the full range of spells, and lacked a situational.
  • The Calling ability of Order of the Star cavaliers could throw an error when added to a character with less than 4 paladin levels and was not adding to the effective level of Lay on Hands.
  • Many of the Animal Shaman druid archetypes had an incorrect ability with misleading text that implied they broke the normal rules for polymorph effects. The ability has been removed or reworded.
  • Several references to the Mastodon race were misspelled as "Mastadon".
  • The Blood Golem from Bestiary 4 was not available for purchase.
  • The Boneshatter, Fleshcurdle and Shadow Ribbons spells were duplicated as a 2nd level Sor/Wiz spells.
  • The White Haired Witch archetype's Constrict ability was not fulfilling the pre-req of the Final Embrace feat.
  • The Animal Ally feat was throwing errors and behaving incorrectly for characters with more than 23 character levels.
  • The Harrow Strike Advanced Rogue talent was incorrectly marked as a normal rogue talent.
  • The Puppet Master familiar ability was missing its DC.
  • The Bloody-Knuckled Rowdy was getting the unarmed strike damage of a full monk, rather than a monk of 2 levels lower.
  • The combination of spending a Ki point for an extra attack and gaining an extra attack from Haste or similar sources would result in an attack routine typo which also caused the iPad apps dice roller to roll an incorrect number and bonus for flurry attacks.
  • The Lesser Tiger Totem Barbarian Rage Power was incorrectly requiring Barbarian level 6th to take, as though it were the mid level Totem power.
  • The Dragon Disciple was not stacking correctly with some aspects of the Draconic Bloodline.
  • The Evasive Deed, when added through an archetyped Paladin or ranger, was requiring too high a level.
  • The Many Forms Revelation was not calculating its uses per day.
  • The ring of adept maneuvers wasn't reducing the attack penalty from Flurry of Blows.
  • Feline Grace was raising an error if the new combat maneuvers from the Advanced Player's Guide weren't enabled.
  • The Subtle Blade deed was raising an error if the new combat maneuvers from the Advanced Player's Guide weren't enabled.
  • The Improved Flight feat could not be taken more than once.
  • The fauchard was missing the reach property.
 
Data File Authoring
  • Added the Hero.RageStance tag, used for the Unchained Barbarian's Stance powers. One tag is applied to the hero per active stance, and all active stances will report an error if two tags are applied simultaneously.
  • Prerequisites for Custom Special abilities have been revamped, so that they are more manipulable by users from the outside. Since the current trend seems to be allowing classes to use the custom specials of a different class (I.E. a fighter archetype letting Fighters take some alchemist discoveries) this new system should allow that to happen without the necessity of copy/replacing the shared custom specials in order to alter pre-requisites.
    • For convienance, the AutoPrereq component has had new fields added to record minimum class levels for each of the base classes published in Paizo sources. For Prestige classes, 3rd party base classes, and homebrew content please use the #custspeciallevelcount[] macro (see below).
    • There are three levels at which to intervene for the purposes of pre-requisites of custom special abilities, and three different tag groups to accomplish that. All tags must ultimately arrive on the hero to be counted, but can be applied to an archetype (before First 450, when it pushes them to the linked class) or a class helper (before PostAttr 10000, when it forwards one copy per level to the hero).
    • CSCountAs tags intervene at the Class level. If a class counts as another class for meeting any and all custom special ability pre-requisites then apply this tag to its class helper. For example, the Unchained versions of the Barbarian, Monk, Rogue, and Summoner all make use of these tags so that they fulfill pre-requisites as their core rulebook versions.
    • PreReqCaP1 tags intervene at the Ability Group level and inherit from the abCategory tag group. If a class counts its levels for meeting pre-requisites for a certain category of custom special abilities then apply the PreReqCaP1 that matches the abCategory tags to its class helper. For example, the Wild Rager archetype allows Rangers to gain Rage Powers as though their ranger levels were barbarian levels. Since Barbarian Race powers have the abCategory.BbnRagePow, the Wild Rager archetype applies PreReqCaP1.BbnRagePow to the class helper. Investigators (for alchemist discoveries), Skalds (for bardic masterpieces), and Ninjas (for rogue talents) all make use of these tags so that they fulfill pre-requisites of shared custom specials.
    • PreReqPos1 tags intervene at the Individual Ability level and generated as identity tags for all custom special abilities. If a class counts its levels for meeting pre-requisites for a limited list of specific custom special abilities then apply the PreReqPos1 that matches each listed abilities' unique ID. For example, the Undergroud Chemist archetype allows Rogues to gain a limited list of 10 alchemist discoveries so it applies 10 PreReqPos1 tags to the rogue class helper. Thuvian Alchemists, Veneficus Witches, and Mutation Warrior Fighters all make use of these tags for their limited lists.
    • CSCountAdj tags adjusts the number of any of the three tag groups applied by a class helper by up to +/-10. This is useful when an class counts as X levels lower for the purpose of meeting pre-requisites. For example, if your archetype allows Wizards to take Rage Powers as though you were a barbarian 4 levels lower, you would apply PreReqCaP1.BbnRagePow and CSCountAdj.NegLev4 to the Wizard class helper (in addition to any changes required to make the rage powers appear on one of the class tables).
    • PreReqCaN1 is the opposite of PreReqCaP1, it is subtracted when determining if a pre-req is met.
    • PreReqNeg1 is the opposite of PreReqPos1, it is subtracted when determining if a pre-req is met.
    • Added the #custspeciallevelcount[CLASS] macro, which is intended to work like #featlevelcount but for custom specials. It counts both Classes tags and the three tag groups mentioned above and should be used for expr-reqs for custom special abilities. The precise expansion of the macro is included below.
      • hero.tagcount[Classes.#class] + hero.tagcount[CSCountAs.#class] + altthing.intersect[PreReqPos1,PreReqPos1,countsource] - altthing.intersect[PreReqNeg1,PreReqNeg1,countsource] + altthing.intersect[abCategory,PreReqCaP1,countsource] - altthing.intersect[abCategory,PreReqCaN1,countsource]
  • Added FtCountAdj tag group, which functions exactly as CSCountAdj above, but in conjunction with the already existing FtCountAs tags.
  • Added the Climb Specific and Swim Specific general abilities. Like Burrow Specific, these are intended to be used when something has a speed limited to some specific factor, like a climb speed but only in trees, or a swim speed but only in Lava. The limitation should be detailed by filling in the abText field of the special when bootstrapping it.
  • Because of the option to add Planned Class levels, users will want to test any classes they have created in order to make sure they function correctly when no real levels have been added, but planned levels have been added. For example, if a class grants feats at 1st level, like the Improved Unarmed Strike and Stunning Fist feats of a Monk, make sure the tests for those feats are checking if there's at least one level of that class, and if a class grants spells known, like the Cure/Inflict spells of an Oracle, add the BonusSplAt.1 tag, which will hide those spells if they're only on planning classes, but show them once that class is on the real classes tab.
 
Gah! Graphical glitches galore! If I have multiple characters up, one of them is an unchained rogue and the other is a regular rogue, and switch between them, the gui for picking rogue talents gets messed up.
 
I did a bug report, but just wanted to ask about favoured class bonuses for the unchained classes: is their absence just a matter of the book not being fully implemented yet / an accidental oversight / working as intended / other?
 
Not a bug report but a Question

How are the Revised Action economy rules implemented?
Despite checking the box for it I can't seem to find anything that has to do with the system
 
Not sure if I post this here for a bug report this is my first time posting at all. But I noticed that the scythe and other weapons that should have the Trip weapon special now have the Reach weapon special. Such as the Scythe and Sickle.

This is on my iPad. Not sure if it's on the computer version I'm not at my computer to check. I downloaded the new update and reactivated my license twice and it still says it.
 
Is there an option to turn on Skill Unlocks for all skills for all classes without the need for the Signature Skill Feat, like the option for Stamina?

If not, how could that be done with the editor?
 
I have already reported that as a bug but to ask if I'm the only one that ran into this bug: The Synthesist Summoner Archetype seems to be broken since the Update.
Newly created ones with the normal APG Summoner get no Free Evolutions (Show up as Requirements not met). My previously created ones do not show this problem.
And it doesn't seem to work with the Unchained Summoner at all. :(
 
To repeat, everyone, please do not report bugs in this thread. Please report them through our bug tracking system: http://forums.wolflair.com/showthread.php?t=24976

Mathias - I get that re: reporting a bug, but is it okay to talk about whether something is a bug, or just a user's misunderstanding?

This is precisely what just happened with me: I found something I thought was a bug, and reported it, but it wasn't - it was my own dopiness.
 
I have already reported that as a bug but to ask if I'm the only one that ran into this bug: The Synthesist Summoner Archetype seems to be broken since the Update.
Newly created ones with the normal APG Summoner get no Free Evolutions (Show up as Requirements not met). My previously created ones do not show this problem.
And it doesn't seem to work with the Unchained Summoner at all. :(

Unless we get some guidance from Paizo about how the synthesist archetype interacts with the unchained summoner, I think it's unlikely we can make the two work together. Please report it being broken with the standard summoner as a bug though.
 
Mathias - I get that re: reporting a bug, but is it okay to talk about whether something is a bug, or just a user's misunderstanding?

This is precisely what just happened with me: I found something I thought was a bug, and reported it, but it wasn't - it was my own dopiness.

First, please don't hide it in a thread like this - give each issue its own thread.

Second, if you're writing it, and it's natural to start with "I'm not sure if this is a bug or not...", then you should not be posting it in the forums, you should report it as a potential bug. If we see a post starting with "is this a bug" in the forums, we won't study the issue in enough depth to confirm or deny it - we'll just tell you to report it, and I've seen "is this a bug" threads never get followed up on, because no-one answers the original question, so it never gets reported as a bug. So that's why I don't like seeing "is this a bug" threads - I'd rather have "is this a bug" bug reports.

Also, the "oops" moment doesn't have to be in public if you're working in the bug reporting system.
 
Last edited:
Back
Top