Page 1 of 1

Cannot Select Path of the Bladesinger

Posted: Tue Jan 11, 2022 12:16 am
by Dubhwulfe
Description of Bug Experienced:
Created a half-elf Spellsword on Skal within 24 hours of class creation. Currently reached level 12. Have dodge (half-elf), Dex 18, and am unable to choose Path of the Bladesinger as either a default level 12 feat, or the Spellsword 12 bonus feat. Feat does not show up in list, though I do have the "Spellsword Path Token" feat.


Steps to reproduce the Bug:
Unable to reproduce on another character. Friend and I both attempted to test it in the PGCC.


Expected Result:
Able to choose "Path of the Bladesinger" feat.


Actual Result:
"Path of the Bladesinger" feat doesn't exist.


Screenshot(s)
Image

Additional Information/Notes Minor Award: Sylvan Language used.

Re: Cannot Select Path of the Bladesinger

Posted: Tue Jan 11, 2022 1:29 am
by Normolomue
Just a quick thought, does the character have the "Dodge" feat as a prerequisite?

Re: Cannot Select Path of the Bladesinger

Posted: Tue Jan 11, 2022 1:40 am
by Zanithar
Normolomue wrote: Tue Jan 11, 2022 1:29 am Just a quick thought, does the character have the "Dodge" feat as a prerequisite?
HElf nets that feat as a racial bonus feat.

Re: Cannot Select Path of the Bladesinger

Posted: Tue Jan 11, 2022 6:08 am
by Deapri
I just tested this with a Half-Elf on the PGCC taking Dodge, despite it supposed to being free, at creation, the Bladesinger bonus feat never appeared on the spellsword 1-30. I was able to select the Path of the Bladesinger feat on level 12 as a bonus when not selecting dodge at creation, is there more than 1 dodge feat reference? might see if making the normal dodge unelectable is the trick here. The prerequisited say 12+ spellsword levels the uniformity would put this as 11+ as you are able to take it on 12.

Re: Cannot Select Path of the Bladesinger

Posted: Tue Jan 11, 2022 4:09 pm
by Dubhwulfe
Since it seemed to not be an issue with all characters I made, just this one for some odd reason, I deleted it, so while it was still a toon-specific bug, there's no hurry for me. :)