• 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

Skill Adjustment not showing in column

Kerokus

Member
Hey all! So our DM informed us that we get a "+2 skill bonus to skill of your choice."

So I wanted to up my Diplomacy by 2 points. I went to the "Adjust" tab, clicked on "Other Adjustments" and selected, "Skill bonus".

I changed the number to 2, and selected "Diplomacy".

Now, the program is saying all Validation rules are satisfied, but if you look at the "Skill & Feats" column, it's not showing the change. Even when you output the char sheet, it doesn't show the adjustment.

Anyone know what I'm doing wrong here? When I google it, I can't find anyone else having this problem, so it's making me think it's something I'm not doing correctly, rather than a bug of some kind. Suggestions?
 
Did you choose a bonus type, although I get this error when I do it

Code:
Attempt to access pick information or behaviors for read-only thing 'selBonus'
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 8
- - -
Attempt to access 'focus' pick from script when no focus exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 10
- - -
Attempt to access pick or thing information when no context exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 10
- - -
Attempt to access 'focus' pick from script when no focus exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 13
- - -
Attempt to access pick or thing information when no context exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 13
- - -
Attempt to access 'focus' pick from script when no focus exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 15
- - -
Attempt to access pick or thing information when no context exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 15
- - -
Attempt to access 'focus' pick from script when no focus exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 18
- - -
Attempt to access pick or thing information when no context exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 18
- - -
Attempt to access 'focus' pick from script when no focus exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 21
 
The "official" adjustments that use a "type" of bonus are messed up. They don't currently work as of the the last release.

If you have HL in debug mode you see the adjustments are tossing a LOAD of errors:
Code:
Attempt to access pick information or behaviors for read-only thing 'selBonMora'
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 8
- - -
Attempt to access 'focus' pick from script when no focus exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 10
- - -
Attempt to access pick or thing information when no context exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 10
- - -
Attempt to access 'focus' pick from script when no focus exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 13
- - -
Attempt to access pick or thing information when no context exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 13
- - -
Attempt to access 'focus' pick from script when no focus exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 15
- - -
Attempt to access pick or thing information when no context exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 15
- - -
Attempt to access 'focus' pick from script when no focus exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 18
- - -
Attempt to access pick or thing information when no context exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 18
- - -
Attempt to access 'focus' pick from script when no focus exists
Location: 'eval' script for Thing 'pSkillBon' (Eval Script '#1') near line 21

I am pretty sure this is has been reported to LW as I several people reported the problem to me thinking it was my Adjustment addon. But its the core adjustments that are down. :( I would expect them to be fixed in the next release of Pathfinder.
 
For those curious about what happened, somebody asked last month for a way to add a class of spells to an existing class' spellcasting. I wanted to select among the classes on the character with one chooser and all spellcasting classes with the other chooser. In order to do that I had to make the 1st and 2nd chooser on adjustments be able to decide whether they are picking among "things" or "picks" individually. Prior to that, they both had to pick the same.

Unfortunately, once I split that up, existing adjustments which assumed that the 2nd chooser was the same as the first were suddenly defaulting to things instead of picks. And since many of those 2nd choosers tried to set the focus to the chosen item, that was throwing errors (since a focus can only be set to a pick).

Cautionary tale about simple changes leading to unintended consequences in coding.
 
For those curious about what happened, somebody asked last month for a way to add a class of spells to an existing class' spellcasting. I wanted to select among the classes on the character with one chooser and all spellcasting classes with the other chooser. In order to do that I had to make the 1st and 2nd chooser on adjustments be able to decide whether they are picking among "things" or "picks" individually. Prior to that, they both had to pick the same.

Unfortunately, once I split that up, existing adjustments which assumed that the 2nd chooser was the same as the first were suddenly defaulting to things instead of picks. And since many of those 2nd choosers tried to set the focus to the chosen item, that was throwing errors (since a focus can only be set to a pick).

Cautionary tale about simple changes leading to unintended consequences in coding.
What I got out of this is the gamer that asked for that Adjustment caused all the issues. If he had just kept his mouth shut we all would have working adjustments right now! :D ;)

Come on Aaron you got to learn how to deflect fault on to anyone but yourself. Its the proper business method I have learned. Which is actually very sad but true... :( :(
 
Back
Top