View Single Post
Mathias
Senior Member
Lone Wolf Staff
 
Join Date: May 2005
Posts: 13,213

Old September 26th, 2019, 07:50 AM
When we add a message that a feature is not yet implemented, it also means that it is already on our to-do list, and that we've already analyzed what needs to be accomplished, and assessed that as something that has to be put on the back burner, and so bug reports about that missing feature will not supply any new information that will help us address that issue.

In this case, the problem is that the same feat, when added to this specific table (not the general feats table, for example), but only when that table is offered by this archetype, needs to be fed an extra bit of information to tell it that if there's a fighter level prereq on the feat, it can instead feed the paladin level + fighter level into that value. Unfortunately, this kind of wrinkle in how specific the prereq code would need to get was not anticipated when building the prereq mechanics, so there's a lot of behind the scenes work needed to adjust how those work in order to get this functioning.

So in the meantime, you'll have to work around this issue - in this case, you can ignore the error message, add the feat anyway, and the only problem will be that there's a false error message on your character you'll have to ignore - the feat will still apply its effects, regardless of whether it fulfills its prereqs or not.
Mathias is offline   #8 Reply With Quote