• 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

Table Linkage for Class Skills Not Working

I've noticed there has been a change to the way the linkage to a class skill is working. Whereas previously, the linkage worked fine for defining a class skill, it is not working now. Keeps throwing the following error: "Linkage pick 'table' not located for current context".

My guess is that now the parent-child relationships in HeroLab has changed, because I've begun to notice a lot of things are no longer requiring the transition to the parent container to get things done. Is this what is happening here? For example, try adding Trickery to a Cleric, then try adding ranks to Hide. The linkage doesn't see the table context anymore.

Feature or bug?
 
What happens when you do the trickery cleric/hide class skill thing for you? It seems to work as it always has for me.
 
I am also unable to produce errors with this. When I add Trickery, Hide becomes a class skill for the Cleric as it should.
 
Hmm, I might have something wrong in my user file, I have been playing around with different configurations of tags and fields and I may have inadvertently caused the table linkage to break.
 
Ok, this is odd. Seems this is only occurring when I have a custom domain I created. I'm trying to link Sense Motive as a class skill and I get an error. The same code exists in Trickery but for Hide, etc. and there is no error. Can someone verify this?

UPDATE: Nevermind, figured it out. Was being stupid and trying to get the linkage from a special when the special didn't bootstrap to the class. I was bootstrapping it to a domain. Been like that a while, and I never knew I had made the blunder until I started using the domain. D'oh!
 
Last edited:
Back
Top