Lone Wolf Development Forums  

Go Back   Lone Wolf Development Forums > Hero Lab Forums > HL - d20 System

Notices

Reply
 
Thread Tools Display Modes
Sendric
Senior Member
 
Join Date: Jul 2010
Posts: 3,147

Old January 24th, 2014, 11:16 AM
So I have a bit of an issue with the Tome of Battle that I didn't realize until I read the unofficial official errata. Each base class from the book carries its own initiator level. For example, a Crusader 11/Swordsage 8 would have an initiator level of 15 for the Crusader, but only 13 for the Swordsage. Both classes have access to some maneuvers, but if the maneuver requires an initiator level 15, then that maneuver would only be available to the character via his/her Crusader levels. So, how do I script such a thing? I can set up the initiator level for each class fine. For example, if I have a special called "Initiator Level - Crusader" and it sets its value appropriately. Checking the value on this is easy enough, but makes the maneuver available to both classes. To make it only available to the crusader, I tried this:

Code:
if (linkage[table].field[cTotalLev].value <> 0) then
 validif (hero.childfound[xInitCrusa].field[Value].value >= 15)
endif
This gave me the following error upon compiling:

Quote:
Hero Lab was forced to stop compilation after the following errors were detected:

Syntax error in 'pre-requisite rule' script for Thing 'cStoDra081' on line 1
-> Script reference is invalid under the circumstances
Either I'm using the linkage command incorrectly (which is highly probably given my lack of experience with it) or it doesn't work right in d20. Either way, does anyone have any suggestions on how to handle this?
Sendric is offline   #1 Reply With Quote
Mathias
Senior Member
Lone Wolf Staff
 
Join Date: May 2005
Posts: 13,213

Old January 24th, 2014, 11:33 AM
A prereq has to be tested both before and after it's been added to the character, but a linkage isn't established until after the pick has been added, so a linkage can't be used in a prereq.
Mathias is offline   #2 Reply With Quote
Sendric
Senior Member
 
Join Date: Jul 2010
Posts: 3,147

Old January 24th, 2014, 11:38 AM
So is there a way to check the parent class prior to it being added to the character? Would the above script work in an eval rule?

Last edited by Sendric; January 24th, 2014 at 11:41 AM.
Sendric is offline   #3 Reply With Quote
ShadowChemosh
Senior Member
Volunteer Data File Contributor
 
Join Date: Jan 2010
Location: Chicago, IL (USA)
Posts: 10,729

Old January 24th, 2014, 11:58 AM
Quote:
Originally Posted by Sendric View Post
So is there a way to check the parent class prior to it being added to the character? Would the above script work in an eval rule?
This is exactly the same issue I had with Path of War (Pathfinders Tome of Battles Rules). You can't figure out what class from a Table Selection. I confirmed this by looking how LW implemented Psionics in d20. That works the exact same way with Powers.

Until the Power becomes a "pick" you can't test what your attached too. So only after your a "pick" can you throw the error. It can't be done while you exist as a "Thing" in a table.

Hero Lab Resources:
Pathfinder - d20pfsrd and Pathfinder Pack Setup
3.5 D&D (d20) - Community Server Setup
5E D&D - Community Server Setup
Hero Lab Help - Hero Lab FAQ, Editor Tutorials and Videos, Editor & Scripting Resources.
Created by the community for the community
- Realm Works kickstarter backer (Alpha Wolf) and Beta tester.
- d20 HL package volunteer editor.
ShadowChemosh is offline   #4 Reply With Quote
Sendric
Senior Member
 
Join Date: Jul 2010
Posts: 3,147

Old January 27th, 2014, 11:39 AM
I guess I could do this as an eval rule then. Thanks.
Sendric is offline   #5 Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -8. The time now is 01:06 PM.


Powered by vBulletin® - Copyright ©2000 - 2024, vBulletin Solutions, Inc.
wolflair.com copyright ©1998-2016 Lone Wolf Development, Inc. View our Privacy Policy here.