• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Paladin Divine Guardian Bonus Feats not working correctly

C

Cards77

Well-known member
Specifically, Greater Shield Focus is still requiring Fighter Level 8 and cannot be selected even though all prereqs are met (Shield Focus, Shield Proficiency, +1 BAB, etc)

I am using a Divine Guardian level 11, I have Shield Focus.


Obviously all other prereqs have been met but the part of the archetype that states "paladin level equals fighter level" for the purposes of bonus feats isn't being treated correctly by HL.
 
Lj Stephens said:
Yes, please! And screen shots are always helpful too. Thanks![/Q]


Reported bug

File limits on uploads are way too small for this screen shot.

See image here

GTtLzf3


I guess linking to imgur isn't allowed either. Pretty limited options we have here

https://imgur.com/a/GTtLzf3
Click to expand...
 
Last edited:
ShadowChemosh said:
Did you read the text right above where you highlighted the warning? It actually tells you everything your asking about. :)
Click to expand...

I saw that when i made the screenshot. Doesn't mean it makes sense. Why would it be in there and all other shield related bonus feats work?

We bought the data package, the archetype is there, other bonus feats in the same screen work properly. The prereqs are met for this feat, and I'm able to take all other feats with the same prereqs.

I could understand I guess if a bonus feat required Spellbreaker, or some other requirement mentioned there, but this isn't the case.

So, no that doesn't answer anything for me sorry.
 
Last edited:
Cards77 said:
I saw that when i made the screenshot. Doesn't mean it makes sense. Why would it be in there and all other shield related bonus feats work?

We bought the data package, the archetype is there, other bonus feats in the same screen work properly. The prereqs are met for this feat, and I'm able to take all other feats with the same prereqs.

I could understand I guess if a bonus feat required Spellbreaker, or some other requirement mentioned there, but this isn't the case.

So, no that doesn't answer anything for me sorry.
Click to expand...

It means that implementing the details of this particular feat are quite challenging, and probably require changes in other parts of the data set in order to be able to get it to work.

Thus, the warning that it hasn't been fully implemented yet.
 
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 said:
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.
Click to expand...

Thanks I understand. Not trying to sound flippant, I would think it would be a pretty simple fix (I'm definitely NO coder). Paladin level = fighter level, easier said than done it seems.

I will work around
 
You must log in or register to reply here.
Back
Top