• 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

Some way around...

royalfa

Active member
Well I can choose now the attribute that has a +2 at creation.

But here is the thing if this attribute already has a value,as per Racial Bonus in the racStr field for example, then I get this error:

Attempt to use inconsistent operator for field adjustment with history tracking for field "trtRacial".

Lets say that one race has "+2 to any attribute and -2 Constitution" and the player what the +2 optional in Con to erase the -2.
The race has a Racial bonus: -2 Con stored in racCon, and is tracked with trtRacial, but at the selection of Constitution in the menu, HL pops up the above error.

Moreover one race has "+2 to any and -2 to any" if I select in any of this the same attribute; the second time I do that, the error "pops"

I solve the first making a new field called racCreat (name= Creation bonus)
and I'm thinking in modify that (to racCreatP, name= Creation Plus Bonus) and create a new one: racCreatM, name Creation Minus Bonus)

I think this solve the trouble but is not "elegant"

Is any other way to access/modify the trtRacial instead??
Right now I have this:


Code:
perform field[usrChosen1].chosen.field[trtRacial].modify[+,2,"Racial"]

I presume here is the error.
 
0k I understand the history is "best" then will use "the best bonus" I assume but send and error...

You thing is better to change history option to "change" and leave the script as the first one I have??
 
"stack" is the history option I prefer for most fields.

History tracking is useful because it allows you to show the user how Hero Lab reached the value it has for an attribute, or attack roll, or whatever. It isn't necessary, though, so you may also choose to work towards getting your system functional enough to build a character, and not worry about the "nice to have" things like history tracking, then come back and modify everything to use history tracking once you have your game more complete.
 
Ok I like that.
Right now I'm having troubles to "figure it out" What to do next?

I need to implement class, Specialty/Talent (the second one only for humans; function similar to background in 4e), saving throws and other basics (Initiative, Defense, Vitality all depends on class) and Wounds (depends on constitution but need track in "in play tab")

I'm thinking in Saving throws first and try to work out some more race features.
 
Back
Top