Cannot Add Property Runes to Weapons and Armor when Using Automatic Bonus Progression Alternate Rules

Pathfinder Nexus & Character Tools
1

Hello,
So by the standard rules of Pathfinder you can add a number of property runes to a weapon or suit of armor equal to the potency rune bonus the weapon or armor has. The character tools are configured for this, and if your armor or weapon doesn’t have a potency rune on it it gives you no property rune slots. This is a problem because when you use the Automatic Bonus Progression alternate rules your character receives the potency bonus as a part of their level progression, and because of that you never add potency runes to weapons and armor. It looks like the sheet does not allow you to add property runes once you have the potency bonus.
In fact, as I look at the variant rules for Automatic Bonus Progression it doesn’t really say how many property runes you can put on a weapon using the rule. I think it is probably 3 of them on a normal weapon. If you’re using special materials, it’s 1 for a low grade item, 2 for a medium grade and 3 for a high grade. 4 if the weapon is made of Orachalcum. As a GM I would probably rule that you can only activate a number of runes equal to the potency bonus you have or something similar. But either way there definitely needs to be a way to add property runes when using Automatic Bonus Progression.

1 Like
2

Those are alternative rules so it makes sense that by default they are not supported. A workaround in the meantime could be to add the relevant potency runes and then manually cancel them out with a hidden penalty

3

… I mean, the Automatic Bonus Progression rules are absolutely supported. You can enable them in the Preferences of the character builder. Since they actually are a rule system that is supported in the character builder it is completely correct to report incorrect behavior with them. Yes, there is a workaround. This is still something that should be fixed.

4

I appreciate the report, sorry to hear it’s not working but I’ve got a ticket filed for further investigation.

5

Thanks I appreciate it. I’ve got a workaround going for now but it’ll for sure be good to have that working right :slight_smile: