• 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

Class skill code... need some help

Sendric said:
kUserPts = 8
kUserRanks = 4

PS Sorry the table isn't cleaner. Let me know if it's confusing.
Click to expand...

The table is good, I have become accustom to how herolab does similar things to a table ..hahah
On kUuserPts & KuserRanks, I would agree on the divisor to not duplicate the effect.. but I'm still confused as to why its bad to use KuserPts and ok to use KuserRanks? Would seem one is just "pre-class" adjusted and the other isn't?

Kendall's Approach is certainly streamlined to what I was hoping to do... I'm certain I was losing something in my ability to convey what my goal was in translation of "want to accomplish":o.

2e "skill checks" were fundamentally simpler than 3.5e since most all revolved around a check against the attribute itself. It just gets muddy when the checks are % based and vary based on progression or attribute change.. But hey at least its not a 1e conversion where they had 18/98 strength to factor heheh:p

@ Both
I do appreciate the help from both of you:D I'm am certainly at the consider me "dangerous" level of understanding in herolab code writing .. hehehe
 
kUserPts vs. kUserRanks

Class Skill: kUserPRanks = kUserPts
Cross-Class Skill: kUserRanks = 1/2 kUserPts

It's just easier to take the later, since no math is involved. That's my take from the whole thing.
 
You must log in or register to reply here.
Back
Top