Bug with Armor/shield Proficiency Feats and Hybrid Characters

Post/Author/DateTimePost
#1

CarlT

Jun 09, 2009 17:44:41
If there is a more reliable way to submit bugs, please point me in that direction. Otherwise....

Bug Report

Character Builder build 201227 (June 2009 update)
Reproducibility: 100%


When creating a Paladin/ Warlock Hybrid, the character is limited to Leather Armor (as it should be according to the rules).

However, when attempting to add Armor Proficiency Feats to a character (example case: Halfling Paladin/ Warlock hybrid) who is eligible for the feats (Str 13, Con 13), the system does not behave as expected.

When I attempt to add Armor Proficiency (Chainmail) to the character, the feat is available to be selected, but when the feat is selected it does not show up in the Feat Choice Checklist as having been selected (the display continues to say and the relevant armor choices remain "red" in the Shop: Equipment: Armor window. However, the feat Armor Proficiency (Chainmail) disappears from the Feat Choices window and is replaced with the feat Armor Proficiency (Scale).

If I then attempt to add Armor Proficiency (Scale) to the character, the same process occurs: The feat does not appear in the Feat Choice Checklist and the scale armor options remain "red" in the Shop window (as does chainmail). Furthermore, the Armor Proficiency (Scale) option disappears from the Feat Choices window and is replaced by Armor Proficiency (Chainmail), bringing us back where we started.

If the character is eligible for Armor Proficiency (Plate) the process continues: Upon selecting Armor Proficiency (Scale), the feat Armor Proficiency (Scale) still does not appear in the Feat Choice Checklist window (which still reads and it disappears from the Feat Choices window. But now both Armor Proficiency (Chainmail) and Armor Proficiency (Plate) appear in the Feat Choices window. Clicking AP (Plate) causes AP (Plate) to disappear as an option and be replaced by AP (Chainmail), Clicking AP (Chainmail) causes AP (Chainmail) to disappear and be replaced by AP (Scale).

The same process also occurs with the Shield Proficiency (Light) feat, which is replaced by the Shield Proficiency (Heavy) feat, without the feat actually appearing in the Feat Choice Checklist window; and then again with the Shield Proficiency (Heavy) feat which is replaced by Shield Proficiency (Light) in the Feat Choices window without actually registering the feat in the Feat Choices Checklist window.

Bottom Line: There is no way to add these armor/ shield proficiency feats to an eligible character, despite their appearing in the Feat Choices window.

This was also tested with a Fighter/ Warlock hybrid and the same process occurs with that class. However, significantly, when the process made Armor Proficiency (Plate) available to the fighter/warlock - I was able to select that feat and it registered properly on the character sheet. This led to the unusual situation of a character who was proficient in plate (the plate armor option was listed in "black" in the Shop: Equipment: Armor window but not in either chainmail or scale armor (both of these were still listed in "red" in the Shop: Equipment: Armor window.

Bottom Line: You can add Armor Proficiency (Plate) to a fighter class hybrid combined with a hybrid class that is more restricted in their armor choices, but you cannot add either AP (Chainmail) or AP (Scale).

Although not tested with every class combination, I suspect this is true of any hybrid character that combines a heavier and a lighter armor using the hybrid rules: Any Armor or Shield proficiency feat that duplicates an armor or shield type available to one class but not to the other (and thus not to the hybrid character) cannot be selected although one can select those armor types that are not available to either - despite not truely having the requisite feats.



I suspect this is due to a conflict between a routine that is (correctly) determining that the hybrid character lacks the ability to use the heavier armor and therefore offering the feat as an option, and a second routine that is (incorrectly) rejecting that choice as being redundant because the heavier-armor using class already has that ability (and then offering the next feat in the progression).

Carl
#2

Mock

Jun 10, 2009 8:20:33
It's a bad one. I reported it via the "formal" bug report system, too. Hopefully they'll fix it immediately, if not sooner.