Armor Speed/Check penalty?
 

Whenever I buy armor in the app, it shows the armor penalties as simply "-", and doesn't reduce the speed or skill checks by the appropriate amounts. But it shows correctly in the catalog before I buy it.

Is there something I need to do to apply the penalties properly, or is there a bug?

Hi Maclimes. When you buy armor in HLO, it automatically equips usually, and shows up on your character sheet on the right hand side. I suggest sending this to support@wolflair.com with as much step-by-step detail as you can offer, and we'll dig into it for you. Thanks!

It has something to do with the order of the process, but I can't quite figure out what. I created a Human (Versatile) Fighter, and gave him a Breastplate. The copy he got has -/- for the penalties. But if I create a new character, blank, and give him a Breastplate, it has the appropriate -2/-5 that it should (and it retains the value after completing the character).

Strange.

EDIT: Found it! I bought and sold the Breastplate after every single step. It was the act of adding my Ability Scores that broke it. Adding the four 1st level stats is fine. But checking the boxes for my Ancestry and/or Background, specifically the Strength attribute, causes the existing armor to break. WEIRD. Reporting the bug through the in-system Bug Report feature.

Core Rulebook pg. 274 in the Strength section: "If your Strength is equal to or greater than this value, you no longer take the armor’s check penalty, and you decrease the Speed penalty by 5 feet". So once you add the armor, HL determines what penalties it actually applies to your character, based on whether you meet the strength minimum for that armor, and shows you only the adjusted values.

So this is NOT a bug.

I noticed that when I bought and equipped leather armor, it is actually adding 5 to my speed. Leather armor has no speed penalty, so it looks like the program is subtracting 5 from 0 (since I have strength > 10) and getting a +5 speed adjustment. THAT seems like a bug.

I somehow completely missed that! Thank you!

Although it seems a bit odd that it wouldn't be clearly displayed anywhere. It certainly LOOKS like a bug or something, but now I understand where the calculation came from.